Op Woensdag 2007-10-24 skryf Xavier Alvarez: > On Wednesday 24 October 2007 09:43, F Wolff wrote: > FW> Op Dinsdag 2007-10-23 skryf Xavier Alvarez: > FW> > On Tuesday 23 October 2007 17:01, F Wolff wrote: > FW> > FW> Op Dinsdag 2007-10-23 skryf Xavier Alvarez: > > ...snip... > FW> > Xavier > FW> > > FW> > FW> The l10n comments are retrieved from the Python source code > FW> when the POT file is generated with xgettext. It is supplied > FW> by the programmers and displayed along with the translation > FW> to help the translators. > > Oh, yes, I know where the "#." comments originate from, I was just > wondering if the "L10n" prefix on some of the comments was > chosen/used as a way to direct the attention to the 'site > paremeterization' :) (although it doesn't seem very consistent)
Oh, sorry! No. The l10n keyword is simply chosen to ensure that no unintended comments are used by xgettext. This is done by passing the parameter --add-comments=l10n to xgettext. I've tried to explain as many strings as might be necessary to help translators, but not in terms of the site customisation areas. > > > FW>You could edit the Python files to > FW> change those messages, regenerate the POT file, update all > FW> the translations with pot2po, and then have translators > FW> translate it all over again. But realistically speaking it > FW> might simply mean that several languages won't have those > FW> messages translated at all, instead of simply having your > FW> small part untranslated. > FW> > FW> Perhaps the easiest is to simply add an element to the GUI > FW> with the python code and kid templates which will simply add > FW> translations to the POT file which could then be translated > FW> where there are translators available and willing to do. > > Both of these options involve a new POT and the regeneration of > the POs (the second one also involving the modification of the > source code)... maybe an easier alternative would be to locate > those msgids we want changed, create an 'empty and fuzzy' POT and > use msgcat to zap the existing translations? > Yes, both my suggestions involve editing the Python. I'm not sure I understand your intended approach 100%, but I think it might be an ok method. You might want to take a look at pogrep and pomerge in the toolkit - but gettext tools might be ok as well. (see http://translate.sourceforge.net/wiki/toolkit/pogrep and http://translate.sourceforge.net/wiki/toolkit/pomerge ) > > FW> > FW> See if you get things working and then you can try one step > FW> at a time :-) > > Yes. Most of it is working (now I'm trying to use glossaries, and > probably some translation memories later). > > The 'cosmetics' part is a bit more important as we'll be using a > sort of open-house translator approach (anybody that cares can > collaborate) and we wanted to give more information and guidance > to the translators. Ok, the javascript approach is still usable, I guess. You might also want to do something like an iframe where you can use the lang attribute of the surrounding html to construct a url to embed in the page. But perhaps we're trying to be too fancy :-) I hope it works out well for you. Keep well Friedel ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
