Re: wrong translations of gconf key values
Em Qua, 2009-01-28 às 21:56 +0200, Deniz Koçak escreveu: > On Wed, Jan 28, 2009 at 9:31 PM, Og Maciel wrote: > > +1 for adding comments to the strings. > > +1 for comments, but what is the idea of developers about always > warning translators? > It would be great if somehow the comments were added automatically, but I don't know how to do it, and with which tool. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Bug 569118 - Use C_() instead of Q_() with context (orca)
Em Ter, 2009-01-27 às 14:09 -0500, Willie Walker escreveu: > In the past, I was slapped seriously by the l10n team for touching *.po > files. So, I'm requesting permission here before I check in the *.po > changes. Is this OK with you all? > This might be more to the point: for file in po/*.po; do sed -i "s+msgid \"\([^|]*\)|+msgctxt \"\1\"\nmsgid \"+" $file done But yes, let's see what happens to nl.po before doing it for every file :) -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String change in Cheese documentation
IIRC I didn't need to, but I wanted to tell you that I introduced minor changes in the documentation for Cheese: http://svn.gnome.org/viewvc/cheese?view=revision&revision=1177 Updating the translation should be trivial for the 5 or 6 locales for which the documentation was completely translated before. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [Fwd: [Bug 566454] Literal values should be kept between double quotes]
Em Qua, 2009-01-21 às 17:35 +0100, Marcel Telka escreveu: > On Tue, Jan 20, 2009 at 05:59:49PM -0200, Leonardo F. Fontenelle wrote: > > Em Seg, 2009-01-19 às 23:20 +0100, Andre Klapper escreveu: > > > Am Montag, den 19.01.2009, 20:09 -0200 schrieb Leonardo F. Fontenelle: > > > > If devhelp branch gnome-2-24 is used in GNOME 2.26, is it still string > > > > freezed? > > > > > > yes, it is still string frozen and will remain for all times, because > > > the gnome-2-24 branch is also used in the stable GNOME 2.24 series which > > > is string frozen too. > > > > > > > The following diff in the POT shows what I changed in the source code > > for trunk. I'm posting here to warn translators to check if the > > translations in GNOME 2.24 are correct. The elements names shouldn't be > > translated! > > Then, why are those elements just a part of the msgid without a > translation comment? Please either add a translation comment or use %s > instead of the untranslatable element. > Words between double quotes are usually literal values, but if it's not clear enough already, comments shouldn't hurt. (Richard Hult, please do it; my right forearm hurts and I'm typing just with the other hand.) We've discussed the %s here, weeks or months ago. Keeping the literal values helps the translator choosing gender and other inflexion in the remaining translation, and allows the translation to have explanations like: "Os valores válidos são \"none\" (nenhum), \"top\" (topo)..." -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [Fwd: [Bug 566454] Literal values should be kept between double quotes]
Em Seg, 2009-01-19 às 23:20 +0100, Andre Klapper escreveu: > Am Montag, den 19.01.2009, 20:09 -0200 schrieb Leonardo F. Fontenelle: > > If devhelp branch gnome-2-24 is used in GNOME 2.26, is it still string > > freezed? > > yes, it is still string frozen and will remain for all times, because > the gnome-2-24 branch is also used in the stable GNOME 2.24 series which > is string frozen too. > The following diff in the POT shows what I changed in the source code for trunk. I'm posting here to warn translators to check if the translations in GNOME 2.24 are correct. The elements names shouldn't be translated! #: ../src/dh-parser.c:122 #, c-format -msgid "title, name, and link elements are required at line %d, column % d" +msgid "" +"\"title\", \"name\", and \"link\" elements are required at line %d, column %d" msgstr "" #: ../src/dh-parser.c:188 #, c-format -msgid "name and link elements are required inside on line %d, column %d" +msgid "" +"\"name\" and \"link\" elements are required inside on line %d, column %" +"d" msgstr "" #: ../src/dh-parser.c:268 #, c-format -msgid "name and link elements are required inside '%s' on line %d, column %d" +msgid "" +"\"name\" and \"link\" elements are required inside '%s' on line %d, column %d" msgstr "" #: ../src/dh-parser.c:281 #, c-format -msgid "type element is required inside on line %d, column %d" +msgid "\"type\" element is required inside on line %d, column %d" msgstr "" -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [vertimus] Merge uploaded file?
Em Seg, 2009-01-19 às 22:36 +0100, Claude Paroz escreveu: > Hi, > > I'd like to know your opinion about the following matter: > - Should files uploaded by translators on the Vertimus section of > l10n.gnome.org be always merged with the latest pot file? > > This would have the advantage of being able to do a better comparison > between files (same wrap policy, same line numbers, etc.) > On the downside, I'm always reluctant to modify files that claimed to be > 'owned' by a specific user. > Do you see major drawbacks to this updating? > I only see advantages. The only changes are in automatically extracted comments, which are not important if they are obsolete. I already do that (merge with latest POT) when I rview a translation (mine included. I'm not sure if you're going to use python libs or command line for that; msgmerge doesn't seem to fix the lkine lenght for PO files edited with poEdit, so you might need msgcat file.po -o file.po -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
Em Seg, 2009-01-19 às 23:14 +0100, Vincent Untz escreveu: > Le lundi 19 janvier 2009, à 19:27 +0100, Jorge González González a écrit : > > When you have a lot of people entering and leaving the team you don't > > get that consistency, since they have to learn the workflow and the > > style guides, which usually takes a while. > > I see the potential issue you're highlighting, but at least for the > french team, it was still a theoretical issue in the past few years (and > we were already using vertimus): the fact is that newcomers nearly > always ask how they can help first, and so they don't go and reserve > modules without asking. > > Now, maybe it's a real issue for another team, in which case it's > important to say that you're experiencing it :-) > When the pt_BR used a separate Vertimus server, we had some people reserving translations without even saying hello in the mailing list. Sometimes they were just curious, like the pt_BR KDE l1n coordinator, but sometimes the reserved modules for translation, or even worse, uploaded bad translations. Since we moved to the improved Damned Lies, we didn't have such problems. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[Fwd: [Bug 566454] Literal values should be kept between double quotes]
If devhelp branch gnome-2-24 is used in GNOME 2.26, is it still string freezed? Mensagem encaminhada > De: devhelp (bugzilla.gnome.org) > Para: leonar...@gnome.org > Assunto: [Bug 566454] Literal values should be kept between double > quotes > Data: Mon, 19 Jan 2009 21:17:03 + (UTC) > > If you have any questions why you received this email, please see the text at > the end of this email. Replies to this email are NOT read, please see the text > at the end of this email. You can add comments to this bug at: > http://bugzilla.gnome.org/show_bug.cgi?id=566454 > > devhelp | General | Ver: trunk > > > > > --- Comment #4 from Richard Hult 2009-01-19 21:17 UTC --- > OK. Also, as it turns out, webkit got rejected again so we are not going to > use > trunk in gnome 2.26 anyway, so we can do anything anyway... so feel free to > commit. > > Thanks! > > -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Vertimus: Upload for proofreading
Em Sáb, 2009-01-17 às 22:26 +0100, Stéphane Raimbault escreveu: > Hi, > > I've just made a diagram to explain the current Vertimus workflow and > the used terms. > > Stéphane > > PS : if useful I could add some colors to detail actions by role > (translator, reviewer, committer). Let me see if I understood the diagram correctly: Orange circles are states which can be set by translators; blue circles are states which can be set by reviewers; and green circles are states which can be set by committers. The black "None" circle is set automatically by Damned Lies / Vertimus. I'm not sure about the red color, what does it mean? There's another thing I'd like to check. When someone proofreads a translation, it should be upload for proofread by yet another reviewer? Finally, I'd like to hear definitions for "review" (as in "requiring review"), "reviewer" and "proofread". Every translation needs proofreading, which must be done by a reviewer, but if the translation needs review, any translation can review/retranslate it? -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Mangled files uploaded in vertimus
Em Qui, 2009-01-15 às 08:30 -0500, Og Maciel escreveu: > Ok, turns out the translator had added a tar.gz (or some other > combination) and the extension was changed to .po. So you can imagine > what vim would display when opening such a file. :) > Just to be sure: what do DL admins prefer, .po or .gz attachments? -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Previous msgids
Em Dom, 2009-01-11 às 18:05 +0100, Petr Kovar escreveu: > Claude Paroz , Sat, 10 Jan 2009 17:26:17 +0100: > > > Hi all, > > > > As requested by Leonardo in bug 550208 (1), damned-lies now passes the > > --previous argument to msgmerge. With the next updates you'll > > progressively see previous msgids on fuzzy entries in merged po files, > > like this: > > > > #: ../gkr/seahorse-gkr-keyring.glade.h:5 > > #, fuzzy > > #| msgid "Name" > > msgid "_Name:" > > msgstr "Nom" > > > > I hope you'll be able to take advantage of this new functionality. > > Thank you. I'm wondering whether there's any easy and straightforward way to > get the same msgmerge output when working with SVN and intltool-update? > Sorry for dumb question but still, anybody knows? > Not tested, but should work: intltool-update --pot msgmerge -U pt_BR.po seahorse.pot --previous I believe believe there's no way of "intltool-update pt_BR" work unless the intltool-update's source code is changed. If you're interested, please follow: http://bugzilla.gnome.org/show_bug.cgi?id=550208#c5 -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Please remove Slovak Team from TeamChangesState page
Em Dom, 2009-01-11 às 02:43 +0100, Marcel Telka escreveu: > Hi, > > Please remove note about possible coordinator change for Slovak team > from the http://live.gnome.org/TranslationProject/TeamChangesState page. > > Thanks. > Why not do it yourself? -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [Fwd: Previous msgids]
Em Sáb, 2009-01-10 às 20:50 +0100, Gil Forcada escreveu: > Bones, > > No us espanteu quan agafeu algun fitxer del damned-lies i veieu coses > rares :) > > Salut! > Wrong mailing list ;) > anexo mensagem de correio eletrônico, "Missatge reenviat - Previous > msgids" > > Mensagem encaminhada > > De: Claude Paroz > > Para: gnome-i18n > > Assunto: Previous msgids > > Data: Sat, 10 Jan 2009 17:26:17 +0100 > > > > Hi all, > > > > As requested by Leonardo in bug 550208 (1), damned-lies now passes the > > --previous argument to msgmerge. With the next updates you'll > > progressively see previous msgids on fuzzy entries in merged po files, > > like this: > > > > #: ../gkr/seahorse-gkr-keyring.glade.h:5 > > #, fuzzy > > #| msgid "Name" > > msgid "_Name:" > > msgstr "Nom" > > > > I hope you'll be able to take advantage of this new functionality. > > > > Claude > > > > (1) http://bugzilla.gnome.org/show_bug.cgi?id=550208 > > > > ___ > > gnome-i18n mailing list > > gnome-i18n@gnome.org > > http://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String change in mousetweaks
Em Sex, 2009-01-09 às 17:02 -0200, Leonardo F. Fontenelle escreveu: > I just committed another change to the gconf keys descriptions for the > pointer capture applet in mousetweaks. Gerd Kohlberger and I are > confident the messages should be easier to translate now. > > http://svn.gnome.org/viewvc/mousetweaks?view=revision&revision=371 > Sorry, I almost forgot to mention, after this commit I made a second commit, fixing a typo in three messages: release-button → release_button -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String change in mousetweaks
I just committed another change to the gconf keys descriptions for the pointer capture applet in mousetweaks. Gerd Kohlberger and I are confident the messages should be easier to translate now. http://svn.gnome.org/viewvc/mousetweaks?view=revision&revision=371 -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GDM trunk will be used for GNOME 2.24.
Em Sáb, 2008-09-27 às 20:07 +0200, Claude Paroz escreveu: > Le samedi 27 septembre 2008 à 14:05 -0300, Leonardo F. Fontenelle a > écrit : > > Em Seg, 2008-09-22 às 13:21 +0200, Vincent Untz escreveu: > > > > > > Note that the new GDM deprecates fast-user-switch-applet, since there's > > > an applet included with GDM now. > > > > > > > Shouldn't fast-user-switch-applet be removed from the GNOME 2.24 release > > set in Damned Lies? > > I think it's not worth removing it from 2.24, considering that some > distros might still choose gdm 2.20 with GNOME 2.24. > > We should omit it for GNOME 2.26, though. > Maybe fast-user-switch-applet should be removed now from GNOME 2.26? -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: What can Git do for translators?
Em Sex, 2009-01-09 às 03:27 +, Simos Xenitellis escreveu: > > The Translation Project (http://translationproject.org/) has (for many > years now) an automated system where you send the translation file as > an e-mail attachment and it adds it for you to a common location of > translation files. > > Something that would be desirable with GNOME translations would be to > able to make easily changes across all the translations of a language, > and then commit the files in an easy way. > In KDE, all translations for a specific language reside in a separate > directory tree, which makes it easy to make overall changes. I think > the KBabel/Lokalize tool has an option to allow to view all the > translations in a single list, so that one can identify discrepancies > in similar terms. > The same tool has an option to commit (SVN) the translations from > within the GUI. > > Reading about 'git submodule' at > http://book.git-scm.com/5_submodules.html it looks it might be good to > try this feature in order to separate the translations from the code > in each repository. > I hope the submodule feature works for us. I don't like the KDE approach (even if KDE translators don't seem to bother having scripts changing PO files in the repository), and it works best with a policy of giving SVN accounts to most regular translators (that would be circa 10 in my team). The TP-Robot approach might work most of the time, if it can receive screenshots as well. Same for an Web-based approach (e.g. Damned Lies). There are some translations which are not in PO files or in screenshots; e.g. the welcome mail in Evolution. If we get a simple "commit" interface like TP-Robot or Transifex, then we will need to decide between keeping translators with commit access or handling exceptional translations (like the welcome mail) via bug reports. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
msgctxt migration
I tried to help with the msgctxt migration, but then I found out I have no idea on how to migrate Python source code to use msgctxt. Please, if anyone knows how to, please add the information here: http://live.gnome.org/GnomeGoals/MsgctxtMigration -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: What can Git do for translators?
Em Qui, 2009-01-08 às 18:19 -0600, Federico Mena Quintero escreveu: > The "real" discussion about how the migration is being done is in > gnome-infrastructure: > http://mail.gnome.org/archives/gnome-infrastructure/2009-January/thread.html > Thanks for clarifying this. > However, I'm not 100% sure about the workflows that translators tend to > use. Do people mostly use web tools (and what happens then --- does the > tool commit for them)? Or do they checkout a whole module and simply > commit to the .po files? Or do they checkout a *single* .po file and > then commit it back, or send patches to a language coordinator? > Currently translations must be committed by translator with svn access. Adding committing capabilities in Damned Lies is somewhat in the roadmap, but currently the developers are implementing more basic features, like team management. As a translator, I just have to check out the po/ or help/ subdirs where I want to commit my translation files to. There's even a LINGUAS file in the po/ subdirs to avoid translators checking out the whole module just to edit Makefile.am. AFAIK moving to git would mean committers must checkout the whole module. If it can't be worked around, it will be a major problem for most translation teams. Brazil is not exactly a poor country, and 128kbps is still called "broadband" here. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
How to translate GTK+ 2.16 (trunk)
Moving to msgctxt [1] created approx. 300 fuzzy messages in GTK+. The GNU Gettext doesn't know about our old context hack, so when Damned Lies merged the old translations with the new POT file, most translations with context were marked as fuzzy and/or lost. This is a suggestion on how to reuse the translations in GTK+ 2.14 (from GNOME 2.24) with minimal need for manual work. This will work well only if you didn't start to translate GTK+ trunk yet. Start downloading gtk+.HEAD.ab_CD.po (I'll call it new.po for short) and gtk+.gtk-2-14.ab_CD.po (old.po). Then run: sed -i "s+msgid \"\([^|]*\)|+msgctxt \"\1\"\nmsgid \"+" old.po msgmerge -U old.po new.po Now, you should be able to finish translating "old.po" and upload it to Damned Lies as the new translation for GTK+ trunk. It worked well for me, and I hope it works for everyone in the same situation. If something looks weird or if the commands look like greek for you (no offense meant ;) ) then please check the content of old.po after every step: open it with a text editor, run "msgfmt -cvo /dev/null old.po" or open it with you favorite translation tool. 1. http://live.gnome.org/GnomeGoals/MsgctxtMigration -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: What can Git do for translators?
Em Qui, 2009-01-08 às 00:23 +0100, Axel Hecht escreveu: > Jumping in to this discussion at some random point: > > I think that DVCSes can add value to localizers. In particular for > projects that have in-development l10n, but probably for other > projects, too. > > The main value a DVCS gives to localizers is coming from exposing the > history of the original language, though. I can see good value in > exposing localizable strings to the localizer in changesets as they > were added to the original language, as they're likely going to belong > to the same context. So while going through a file of localizable > strings from top to bottom, you would have to go through several > context switches, going through the localizable strings patch-wise > might come with less contex switches. > > That of course is more of a job and an opportunity for translation > tools than anything else. > At least with GNU Gettext, running msgmerge will move translations from one line to another without hesitation, and automatic comments are always there to add noive to diffs. If any dcvs can work around this adversities, I'll defend its adoption. Today, if I need to read a diff between message catalogs, I run "msgcat file.po -o file.po" (because some translators use poEdit), then msgmerge between both of them and the same POT, or usually between the oldest and the newest (from DL), and only then I can get a readable diff. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: What can Git do for translators?
Em Ter, 2009-01-06 às 15:24 +, Simos Xenitellis escreveu: > Hi All, > > There is a discussion on the gnome developer mailing lists regarding a > possible move from Subversion (SVN) to a Distributed Version Control > System (DVCS) such as git, which is already used for the Linux kernel, > Perl, some libraries such as clutter. This post is to help contribute > to the discussion. > > [...] > As a translator I can't see any benefit in a distributed VCS. We work with _the_ version with _the_ strings; heck, we have even string freezes! Regular translators shouldn't use svn already, because damned lies realy adds value to the repository (updated message catalogs, alerts, statistics etc.). But someone must commit the translations, and that would be the team leaders and a few more translators. If damned-lies ever learns to commit translations and "translated" and other stuff, then translators shouldn't have to care about the VCS. Otherwise, I wouldn't like to have to learn git or bzr. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New damned lies thoughts
Em Ter, 2008-12-30 às 20:12 +0100, Gil Forcada escreveu: > > I really also liked the doc+ui single view rather than the split > version. Me too. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New release of Damned Lies with Vertimus included
Em Ter, 2008-12-30 às 14:58 -0300, Jonh Wendell escreveu: > Hi, Stéphane. What a great news! Many, many thanks from us, Brazilian > translators. We're using vertimus and we were looking forward to hear > this fantastic news. > I second that! -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: ChangeLog and LINGUAS consistency
Em Ter, 2008-12-09 às 17:15 +0100, Kenneth Nielsen escreveu: > 2008/12/9 Djihed Afifi <[EMAIL PROTECTED]>: > > Hello, > > > > > > 1) Currently, some modules in GNOME use a custom ChangeLog for the po > > directories. Some don't and ask NOT to introduce a Changelog entry. > > Some removed the ChangeLog file all together. > > > > I don't mind either way, but it would be nice if we had some > > consistency and enforced one way or another for all modules, as was > > done with LINGUAS. > > > > 2) A while back there was the wonderful effort to enforce LINGUAS files: > > > > http://live.gnome.org/GnomeGoals/PoLinguas > > > > I think it is time a similar file is introduced for help files - for > > the same reasons. Any comments? > > > > > > Djihed > > I second that. I would be great to have a consistent way of doing > that. Personally, as a translator/commiter, I prefer the separate > Changelog approach which, I believe, is the one most commonly used. > If there's a ChangeLog file, it must be inside the po/ or help/ or equivalent directory. I can check out automatically all the needed po/ and help/ and equivalent directories, but then having to check out the base module dir just for a Makefile.am or a ChangeLog is ridiculous. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'gnome-panel.gnome-2-24'
Em Seg, 2008-12-08 às 18:25 +0100, Frederic Peters escreveu: > GNOME Status Pages wrote: > > > This is an automatic notification from status generation scripts on: > > http://l10n.gnome.org/. > > > > There have been following string additions to module > > 'gnome-panel.gnome-2-24': > > > > + "Type a city, region, or country name and then select a > match from the pop-up." > > For the record, this is http://bugzilla.gnome.org/show_bug.cgi?id=555468 > and has been approved (Claude just told me). Shouldn't "pop-up" be replaced by "drop-down list"? (And does that need another string freeze break approval?) -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Res: Adding context information for tooltips
Gnome-i18n moderators, sorry for sending this e-mail from the wrong address before: Em Seg, 2008-12-08 às 18:42 -0200, Leonardo Ferreira Fontenelle escreveu: > Hi, Joao; hi, all! > > I agree such metadata (eg this message comes from a checkbox label) > would be very valuable. Technically I believe it should be part of the > automatic comments, leaving msgctxt for disambiguation. I'm not > confident we can expect from developers to systematically add such > comments (even the Orca develpers don't do this), but maybe Glade or > any other develpment tool could do it. Does anyone know if, and how, > coukd we get this kind of information in the translator comments? ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GNOME 2.25/2.26 on Damned Lies
Em Qui, 2008-12-04 às 01:46 -0200, Leonardo F. Fontenelle escreveu: > Em Seg, 2008-11-10 às 13:20 +0100, Claude Paroz escreveu: > > As a first step, I implemented an XML and a JSON output of the release > > list: > > > > http://l10n.gnome.org/releases/xml > > http://l10n.gnome.org/releases/json > > > > Is this a good direction? > > > > I'm very sorry for not noticing your reply before. I see releases.xml > was substituted by releases/xml, and recently you reintroduced the > releases XML files (e.g. gnome-2-26.xml) for Vertimus. After a minor > fixes, my scripts should start working again. Thanks! > Actually, I did need the old releases.xml; the review script used it to discover which release was the translation from. I was going to ask you to create it back, but then I decided to make the script discover the correct PO file URL in DL without parsing any metadata from the web. The result is a new review script, which I just uploaded to http://live.gnome.org/TranslationProjects/Scripts. The bad news is that the code had to be adjusted for a lot of quirks, which is means it's less future-proof and harder to maintain. The good news is that the script is faster (because it doesn't download the XML files) and doesn't depend on xmlstarlet anymore. The script was extensively tested, and so I hope it works out-of-the-box for everyone (even more than the previous version). -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GNOME 2.25/2.26 on Damned Lies
Em Seg, 2008-11-10 às 13:20 +0100, Claude Paroz escreveu: > As a first step, I implemented an XML and a JSON output of the release > list: > > http://l10n.gnome.org/releases/xml > http://l10n.gnome.org/releases/json > > Is this a good direction? > I'm very sorry for not noticing your reply before. I see releases.xml was substituted by releases/xml, and recently you reintroduced the releases XML files (e.g. gnome-2-26.xml) for Vertimus. After a minor fixes, my scripts should start working again. Thanks! -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Localizing the firefox extension
I believe I can contribute with instructions for translators on how to localize (translate) Beagle's Firefox extension in a more familiar way (from .dtd/.properties to .po and back). Where should I place this instructions: in GNOME's wiki, in Beagle's wiki, or in firefox-extension/chrome/locale/? http://svn.gnome.org/viewvc/beagle/trunk/beagle/firefox-extension/chrome/locale/ -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: How to find where the string is from?
Em Seg, 2008-11-10 às 00:13 +0100, Yannig MARCHEGAY escreveu: > So gedit uses KDE translations, I wouldn't have imagined that :p > Thanks a lot, I know have to find a way to install kbabel to edit > their po files (sudo apt-get install kbabel just does not work since I > installed Intrepid). > No, it doesn't. It uses "iso-codes", a package developed at Debian and largely reused by other software like Gedit to display translated country, language and currency names: http://pkg-isocodes.alioth.debian.org/ Look here and you'll get yet another Franchimand: http://svn.debian.org/wsvn/pkg-isocodes/trunk/iso-codes/iso_639/oc.po?op=file&rev=0&sc=0 -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: How to find where the string is from?
Em Dom, 2008-11-09 às 23:57 +0100, Yannig MARCHEGAY escreveu: > Hello everybody, > > I'm translating GNOME into Occitan and I'm quite alone to do it. Now, > I'm using it "normally" and I translate in priority the English > strings that remain in what I see. Recently, I saw a mistranslation in > the languages (French, Spanish, etc., not PHP, ASP, etc.) shown when > defining the doc language in gedit. That mistranslation is > "Franchimand" but no way to find it in the langpack. > My question is then "how can I know where a string is from in order to > translate it or correct it?" > If you know the translation error is in a package which you have installed in your system, you can run: fgrep "Franchimand" /usr/share/oc/LC_MESSAGES/*.mo (BTW, thanks for the tip, Thomas.) -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Merging translation from gnome-build to anjuta
Em Dom, 2008-11-09 às 14:18 +0100, Johannes Schmid escreveu: > Hi! > > We plan to drop the gnome-build module soon and merge it's code into the > anjuta codebase. (You will get a notice when this happens.) > > The problem is that I don't know how to merge the translations from > gnome-build to anjuta. Most teams have a quite complete translation of > gnome-build and we don't want to loose that once the code files are > moved. > > Does anyone have an idea (or script) that can do that? > msgcat gnome-build.po anjuta.po -o anjuta.po This command will yield weird headers, which most translators will never have seen, e.g.: # #-#-#-#-# pt_BR.po (gnome-build) #-#-#-#-# # Brazilian Portuguese translation of gnome-build # Copyright (C) 2002,2003 Free Software Foundation, Inc. # This file is distributed under the same license as the gnome-build package. # Alexandre Folle de Menezes <[EMAIL PROTECTED]>, 2002. # David Barzilay <[EMAIL PROTECTED]>, 2003. # Afonso Celso Medina <[EMAIL PROTECTED]>, 2005 # Raphael Higino <[EMAIL PROTECTED]>, 2005. # Afonso Celso Medina <[EMAIL PROTECTED]>, 2008. # # # #-#-#-#-# pt_BR.po (Anjuta) #-#-#-#-# # Brazilian Portuguese translation of Anjuta. # Copyright (C) 2001-2003, 2004, 2005 Free Software Foundation, Inc. # This file is distributed under the same license as the anjuta package. # based on the GNOME 2.2 translation to Portuguese (pt) by # Marcelo Elias Del Valle <[EMAIL PROTECTED]>, 2002. # Duarte Loreto <[EMAIL PROTECTED]>, 2001, 2002, 2003. # # Alexandre Folle de Menezes <[EMAIL PROTECTED]>, 2003, 2004. # Afonso Celso Medina <[EMAIL PROTECTED]>, 2004, 2005. # Airton Arantes <[EMAIL PROTECTED]>,2007. # Rodrigo Flores <[EMAIL PROTECTED]>, 2007. # Jonh Wendell <[EMAIL PROTECTED]>, 2008. # Leonardo Ferreira Fontenelle <[EMAIL PROTECTED]>, 2008 # #, fuzzy msgid "" msgstr "" "#-#-#-#-# pt_BR.po (gnome-build) #-#-#-#-#\n" "Project-Id-Version: gnome-build\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2008-06-26 15:01-0300\n" "PO-Revision-Date: 2008-06-26 15:00-0300\n" "Last-Translator: Jonh Wendell <[EMAIL PROTECTED]>\n" "Language-Team: Portuguese/Brazil <[EMAIL PROTECTED]>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "#-#-#-#-# pt_BR.po (Anjuta) #-#-#-#-#\n" "Project-Id-Version: Anjuta\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2008-09-27 03:18+\n" "PO-Revision-Date: 2008-09-14 21:45-0300\n" "Last-Translator: Leonardo Ferreira Fontenelle <[EMAIL PROTECTED]>\n" "Language-Team: Brazilian Portuguese <[EMAIL PROTECTED]" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n != 1)\n" But this is good because it will let each team manually merge the translation credits. Currently there are 12 messages which are identical between Anjuta and GNOME Build. If one or more of those messages are currently translated differently, the output of that command will include fuzzy messages, like: #, fuzzy msgid "General" msgstr "" "#-#-#-#-# anjuta.po (Anjuta) #-#-#-#-#\n" "BBB\n" "#-#-#-#-# gnome-build.po (gnome-build) #-#-#-#-#\n" "AAA" Most translators will never have seen this before, so translation team coordinators will have to tell their own teams about what to do with these messages. There is another way, but I don't recommend it: msgmerge gnome-build.po new-anjuta.pot -C anjuta.po -o anjuta.po Instead of marking incoherent translations as fuzzy, this command would adopt the gnome-build version, even in the message catalog header and header comments. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GNOME 2.25/2.26 on Damned Lies
Em Dom, 2008-11-09 às 00:07 +0100, Claude Paroz escreveu: > Le samedi 08 novembre 2008 à 10:09 -0200, Leonardo F. Fontenelle a > écrit : > > > > Djamned Lies seems faster than Damned Lies :) > > > > Replacing the XML files for a database had a collateral effect for me, > > though. My pet scripts "tsfx" and "review" relied on those XML files to > > find out if updating a po/ or help/ was just a matter of "svn up" or if > > there was a branch and thus the correct command would be "svn sw". > > > > Is there any way to get data from this database using a remote computer? > > We should be able to produce any output you want. > Ideally, what data and in which format would you like to have ? > I'd like to know: 1. the list of release sets; 2. the list of modules for each release; 3. the branch for each module; 4. the list of domains and docs for each module; 5. the svn path for each domain/doc. A XML file would be fine (thanks for the tip, Shaun McCance). If by any chance you can fit that data in plain text tables, that would be nice, too. Thanks! -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GNOME 2.25/2.26 on Damned Lies
Em Sáb, 2008-11-08 às 10:32 +0100, Claude Paroz escreveu: > > We finally switched to the new app as the main Damned Lies a little > sooner than planned, because the update process did not support well too > apps in parallel. > > Feel free to report bugs, and I'll try to be as responsive as possible > in the next days. > > Thanks to Olav for the sysadmin work. > Djamned Lies seems faster than Damned Lies :) Replacing the XML files for a database had a collateral effect for me, though. My pet scripts "tsfx" and "review" relied on those XML files to find out if updating a po/ or help/ was just a matter of "svn up" or if there was a branch and thus the correct command would be "svn sw". Is there any way to get data from this database using a remote computer? -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Some useful scripts
Short story: You should try the script now. Long story: The October 21 version was a reply to your report. You and Vladimir Melo were experiencing opposite issues, to I made the script try both "xml" and "xmlstarlet" binaries, and use whatever it finds. But while doing that I made a silly mistake, and a few hours ago I fixed it. BTW: nice to see you around. Em Sáb, 2008-10-25 às 21:23 -0300, Fabrício Godoy escreveu: > Is this a reply to my report? > > 2008/10/25 Leonardo F. Fontenelle <[EMAIL PROTECTED]> > Just updated the "review" script in the wiki to fix a syntax > bug. > > Em Ter, 2008-10-21 às 16:53 -0200, Leonardo F. Fontenelle > escreveu: > > > > > Today I uploaded new versions of the "review" and "zzgrep" > scripts: > > > > http://live.gnome.org/TranslationProject/Scripts > > > > The first one was reworked to be useful for regular > translators as well. > > If the file name is descriptive (e.g., > evince.HEAD.pt_BR.po), then > > script won't depend on subversion to help you review the > translation. > > Subversion users should run the script without specifying > the file name, > > as before. The script is quite mature, and has even a > workaround for > > differences between GNU/Linux distributions! The pt_BR l10n > team is > > using it in the last weeks, and I'd like other teams to try > it too. > > > > "zzgrep" is more specific, but may be of someone else's > interest. It's > > used to verify terminology compliance across many > translations of a > > single locale. Please refer to the scripts page for more > information. In > > case you remember the previous version, the new feature is > that you can > > specify a regular expression for the translated message as > well, so that > > only messages *without* the regular expression in the > translated message > > will be marked as fuzzy. > > > > I apologize for "tsfx". The script is very nice, but I > couldn't sit down > > and write the --help yet. People who tried it said it's much > more robust > > than svn-checkout_l10n... Please read this email, and try > the script as > > described or with the --usage option. If you have an SVN > account, please > > run ssh-add before running the script. > > > > > http://mail.gnome.org/archives/gnome-i18n/2008-August/msg00221.html > > > > PS: I didn't forget what I said about not reading the > mailing list for a > > few weeks. > > -- > Leonardo Fontenelle > http://leonardof.org > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n > > -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Some useful scripts
Just updated the "review" script in the wiki to fix a syntax bug. Em Ter, 2008-10-21 às 16:53 -0200, Leonardo F. Fontenelle escreveu: > > Today I uploaded new versions of the "review" and "zzgrep" scripts: > > http://live.gnome.org/TranslationProject/Scripts > > The first one was reworked to be useful for regular translators as well. > If the file name is descriptive (e.g., evince.HEAD.pt_BR.po), then > script won't depend on subversion to help you review the translation. > Subversion users should run the script without specifying the file name, > as before. The script is quite mature, and has even a workaround for > differences between GNU/Linux distributions! The pt_BR l10n team is > using it in the last weeks, and I'd like other teams to try it too. > > "zzgrep" is more specific, but may be of someone else's interest. It's > used to verify terminology compliance across many translations of a > single locale. Please refer to the scripts page for more information. In > case you remember the previous version, the new feature is that you can > specify a regular expression for the translated message as well, so that > only messages *without* the regular expression in the translated message > will be marked as fuzzy. > > I apologize for "tsfx". The script is very nice, but I couldn't sit down > and write the --help yet. People who tried it said it's much more robust > than svn-checkout_l10n... Please read this email, and try the script as > described or with the --usage option. If you have an SVN account, please > run ssh-add before running the script. > > http://mail.gnome.org/archives/gnome-i18n/2008-August/msg00221.html > > PS: I didn't forget what I said about not reading the mailing list for a > few weeks. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Some useful scripts
Em Ter, 2008-09-02 às 02:06 -0300, Leonardo F. Fontenelle escreveu: > > I just created the TranslationProject/Scripts page and added "review", a > reworked version of "zzpo". Usage is very simple: checkout the po/ or > help/ dir, make local changes (translate, or download a translation you > want to review), then run the script without arguments. It's a very good > companion to the "tsfx" script I attached to a previous email. With them > you don't need to checkout the entire module and run 'intltool-update': > you can use damned-lies' message catalogs. > Today I uploaded new versions of the "review" and "zzgrep" scripts: http://live.gnome.org/TranslationProject/Scripts The first one was reworked to be useful for regular translators as well. If the file name is descriptive (e.g., evince.HEAD.pt_BR.po), then script won't depend on subversion to help you review the translation. Subversion users should run the script without specifying the file name, as before. The script is quite mature, and has even a workaround for differences between GNU/Linux distributions! The pt_BR l10n team is using it in the last weeks, and I'd like other teams to try it too. "zzgrep" is more specific, but may be of someone else's interest. It's used to verify terminology compliance across many translations of a single locale. Please refer to the scripts page for more information. In case you remember the previous version, the new feature is that you can specify a regular expression for the translated message as well, so that only messages *without* the regular expression in the translated message will be marked as fuzzy. I apologize for "tsfx". The script is very nice, but I couldn't sit down and write the --help yet. People who tried it said it's much more robust than svn-checkout_l10n... Please read this email, and try the script as described or with the --usage option. If you have an SVN account, please run ssh-add before running the script. http://mail.gnome.org/archives/gnome-i18n/2008-August/msg00221.html PS: I didn't forget what I said about not reading the mailing list for a few weeks. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gnome-applets string pseudo-changes in 2.24
Em Sex, 2008-10-17 às 23:52 +1300, Callum McKenzie escreveu:
> Callum McKenzie wrote:
> >
> > svn diff -r\{20070101\} pt_BR.po | grep -B3 \\.glade | less
> >
> Sorry, that should be:
>
> svn diff -r\{20070101\} pt_BR.po | grep -A3 \\.glade | less
>
> (the =B3 becomes -A3)
>
> For languages other than pt_BR, just change the language code.
>
> - Callum
>
>
Thank you very much, and sorry for spaming the wrong person.
After looking at you suggestion, I found this option useful, too:
svn cat -r\{20070101\} pt_BR.po > pt_BR.po.20070101
(Download gnome-applets.gnome-2-24.pt_BR.po from l10n.gnome.org)
msgmerge -U pt_BR.po gnome-applets.gnome-2-24.pt_BR.po -C pt_BR.po.20070101
gedit pt_BR.po &(replace with prefered PO file editor)
diff -u gnome-applets.gnome-2-24.pt_BR.po pt_BR.po | less
--
Leonardo Fontenelle
http://leonardof.org
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gnome-applets string pseudo-changes in 2.24
Davyd, this bug fix will give a lot of work to the pt_BR l10n team, and possibly to other teams as well. Please make the 2.14.1 tarball as close to the deadline as possible. Thanks in advance! Em Sex, 2008-10-17 às 12:42 +1300, Callum McKenzie escreveu: > I have just added explicit type annotations for the GtkBuilder files to > the gnome-applets POTFILES.in in the gnome-2-24 branch. This will mean > that strings will be marked for translation in the GtkBuilder files that > may not have been previously. All the strings were previously in .glade > files and should be unchanged from the 2.22 release so hopefully > translations are already available. > > I apologise for any inconvenience this may cause, but it is necessary to > avoid untranslated menus. See bug 555656 for details. > > - Callum > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Semi vacations
During the days October 21 to December 1st I'll be partially unavailable to GNOME translation, because of some graduate dissertation deadlines [1]. During this period, I'll stop reading mailing lists but will continue to read private mail. Anyone is more than welcome to email me as usual, no need to think twice. I don't think it will be necessary to indicate a substitute, because the Brazilian Portuguese GNOME translation team (which I coordinate) has other committers and enough skilled translators. I'll be around until the release of GNOME 2.24.1, so you'll have to bare me a little more ;) 1. If you are from Latin America or the Iberic Peninsule, read: http://www.gnome.org/~csaavedra/news-2007-10.html#D06 -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'epiphany.gnome-2-24'
Em Seg, 2008-10-13 às 00:57 +, GNOME Status Pages escreveu: > This is an automatic notification from status generation scripts on: > http://l10n.gnome.org/. > > There have been following string additions to module 'epiphany.gnome-2-24': > > + "Cannot Load Document While Working Offline" > + "Cannot load document while working offline." > > Note that this doesn't directly indicate a string freeze break, but it > might be worth investigating. Diego, your commit broke a string freeze: http://svn.gnome.org/viewvc/epiphany?view=revision&revision=8580 It is evident from the URL that you were carreful enough to fix message catalogs as well, so that virtually no translation team will get hurt. But it's still an unapproved string freeze break... We (translators) were just discussing communication issues between develpers and translators in this release cycle. http://live.gnome.org/TranslationProject/HandlingStringFreezes -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GNOME 2.24: Worst release cycle I have been a part of [l10n/i18n]
I agree that translating GNOME 2.24 was harder than usual, but that is a consequence of overall improvements in GNOME. The large number of new messages in libgweather-locations, for instance, is a collateral effect of an enhanced internationalization feature. I really want Brazilian cities, for instance, to be available in the locations list. As Claudio Saavedra said, the development cycles have been hard to developers as well. Remember that GVFS almost didn't get FTP support in time for GNOME 2.22! I believe Glade was worst than GDM in this development cycle, from the translators' point of view. We only discovered *by accident* we should be translating branch gnome-2-22, when a string change was made after the string freeze. The GDM version, in contrast, was informed in the last minute just because the developers and the release team didn't know it, too, until that moment. I agree a quoting style would be desirable, even if I don't have the time to do that outside the scope of my translation team's work. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'seahorse.HEAD'
Em Dom, 2008-10-12 às 03:10 +, GNOME Status Pages escreveu:
> This is an automatic notification from status generation scripts on:
> http://l10n.gnome.org/.
>
> There have been following string additions to module 'seahorse.HEAD':
>
> + "Are you sure you want to delete %d passwords?"
> + "Are you sure you want to delete the password '%s'?"
>
> Note that this doesn't directly indicate a string freeze break, but it
> might be worth investigating.
Thank you, Adam!
_If you get approval_, you might use something like this pseudocode:
if number==1
string=printf(_("Are you sure you want to delete the password '%s'?"),
name)
else
string=printf(N_("Are you sure you want to delete %d password?", "Are
you sure you want to delete %d passwords?", number), number)
fi
It doesn't make much sense in English (or in Portuguese), but I hope it
helps for languages with more than two plural forms.
--
Leonardo Fontenelle
http://leonardof.org
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'seahorse.HEAD'
Actually, this string change is not the fix for bug #554937; it's the fix for bug #554933. This is a string change. My email archive and I don't recall any string freeze break request from seahorse. Worse, translationg this message makes msgfmt find a fatal error, which means the module probably can't be built: #: ../gkr/seahorse-gkr-commands.vala:63 #, c-format msgid "Are you sure you want to delete the password '%s'?" msgid_plural "Are you sure you want to delete %d passwords?" msgstr[0] "Você tem certeza de que deseja excluir a senha \"%s\"?" msgstr[1] "Você tem certesa de que deseja excluir %d senhas?" msgfmt output: 515: format specifications in 'msgid' and 'msgstr[0]' for argument 1 are not the same msgfmt: found 1 fatal error Adam, please revert the following commit: http://svn.gnome.org/viewvc/seahorse?view=revision&revision=2574 And: 1. Ask for aproval (if it wasn't given yet); and 2. Find a solution which makes gettext happy. Em Sáb, 2008-10-11 às 20:59 +, GNOME Status Pages escreveu: > This is an automatic notification from status generation scripts on: > http://l10n.gnome.org/. > > There have been following string additions to module 'seahorse.HEAD': > > + "Are you sure you want to delete the password '%s'?"/"Are you sure you > want to delete %d passwords?" > > Note that this doesn't directly indicate a string freeze break, but it > might be worth investigating. > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'seahorse.HEAD'
Em Sáb, 2008-10-11 às 20:59 +, GNOME Status Pages escreveu: > This is an automatic notification from status generation scripts on: > http://l10n.gnome.org/. > > There have been following string additions to module 'seahorse.HEAD': > > + "Are you sure you want to delete the password '%s'?"/"Are you sure you > want to delete %d passwords?" > > Note that this doesn't directly indicate a string freeze break, but it > might be worth investigating. This is not a string freeze break. These messages were previously excluded from the message catalog by accident, and were reintroduced as a bug fix. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
How to merge translations from Glade 3 trunk and gnome-2-22
The pt_BR GNOME l10n team did some terminology fixes for Glade 3, and with the last minute change from trunk to gnome-2-22 we sort of lost them. Even worse, I committed other terminoly fixes to the gnome-2-22, before importing the previous fixes from trunk. This is how I managed to merge the fixes from the two branches; I hope these steps are useful for other teams as well. First, check out the glade3/gnome-2-22/po dir as usual. Run "svn info pt_BR.po" to see the SVN URL for that file (change pt_BR for your locale code, of course). Now run "svn cat ANOTHER_URL > pt_BR.po.trunk", where ANOTHER_URL is the same URL as in the output of "svn info", but replacing "branches/gnome-2-22/" with "trunk/". Now you have the two versions in you hard disc, but merging them won't be easy yet. Run "msgmerge -U pt_BR.po.trunk pt_BR.po", which will make pt_BR.po.trunk have the same original messages and "#. " lines as pt_BR.po, making the diff much easier to read. Now you can use meld or any other tool to "cherry-pick" fixes from trunk to gnome-2-22. Update the ChangeLog and commit as usual. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GDM trunk will be used for GNOME 2.24.
Em Seg, 2008-09-22 às 13:21 +0200, Vincent Untz escreveu: > > Note that the new GDM deprecates fast-user-switch-applet, since there's > an applet included with GDM now. > Shouldn't fast-user-switch-applet be removed from the GNOME 2.24 release set in Damned Lies? -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Licenses of .po files, and translations
Em Seg, 2008-09-22 às 10:53 +0200, Gudmund Areskoug escreveu: > > It is/may be derivative work, but the copyright to a translation belongs > to the translator by default. > > Since it is or may be derivative, the translator mostly can't do > whatever she likes with the translation, but nobody else can do anything > with the translation unless the translator says so. > If it's derivative work, it's copyrighted by the translators as well as those who wrote the strings in the source code. And if it's derivative work from GPL'ed software, it's GPL'ed as well. But it's simpler to say "under the same license as the ... package." -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Strange markup in message catalog for Rhythmbox
Em Dom, 2008-09-21 às 09:26 -0400, Og Maciel escreveu: > > Today I noticed a strange "?" character showing up in the place where > one usually see the location of a string in the source code: > > #. ? > #: ../backends/gstreamer/rb-player-gst-xfade.c:2583 > #, c-format > msgid "Failed to open output device" > msgstr "Falha ao abrir o dispositivo de saída" > > [...] > Most probably those are comments in the source code, not meant for us translators. They ended up in the message catalog just because they were adjacent to strings marked for translation. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: ikedjane tamazight ISO 639-3 :tzm
Em Sáb, 2008-09-20 às 15:05 +0100, khaled habhoub escreveu: > khaled habhoub > e-mail: [EMAIL PROTECTED] > Bugzilla account: [EMAIL PROTECTED] > language: Central Atlas Tamazight ISO 639-3:tzm > mailing list: [EMAIL PROTECTED] > team web: gnome.ikedjane.tk > Welcome! I guess you are providing information to start a new GNOME translation team. Would you please say that in English? (Subject included.) -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: wrong translations of string "Rule" in gtkhtml
Em Qui, 2008-09-11 às 00:45 +0200, Andre Klapper escreveu: > Am Mittwoch, den 10.09.2008, 09:08 -0300 schrieb Leonardo F. Fontenelle: > > Even worse: it seems that providing a patch makes a lot of difference in > > having the bug fixed. Those issues should be trivial to fix for > > developers and yet very important for translators, but sometimes were > > are left without a reply for months (or years). Providing a patch means > > that a translator must learn SVN, check out the source code, and > > actually read and try to understand it. Does anyone here think it is > > reasonable to expect this from a translator? > > [...] > > Creating a patch is mostly trivial, so I wonder whether adding the > gnome-love keyword would help us in getting more such patches from "code > beginners" that are willing to help improving gnome but search for a > place to start. > I loved the idea! -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: wrong translations of string "Rule" in gtkhtml
Em Qua, 2008-09-10 às 10:13 +0300, Александър Шопов escreveu: > > Again, I don't understand why there hasn't been already a bug report > > about this. > Because it is a hassle to bother to file a bug report? > I agree it's a hassle to file a bug report, specially when you have to stop your "batch mode" (to quote Knuth[1]). And I agree these bug reports are very important for us to translate correctly. Even worse: it seems that providing a patch makes a lot of difference in having the bug fixed. Those issues should be trivial to fix for developers and yet very important for translators, but sometimes were are left without a reply for months (or years). Providing a patch means that a translator must learn SVN, check out the source code, and actually read and try to understand it. Does anyone here think it is reasonable to expect this from a translator? 1. http://www-cs-faculty.stanford.edu/~knuth/email.html -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: wrong translations of string "Rule" in gtkhtml
Em Ter, 2008-09-09 às 21:41 +0200, Andre Klapper escreveu: > One thing I've seen while taking a quick look at translation files of > other languages: > > #: ../components/editor/gtkhtml-editor.glade:44 > msgid "Rule Properties" > #: ../components/editor/gtkhtml-editor-actions.c:1774 > msgid "Insert Rule" > #: ../components/html-editor/GNOME_GtkHTML_Editor-emacs.xml.in.h:135 > #: ../components/html-editor/GNOME_GtkHTML_Editor.xml.in.h:135 > #: ../components/html-editor/html-editor-control.xml.h:30 > msgid "_Rule..." > #: ../components/html-editor/popup.c:475 > msgid "Rule Style..." > > There seem to be quite a few languages translating this wrong, e.g. > Norwegian and Spanish? (No, I don't speak every language in the world, > hence I didn't check all of them and I may be wrong ;-). > "Rule" refers to a line, like in HTML (horizontal rule). > This is NOT a rule in the sense of obeying, following, or filtering messages. > > Please check your gtkhtml translations, as this is quite visible in the > main menu of the mail composer. > I've filed http://bugzilla.gnome.org/show_bug.cgi?id=551554 . > Thank you, pt_BR translation is wrong too. Filed a bug for myself: http://bugzilla.gnome.org/show_bug.cgi?id=551590 -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Some useful scripts
Em Ter, 2008-09-02 às 02:06 -0300, Leonardo F. Fontenelle escreveu: > > I just created the TranslationProject/Scripts page and added "review", a > reworked version of "zzpo". Usage is very simple: checkout the po/ or > help/ dir, make local changes (translate, or download a translation you > want to review), then run the script without arguments. It's a very good > companion to the "tsfx" script I attached to a previous email. With them > you don't need to checkout the entire module and run 'intltool-update': > you can use damned-lies' message catalogs. > In case anyone is trying the "review" script, I'd like to say I just updated the file in GNOME Live. I fixed the first pair of XPath's, so that it should work for everything. (The 3 xpaths in the script were harder for me to write than all the rest of the script!) And now the script is a little less verbose. As a side effect of the default settings of the script, I started using gedit more frequently to edit message catalogs. I recommend that everyone tries gedit-pomode 0.16. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'seahorse.HEAD'
Those messages are already present in the Seahose PO file. Most probably a damned-lies issue. Em Dom, 2008-09-07 às 12:48 +, GNOME Status Pages escreveu: > This is an automatic notification from status generation scripts on: > http://l10n.gnome.org/. > > There have been following string additions to module 'seahorse.HEAD': > > + "Are you sure you want to delete %d passwords?" > + "Are you sure you want to delete %d secure shell keys?" > + "Are you sure you want to delete the password '%s'?" > + "Are you sure you want to delete the secure shell key '%s'?" > + "Are you sure you want to permanently delete %d identities?" > + "Are you sure you want to permanently delete %d keys and identities?" > + "Are you sure you want to permanently delete %d keys?" > + "Are you sure you want to permanently delete %s?" > + "Certificate" > + "Close this program" > + "Close this window" > + "Collapse all listings" > + "Configure Key for _Secure Shell..." > + "Couldn't import keys" > + "Create a new personal key" > + "Expand all listings" > + "Exporting is not yet supported." > + "Filter:" > + "Import keys from the clipboard" > + "Import keys into your key ring from a file" > + "Import selected keys to local key ring" > + "Imported keys" > + "Importing keys from key servers" > + "Importing keys" > + "Invalid or unrecognized object." > + "Loading..." > + "Paste _Keys" > + "Publish and/or synchronize your keys with those online." > + "Remote Keys Containing '%s'" > + "Remote Keys" > + "Search for keys on a key server" > + "Selected %d key"/"Selected %d keys" > + "Send public Secure Shell key to another machine, and enable logins > using that key." > + "Show expiry column" > + "Show owner trust column" > + "Show type column" > + "Show validity column" > + "Sign public key" > + "T_ypes" > + "Unrecognized key type, or invalid data format" > + "Used to access other computers (eg: via a terminal)" > + "Used to encrypt email and files" > + "X509 Certificate" > + "_Close" > + "_Collapse All" > + "_Create New Key..." > + "_Expand All" > + "_Expiry" > + "_Find Remote Keys..." > + "_Import..." > + "_Quit" > + "_Remote" > + "_Sign Key..." > + "_Sync and Publish Keys..." > + "_Trust" > + "_Validity" -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: conduit branched for 2.24
CC'ing the epyphany-extensions maintainer, as this module has a similar situation. Em Dom, 2008-09-07 às 11:05 +0100, John Carr escreveu: > [...] > > Which branch is normally shown on gnome-extras? If its normally a > stable branch, then gnome-2-24, otherwise trunk... Usually it's trunk, because most modules in gnome-extras don't have any branch. Epiphany Extensions does have a gnome-2-24 branch, but trunk is being shown in the gnome-extras page. When GNOME 2.24.0 is released, many languages will not have translated conduit (or epiphany-extensions) yet. Then the teams will have some months to complete the UI translation and start translating the documentation. As a translator, I'd prefer to have the gnome-2-24 branch exposed in l10n.gnome.org, at least until GNOME 2.24.3 is released. Then I'd rather have branch exposed, to start working on GNOME 2.26. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: how to get more translators involved
Em Sex, 2008-09-05 às 22:16 +0200, Sven Neumann escreveu: > Hi, > > I would like to see the quality of the GIMP translations improved. Quite > a few languages have not been updated in a while and need to be > completed for the 2.6 release. So I would like to invite our users to > help with the translations. But I wonder how I could best do this > without stepping on the toes of the translation teams. > > Should I ask interested users to contact the translation team of their > language (using http://l10n.gnome.org/languages/)? Or should I ask them > to download the po files from http://l10n.gnome.org/module/gimp and > start to work on them? How could they contribute their work? By opening > a bug report against the l10n product in Bugzilla and attaching the po > file there? Is there a translators guide that I can point potential > contributors to? > All team leaders are subscribed to the mailing list, so you should consider you message delivered. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[Fwd: Re: Doc translation stat on Damed Lies]
Sorry, I used the wrong e-mail address by accident. Mensagem encaminhada > De: Leonardo Fontenelle <[EMAIL PROTECTED]> > Para: Theppitak Karoonboonyanan <[EMAIL PROTECTED]> > Cc: gnome-i18n > Assunto: Re: Doc translation stat on Damed Lies > Data: Wed, 03 Sep 2008 01:43:12 -0300 > > Em Qua, 2008-09-03 às 11:30 +0700, Theppitak Karoonboonyanan escreveu: > > Hello, > > > > I have tried a first Thai translation for gnome-netstatus help and > > committed it yesterday. But it has not appeared on Damed Lies > > stat till now. I wonder if I have missed anything. What I have done > > were: > > - Added th to DOC_LINGUAS in help/Makefile.am > > - Added th/th.po under help/ > > - No th/figures/ was added, since the figures need no localization > > > > I just checked, and now the Thai translation is shown. Damned Lies > updates fast, but it's not instant :) > -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Some useful scripts
Em Ter, 2008-08-12 às 18:10 +0200, Christian Rose escreveu: > On 8/12/08, Leonardo F. Fontenelle <[EMAIL PROTECTED]> wrote: > > Em Seg, 2008-08-11 às 15:46 +0200, Gil Forcada escreveu: > > > To ease my translation/revision workflow I have made some small bash > > > scripts that I'm attaching if anyone things they are useful :) > > > > I got a few of them too, so I'll post them here. > > All sounds really useful, so feel free to put them somewhere on the > http://live.gnome.org/ wiki and link to them from > http://live.gnome.org/TranslationProject/. A > http://live.gnome.org/TranslationProject/Scripts page would perhaps > make sense... > > In any case, having them in the wiki will probably mean that they are > more easily findable instead of having to search in mailing list > archives. > I just created the TranslationProject/Scripts page and added "review", a reworked version of "zzpo". Usage is very simple: checkout the po/ or help/ dir, make local changes (translate, or download a translation you want to review), then run the script without arguments. It's a very good companion to the "tsfx" script I attached to a previous email. With them you don't need to checkout the entire module and run 'intltool-update': you can use damned-lies' message catalogs. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Reporting bugs against gnome-packagekit
Sorry, I meant to forward this information to a Portuguese-speaking mailing list. Em Seg, 2008-09-01 às 09:45 -0300, Leonardo F. Fontenelle escreveu: > (Boas) notícias da gnome-i18n@gnome.org: > > Em Seg, 2008-09-01 às 12:16 +0200, Stéphane Raimbault escreveu: > > > > I hope Transifex will be usable for the GNOME project in a few months > > (for all modules with a nice [D]VCS layer). > > We're currently working to integrate Vertimus/Damned-Lies into > > Transifex. Our goal is to replace Damned-Lies (l10n.gnome.org) by a > > Transifex on steroid. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Reporting bugs against gnome-packagekit
(Boas) notícias da gnome-i18n@gnome.org: Em Seg, 2008-09-01 às 12:16 +0200, Stéphane Raimbault escreveu: > > I hope Transifex will be usable for the GNOME project in a few months > (for all modules with a nice [D]VCS layer). > We're currently working to integrate Vertimus/Damned-Lies into > Transifex. Our goal is to replace Damned-Lies (l10n.gnome.org) by a > Transifex on steroid. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String change in GtkHtml
GtkHtml now has three more fuzzy messages. They had context information
with Q_("|"), and now they use C_("",""). So, we just have to mark the
fuzzy strings back as translated. But there are new translator comments
as well, so you might want to read them for safety ;)
http://svn.gnome.org/viewvc/gtkhtml?view=revision&revision=8943
http://bugzilla.gnome.org/show_bug.cgi?id=549235
--
Leonardo Fontenelle
http://leonardof.org
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: ChangeLog (or lack of it)
Em Sáb, 2008-08-30 às 23:55 +0100, Philip Withnall escreveu: > You could look at the svn log and see if the last commit changed a > ChangeLog file. If the ChangeLog's in use, *all* commits should change > it. > Same as with the other suggestions. If someone recently wrote to the ChangeLog by accident, there will be recent changes even if the ChangeLog is depracated. And yes, it does happen :) -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: ChangeLog (or lack of it)
Em Sáb, 2008-08-30 às 23:25 +0100, Rui Gouveia escreveu: > Wouter Bolsterlee wrote: > > 2008-08-30 klockan 23:51 skrev Leonardo F. Fontenelle: > > > >> Not much; the ChangeLog usually exists, but with a message telling us > >> not to change it. If at least there was an standard for that message, we > >> could reliably automate the check. > >> > > > > Perhaps grepping for "^200" helps? If there is a line starting with "200" it > > is likely to be a real ChangeLog file with timestamps. > > > If you grep the last date used > > $ head -n 1 ChangeLog | cut -d' ' -f1 > 2008-08-30 > > you can calculate how many days have elapsed since then, you can decide > that if not updated for X days, it's obsolete. > If a translator accidentally (eg. with a script) used the ChangeLog in the usual way, there can be recent dates even if the ChangeLog is deprecated. In fact, when a module (e. g. empathy) deprecates a ChangeLog, it *removes* old content, so all dates will be new. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: ChangeLog (or lack of it)
Em Sáb, 2008-08-30 às 23:56 +0200, Wouter Bolsterlee escreveu: > 2008-08-30 klockan 23:51 skrev Leonardo F. Fontenelle: > > Not much; the ChangeLog usually exists, but with a message telling us > > not to change it. If at least there was an standard for that message, we > > could reliably automate the check. > > Perhaps grepping for "^200" helps? If there is a line starting with "200" it > is likely to be a real ChangeLog file with timestamps. > Frequently the ChangeLog should not be written to, but a few translators (and their scripts, obviously) did write commit messages. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: ChangeLog (or lack of it)
Em Sáb, 2008-08-30 às 22:19 +0200, Gil Forcada escreveu: > Hi > > if [[ -f Changelog]]; then > Clever stuff if exists > else > Clever stuff if it doesn't exist > fi > > Hope is useful :) Not much; the ChangeLog usually exists, but with a message telling us not to change it. If at least there was an standard for that message, we could reliably automate the check. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
ChangeLog (or lack of it)
I see a few modules don't use ChangeLog anymore, at least inside "po/". I like using shell scripts to avoid repetitive typing when I review other people's translation, but this issue keeps slowing me down. Is there some way for a script to guess whether if a ChangeLog file is deprecated? -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Sodipodi
Em Sáb, 2008-08-30 às 05:13 +0200, Andre Klapper escreveu: > Am Samstag, den 30.08.2008, 00:01 -0300 schrieb Leonardo F. Fontenelle: > > I see the sodipodi module [1] had no commit in the last 2 years, except > > for two translations. Maybe we should remove it from damned lies, as > > well as from svn to svn-archive (but I don't know who to ping about the > > last one). > > Please write a message to [EMAIL PROTECTED] . Done, thanks. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Sodipodi
I see the sodipodi module [1] had no commit in the last 2 years, except for two translations. Maybe we should remove it from damned lies, as well as from svn to svn-archive (but I don't know who to ping about the last one). http://svn.gnome.org/viewvc/sodipodi/trunk/ -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gnome si locale within next two months
Em Sex, 2008-08-29 às 16:36 +0530, Danishka Navin escreveu: > > Folks, > > I am doing a workshop on gnome localization for Sinhala (si) locale > [1]. > > Date: 3rd September 2008 > Location: Metatechno, WTC Colombo, Sri Lanka > Target: to increase the gnome Sinhala translation status by 30% within > next two months > > > I am planning to work on trunk not branches. > Is it ok? > > [1] http://l10n.gnome.org/teams/si > It's perfect. For most modules, "trunk" means what will be released as GNOME 2.24. Please notice that a few modules (e.g. metacity and epiphany) alredy branched for GNOME 2.24. For those modules, you should probably translate that branch, and latter copy the message catalogs to trunk. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Gtranslator in window$
Em Sex, 2008-08-29 às 22:26 +0200, Gil Forcada escreveu: > Hi Ignacio, > > Is there any approximate date for a stable release? :) > I just hope it's released _after_ GNOME 2.24. We are busy enough right now, so gtranslator would probably be released with little translation. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translation in gnome-power-manager
Em Qua, 2008-08-27 às 23:08 +0200, Claude Paroz escreveu:
> Hi all,
>
> Before entering a bug in gnome-power-manager, I'd just like to know the
> correct way to translate this (from gpm-cell.c):
>
> if (unit->is_present == FALSE) {
> g_string_append_printf (details, "%s: %s\n", _("Status"),
> _("Missing"));
> } else if (gpm_cell_unit_is_charged (unit)) {
> g_string_append_printf (details, "%s: %s\n", _("Status"),
> _("Charged"));
> } else if (unit->is_charging) {
> g_string_append_printf (details, "%s: %s\n", _("Status"),
> _("Charging"));
> } else if (unit->is_discharging) {
> g_string_append_printf (details, "%s: %s\n", _("Status"),
> _("Discharging"));
>
> I think the idea was to remove markup for translators, which is a good
> thing per se, but in this case, I'm afraid it's unavoidable to include
> the markup inside the strings, to give something like :
>
> g_string_append (details, _("Status: Missing\n"));
>
> In French, it would be translatable if the ":" were in the translated
> strings:
>
> g_string_append_printf (details, "%s %s\n", _("Status:"),
> _("Missing"));
>
> But I think this is not acceptable for LTR languages, right ?
>
For Portuguese it will work as well as in French (but let's hear from
the other languages). But we'd like context for "Charged" (and maybe
other languages would want if for other statuses, too) because the
translation should be different depending on whether it's a battery or a
UPS.
--
Leonardo Fontenelle
http://leonardof.org
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Review needed for Pango language sample strings
Em Ter, 2008-08-26 às 18:33 -0400, Behdad Esfahbod escreveu: > > If the string lenght is OK I can open a bug report with a patch. > > Patch would be nice, yeah. I can do the patches myself though if one opens a > bug and leaves me the phrase and English translation. > > So yeah, even if not sure, please open the bug. That makes it easier for me > to track them all and not lose anyone's suggestion. > Done: http://bugzilla.gnome.org/show_bug.cgi?id=549522 > > Em Ter, 2008-08-26 às 18:12 -0400, Behdad Esfahbod escreveu: > >> Hi, > >> > >> Pango keeps a single string (sentence) per language that it uses internally > >> and also exposes for other applications to use (in a font dialog for > >> example). > >> Previously the sample text were quite limited (about 20 language > >> supported), > >> and bogus. I have not extended the list to about a hundred tables. I used > >> various sample-string, pangram, and other resources freely available. > >> These > >> can be found here: > >> > >> http://svn.gnome.org/viewvc/pango/trunk/pango/pango-language-sample-table.h?view=markup > >> > >> I'm now asking translation teams to review the sentence for their language > >> now. Please file a bug against pango at http://bugzilla.gnome.org/ if you > >> think a sample string needs to be changed. A good sample string would be: > >> > >> - Politically correct > >> > >> - Representative of normal text in the language (so, no alphabetical > >> lists) > >> > >> - Exposes features unique to the language (European sample strings would > >> use > >> diacritics used in the target language for example) > >> > >> - Not too short, not too long > >> > >> - Not copied from what Windows uses (unless it's a very widespread thing > >> like "The quick brown fox..." -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Add BillReminder to DL
Em Ter, 2008-08-26 às 18:59 -0400, Og Maciel escreveu: > On Tue, Aug 26, 2008 at 6:48 PM, Daniel Nylander <[EMAIL PROTECTED]> wrote: > > Believe me, this is a serious problem. I have been the manager for the > > Swedish Ubuntu Translators team for a couple of years. Swedish is a > > difficult language and many, many people can't write even close to > > correct Swedish. The method we used was to limit the translator group to > > only 5 people, and fight off all people who applied for membership. That > > was drastic but worked. Now we channel all translations through these > > few members. > > I too ended up doing the same exact thing back when I was the > coordinator for the Brazilian team... and you wouldn't believe how > much flac I got, but it is all behind now. > Coordinator of the pt_BR Ubuntu translation team (to avoid any possible confusion). > > This has to be a Launchpad bug. This guy is part of no translator group > > and should not be able to do much more that make suggestions. > > I have filed a bug, https://bugs.launchpad.net/rosetta/+bug/261660 > > Thanks for filing this. I'll subscribe to it and will follow it. > > Cheers, -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Review needed for Pango language sample strings
The Brazilian Portugues pangram is good but has no diacritcs. As a Brazilian I don't bother to check if a particular software or font supports them; it is very likely that it will do a good job. But, if you want to put enphasis on the diacritics, please consider if this phrase is short enough: À noite, vovô Kowalsky vê o ímã cair no pé do pingüim queixoso e vovó põe açúcar no chá de tâmaras do jabuti feliz. If the string lenght is OK I can open a bug report with a patch. Em Ter, 2008-08-26 às 18:12 -0400, Behdad Esfahbod escreveu: > Hi, > > Pango keeps a single string (sentence) per language that it uses internally > and also exposes for other applications to use (in a font dialog for example). > Previously the sample text were quite limited (about 20 language supported), > and bogus. I have not extended the list to about a hundred tables. I used > various sample-string, pangram, and other resources freely available. These > can be found here: > > http://svn.gnome.org/viewvc/pango/trunk/pango/pango-language-sample-table.h?view=markup > > I'm now asking translation teams to review the sentence for their language > now. Please file a bug against pango at http://bugzilla.gnome.org/ if you > think a sample string needs to be changed. A good sample string would be: > > - Politically correct > > - Representative of normal text in the language (so, no alphabetical lists) > > - Exposes features unique to the language (European sample strings would use > diacritics used in the target language for example) > > - Not too short, not too long > > - Not copied from what Windows uses (unless it's a very widespread thing > like "The quick brown fox..." -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Some useful scripts
Em Seg, 2008-08-11 às 21:22 -0300, Leonardo F. Fontenelle escreveu: > I'm working with a teammate on a script to streamline the checkout part. > The script should use damned-lies information to find the appropriate > branch for a given module in a given release set. We already have a > functional version (actually two, in shell script and ruby), and should > publish them soon. Here it is. I'll put it in GNOME Live as soon as I write decent user documentation of it. The idea behind it is to avoit checking out the entire module when all you want is inside the po/ and the help/ directories. The script works with multi-domain modules (like gtk+) and with multi-help modules (like gnome-games). It will fail to check out the documentation for gfloppy, which is an external dependency for gnome-utils, but as soon as possible I'll add a hack to fix this. Right now, you can put this script in your path, cd to some directory (I use ~/linux/l10n) and run (in example): tsfx -u leonardof -r gnome-2-24 -m eog If you want to check out the entire release set, omit the "-m" argument. You can also open the script with a text editor to set the default locale or SVN account. The script is quite clever. First, it can guess a default language code. Second, if a module branched, or if you previously checked out the module anonymously, it will use "svn sw" to fix the svn root. Thanks to Simos for the vision, and Shaun McCance and Danilo Segan for the tips: http://leonardof.org/2008/04/28/parsing-damned-lies-releasesxmlin-in-the-command-line/en/ -- Leonardo Fontenelle http://leonardof.org tsfx Description: application/shellscript ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Some useful scripts
Em Seg, 2008-08-11 às 15:46 +0200, Gil Forcada escreveu:
>
> To ease my translation/revision workflow I have made some small bash
> scripts that I'm attaching if anyone things they are useful :)
I got a few of them too, so I'll post them here. Most of my workflow is
abount revision, so usually the pt_BR.po files wil be somebody else's
* zzcl - Besides calling prepare-ChangeLog.pl (cl, ChangeLog), it
tiddies up the message catalog (i. e. breaking the long lines from
poEdit) and run a few checks. I run it on
$module/po{,-locations,-properties}/pt_BR.po. It can be used to commit
catalogs with minimal checking (for senior translators in our team),
after saving the new translation as pt_BR.po.gz or pt_BR.po. The
pt_BR.po.trad will make more sense in a minute. After running zzcl, it's
just a matter of "svn ci" and copy an past the ChangeLog entry to the
commit message.
* zzpo - Also to be run after checking out the module translation from
SVN. It asks for a translated message catalog (i. e. downloaded from our
Vertimus server) to be reviewed, and a message catalog from damned-lies.
It makes it easy for me to see what the translator changed, and also
runs pofilter to check for new or old errors. If I do any fix to the
translation, the resulting pt_BR.po and pt_BR.po.trad are used by zzcl
to generate a diff, which I use to inform the translator about the
changes I made.
* zzco - Yet another "svn co" wrapper.
I'm working with a teammate on a script to streamline the checkout part.
The script should use damned-lies information to find the appropriate
branch for a given module in a given release set. We already have a
functional version (actually two, in shell script and ruby), and should
publish them soon.
PS: the script names are an homage to the zz functions, these misc.
shell script utilities (in Portuguese): http://funcoeszz.net/
--
Leonardo Fontenelle
http://leonardof.org
zzcl
Description: application/shellscript
zzco
Description: application/shellscript
zzpo
Description: application/shellscript
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Managing plurals
Em Sáb, 2008-08-09 às 19:38 +0200, Ignacio Casal Quinteiro escreveu: > Could you please try to make a mockup about how you want the > interface? > poEdit implements this singular/plural split view. I hope a ~40 KB attachment is OK. -- Leonardo Fontenelle http://leonardof.org <>___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Managing plurals
Em Sex, 2008-08-08 às 21:30 +0200, Ignacio Casal Quinteiro escreveu: > Hi, > > gtranslator right now is using a kbabel like style for plurals based > on tabs. > So I have: msgid with 2 tabs (Singular|Plural) > and msgstr with N tabs (Singular|Plural 1 ...) > > I want to add that when you are in a message with plurals and you are > in the > singular tab of msgstr and you press next message, I want to do that > gtranslator > switch to the Plural 1 tab, if you press again Pural 2 ... > Another thing that I want to do is that if you are in Plural X on > msgstr gtranslator > switches automatically to the Plural 1 of msgid and if I come back to > Singular of > msgstr switch automatically to Singular of msgid. > > As I only know about languages with 2 plurals here is the question: > > Can I do this? I mean in Spanish/Galician if you in Plural 1 you want > to see the Plural > tab of msgid but is this user case possible in other languages? > This would work for Portuguese, too (big surprise :) ) but probably not for languages with n!=2. Honestly I don't like tabs for msgid plurals. There will be always two of them, so we'd rather display both the singular and the plural msgid "in parallel". That should be much faster to translate, because of the diminished browsing. Even better, there will be diminished _mouse_ browsing, because it's hard to navigate with the keyboard through 3 sets of tabs (msgid, msgstr, catalogs). Original messages with plural forms are typically short, so msgid[0] and msgid[1] could share the vertical dimension of the msgid area of the GUI. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Using msggrep for terminilogy fixes
msggrep was hard to learn, so I decided to write a HOWTO. The blog post has msggrep and msgmerge syntax examples and a few shell tricks for batch processing and underline (access key) inclusion. I hope other translation teams can benefit from it! http://leonardof.org/2008/08/03/how-to-use-msggrep-to-apply-new-terminology-on-previous-translation/en/ -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Strings change in evolution
Em Seg, 2008-07-28 às 16:02 +0200, Christian Rose escreveu: > If the strings don't fit in English, you can bet that most other > languages won't fit either. Many languages, e.g. German, are in > general a lot more verbose than English, and require room for this > verbosity. > > So saying something to the effect of "I shortened an English word in > order to fit in the window/dialog" is a strong indicator that you have > got a lot more serious I18N problems... enough room in the > windows/dialogs from start, in order to fit longer translated > messages, is a key requirement for I18N. > > Furthermore, terminology consistency is very important for translation > -- if "message" is what is used elsewhere in Evolution, it should be > used here too. > Providing another example: Portuguese text is usually ~30% longer than English text. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Prolific Pashto team!
Em Seg, 2008-07-21 às 22:55 -0700, Zabeeh khan escreveu: > Working hard to get it listed as supported language in the next > release or atleast in the second next release. There is only me > working on it. Many promised to contribute, but no one really did. > > Hope to see many more contributors soon. > Even if you don't get any help before GNOME 2.24 is released, don't loose your hope. Do your best, and when GNOME 2.24 is released make sure people know what was achieved, and how can they help. When other people start helping you, praise or thank them publicly! -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String addition to EOG
Em Ter, 2008-07-22 às 18:30 +0200, Felix Riemann escreveu: > Am Montag, den 21.07.2008, 22:42 -0300 schrieb Leonardo F. > Fontenelle: > > Your consideration is telling us what the message means is a sign that > > these information should be added as comments to the messages in the > > catalog (i. e. in the source code near the strings). Please consider > > adding those comments if you didn't you it yet. > > Yes, translator comments are already present. :-) > Thanks! -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'gnome-backgrounds.HEAD'
Em Ter, 2008-07-22 às 22:48 +0200, Claude Paroz escreveu: > Le mar 22 jui 2008 22:09:39 CEST, Thomas Wood <[EMAIL PROTECTED]> a écrit: > > > > I'm not quite sure I follow, we are only in string change announcement > > period, and I was just about to announce these changes. These changes > > are for 2.23. > > > > Please explain if I have missed something. > > The problem is that strings from gnome-backgrounds didn't change for > long, and are freezed from GNOME 2.12 on! > If you want to change/add strings, you'll have to branch > gnome-backgrounds first (probably a gnome-2-22 branch). > Maybe there's no need for branching (this time). GNOME 2.22.3 was already released, so this "string freeze break" won't affect anyone. It surely would be unnacceptable if the strings were added before we released GNOME 2.22.3. IIRC, gnome-user-docs don't branch because it's updated only after GNOME 2.xx.3 is released. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Prolific Pashto team!
My l10n team is making a few terminology fixes in the translation of several GNOME 2.24 modules. I'm committing these fixes, and apparently everywhere I get I see Gil Forcada was there before, committing a Pashto translation. Way to go! -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String addition to EOG
Em Seg, 2008-07-21 às 18:53 +0200, Felix Riemann escreveu: > + "%.1f (lens)" > This one means [...] > > + "%.1f (35mm film)" > This one is [...] Thank you very much. Your consideration is telling us what the message means is a sign that these information should be added as comments to the messages in the catalog (i. e. in the source code near the strings). Please consider adding those comments if you didn't you it yet. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Gtranslator Translation Memories UI
Em Sex, 2008-07-18 às 10:24 +0200, Pablo Sanxiao escreveu: > To create the translation memory the first option that we thought was > getting the strings from PO files in one directory. We think is very > useful and that is the way of doing it in another programs like kbabel > or PoEdit. > IIRC poEdit asks the users for a list of folders, not a single folder. Anyway, it's important to make clear that there will be recursion, i. e., that subfolders will be scanned as well. >From the screenshot it was not clear at first for me if the selected directory would hold the TM database, or if it would be scanned for messages to be included in the TM. > For the Gtranslator 2.0 we think this could be enough but for the next > releases maybe we could implement new ways of adding strings to the > translation memory. What do you think? What would be useful for you? > Automatically adding messages to the TM when the user works with new catalogs. Sometimes the standards change, so the old TM may became counterproductive. It's important to allow the user to erase the database, or maybe (not for 2.0!) edit it. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Gtranslator Translation Memories UI
Very nice! I'm not using it yet, so I can't say if the TM part is too wide. Maybe it doesn't matter, because the TM will be most helpful for short messages anyway. I'd rather have suggestions sorted by score, i. e., the first suggestions would be the ones with the highest "level". -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translation memory in gtranslator
Em Seg, 2008-07-07 às 15:46 +0200, Nacho escreveu: > Today I finished the TM backend for gtranslator. > As soon as we finish with the interface part I think > we'll commit the patches to subversion. > I would be glad having some feedback to test it > as soon as we commit it. > Thank you, I hope to be able to test it in a week or or two. Even if I'm an almost unrecoverable Vim user, I'm very excited with Gtranslator, and I can't wait to see it released. I just hope regular translators can testify the amazing work you guys did in the last months! -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Launchpad licensing issues
Em Qui, 2008-07-03 às 21:31 -0400, Og Maciel escreveu: > On Thu, Jul 3, 2008 at 7:46 PM, Leonardo F. Fontenelle > <[EMAIL PROTECTED]> wrote: > > What a minute... If I localize a GPL-ed software, and distribute my > > translation with the GPL, an Ubuntu translation team will be unable to > > import it into Rosetta. Even worse, today there should be a lot of > > upstream translation already in Rosetta. They can't just change the > > licensing of previously GPL-ed contributions! > > Hold your horses fellas. Nothing of this sort has happened yet. I've > been following this discussion at both ends of the "arena" long > enough, and from what I understand nothing that gets imported (not to > confuse with uploaded manually) by Ubuntu gets the new BSD licensing > scheme. In other words, a GNOME package that gets imported will > maintain its original license. It is only with translations done via > Rosetta OR manual uploads that the BSD license kicks in (assuming you > are a member of the Ubuntu translation team AND have chosen the BSD > license). Because this new process is new, I believe that it is safe > to say that every GNOME package in the Ubuntu repositories still have > their original license. That's better :) When a imported, GPL-ed translation needs one or two adjustments in Rosetta (e.g. because of an Ubuntu patch, or upstream has a translation bug), how will the resulting Ubuntu file be licensed? -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Slowness in farsi translation
Em Qui, 2008-07-03 às 13:59 +0430, s.m ziaei escreveu: > Hi all. > We must all increase our endurance. Usually I just discard the e-mails from this endless thread. We must all stop fighting, and start working together. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Launchpad licensing issues
Em Qui, 2008-07-03 às 19:52 +0200, Sven Herzberg escreveu: > AFAIK the BSD-License was chosen exactly to permit this. You can easily > relicense BSD-licensed code (translations as well) to (L)GPL. They chose > the BSD-License to be able to deal with upstreaming of translations > (read: pushing launchpad translations into the upstream projects). What a minute... If I localize a GPL-ed software, and distribute my translation with the GPL, an Ubuntu translation team will be unable to import it into Rosetta. Even worse, today there should be a lot of upstream translation already in Rosetta. They can't just change the licensing of previously GPL-ed contributions! -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
How successful is your module among translators?
Right now Damned Lies provides convenient ways to find the most successful translation teams, e. g.: - http://l10n.gnome.org/releases/gnome-extras or - http://l10n.gnome.org/module/evolution I think DL is a very useful and usable translation tool. Sorting modules by name helps us finding them, and sorting teams by translation completion makes DL more usable for the people actually using it. But then, don't we love to see when our teams progress in that list? Maybe we should give developers _that_ kind of feedback! The module pages are already very good at showing developers how well are they doing with translators. And they are very rich: they provide quick information on how many teams translated the module, and how homogeneous is the translation status among team. What Damned Lies doesn't provide yet is information about how do modules compare to each other. That kind of information is less useful than that from the module page, but there are all kinds of people, and I'm sure many developers would care to see their modules among the top translated. We could sort the modules (inside a release set) using a translation index, which would be the sum of the percentual translations. E. g., 50% + 30% = 0,8; 10% + 20% + 30% + 40% = 1,0; 90% + 85% + 95% = 2,7; and so on. Of course, adjusting the index for quality would be great, but I doubt we can easily measure quality. So, do you think the idea is worth a formal feature request? -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Quote entities
Em Sex, 2008-06-27 às 23:45 +0200, Jorge González González escreveu: > Hi, > > I was wondering whether the entities and present at > some help documents, which I understand are transformed into "", are > also replaced by each language specific quotes (for example «» in > Spanish). This can be accomplished by translating gnome-doc-utils accordingly: #. #. This is a special format message. Please read the full translator #. documentation before translating this message. The documentation #. is maintained as part of the stylesheet documentation in DocBook. #. For your convenience, it has also been converted to an HTML file #. named STYLESHEETS.xml in the i18n directory. #. #. quote - An inline quotation #. http://docbook.org/tdg/en/html/quote.html #. #. This is a format message used to format inline quotations. This template #. uses roles to control how the quotation is formatted. The role indicates #. whether this is an outer or inner quotation. Quotations nested inside #. another quotation are inner quotations. Many languages have an alternate #. notation for nested quotations. #. #. These stylesheets only provide two levels of quotation formatting. If #. quote elements are nested deeper, the stylesheets will alternate between #. the 'outer' and 'inner' roles. If your language uses different formatting #. for deeper quotations, please contact the maintainers, and we will try to #. implement a more flexible formatting mechanism. #. #. Special elements in the message will be replaced with the #. appropriate content, as follows: #. #. node - The text content of the quote element #. #. These should be written as empty XML elements. Due to limitations #. in intltool, I can't write XML content in translator comments. To #. insert the node, simply write left angle bracket, node, slash, #. right angle bracket. #. #. Additionally, format messages can use the i, b, and tt markup tags #. to mark text as italic, bold, and monospace. #. #: ../xslt/gettext/l10n.xml.in.h:1150 msgid "" "quote.format ‘’ " "“”" -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: evolution-caldev root commits failing
Em Sex, 2008-06-06 às 15:58 +0930, Clytie Siddall escreveu: > To: gnome-i18n, Christian Kellner > __ > > Hi everyone :) > > I just added our translation (enormous, it was ;) ) to evolution- > caldav. Two things made this more difficult: > > 1. the PO directory does not have a LINGUAS file. Christian, it is > much better l10n practice to put LINGUAS in /po, rather than relying > on translators filling in ALL_LINGUAS in the /configure.in file. It's > quicker for us, it means we don't have to check out the whole package, > and that we won't mess up your config info. So please use /po/LINGUAS. I opened a bug report a few weeks ago about this issue: http://bugzilla.gnome.org/show_bug.cgi?id=533045 -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Updating gnome glossary
Em Sex, 2008-05-23 às 09:33 -0700, Praveen A escreveu: > It was very useful when we started and it is still very useful for new > translators. But it last updated 3 years ago. > http://svn.gnome.org/viewvc/gnome-i18n/trunk/glossary/ > > I hope we can update it. Shaun McCance is doing this, with the name "GNOME Terminology". The discussion is held in gnome-doc-list. There has been little activity in the last few weeks, though. Please search the mailing list archives and GNOME Live. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Stepping down
Em Sáb, 2008-04-19 às 19:12 -0500, Guilherme de S. Pastore escreveu: > [...] > I hereby tender my resignation from my role as Brazilian Portuguese > Translation Coordinator in the GNOME Project, and appoint Leonardo > Ferreira Fontenelle <[EMAIL PROTECTED]> to succeed me in this > one, particular task. The resignation shall be effective from the > moment Leonardo has accepted the duty and this message has been > acknowledged by at least one of the GNOME Translation Project > coordinators. > [...] I'd like to thank Guilherme de Siqueira Pastore for appointing me, and I fully accept the team coordination responsibilities [1]. My first action will be scheduling an IRC meeting with the team to discuss our work flow and what do they expect from me. 1. http://live.gnome.org/TranslationProject/TeamCoordinatorResponsibilities -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
