Op Dinsdag 2007-10-23 skryf Xavier Alvarez: > On Tuesday 23 October 2007 17:01, F Wolff wrote: > FW> Op Dinsdag 2007-10-23 skryf Xavier Alvarez: > FW> > Hi! > FW> > > FW> > This may sound a bit weird, but... how does one localize > FW> > the server itself? > FW> > > FW> > I don't mean the strings that are shown in the web-gui to > FW> > the user that are inherently a part of the server, but > FW> > rather the strings that describe the *project* for which > FW> > the server was set up. Some would call this the > FW> > "parameterization" of the server. > FW> > > FW> > IOW, in the main admin page you have entry fields for Home > FW> > Page, Description, Base URL, and Title. Which as far as I > FW> > can tell, are bound to the pootle.prefs file. Fine, but > FW> > it's a single language (afaik). > FW> > > FW> > Another alternative is to modify the html pages themselves > FW> > (quite absurd if you ask me ;) Again, a single language. > FW> > > FW> > But looking into the pootle.pot file you find some of the > FW> > same strings there (amongst all the other msgids[1]). Some > FW> > seem to be preceded by a "#. l10n:" comment that > FW> > identifies them. > FW> > > FW> > I like the idea of using Pootle as a meta-localization > FW> > server that allows its own parameterization in multiple > FW> > languages, but using the same .POT for both functional and > FW> > site localization is both tricky and confusing, because > FW> > when you start out in the parameterization process, the > FW> > 'default' strings have all been translated to the other > FW> > languages... and you don't want that text to show. So how > FW> > can one 'reset' them and define new defaults? > FW> > > FW> > BTW, I don't know much about Pootle itself and may've > FW> > gotten everything wrong; but if I haven't, I would > FW> > strongly suggest splitting the pootle.pot and create a new > FW> > POT exclusively for the "parameterization strings" (that > FW> > also need to be localized) and that is clearly isolated > FW> > from the 'functionality' localization. > FW> > > FW> > So, in the meantime, how could one go about it? > FW> > > FW> > > FW> > Cheers, > FW> > Xavier > FW> > > FW> > FW> Hi Xavier > FW> > FW> Yes, your observations are correct. Currently we only do the > FW> UI localisation properly. My idea for doing the rest is > FW> exactly as you suggest: a separate PO / POT file that the > FW> server admin can augment manually to enter things like the > FW> server description, project descriptions, etc. > FW> > FW> Currently it is not possible. I have considered simply > FW> putting more than one language in the same description, but > FW> that is quite clumsy, and one probably has to limit it to a > FW> single few languages. On the other hand, we'll have to stop > FW> somewhere short of making a complete multilingual content > FW> management system ;-) > FW> > FW> For now I'll recommend to keep things very simple on the > FW> server and to link to an appropriate wiki / existing > FW> documentation site where things can be explained in more > FW> detail, where multilingual content might already be solved > FW> better. I would still like to implement it properly for > FW> Pootle, but for the time being, you'll have to resort to hacks > FW> (unless you want to implement the proper solution with an > FW> extra PO file in the pootle project. One hack that might > FW> look correct to users is to use javascript to detect the > FW> lang attribute in the surrounding xhtml and to hide the > FW> strings in the other languages, but that is just messy > FW> anyway... > FW> > FW> I hope I understood your question and suggestions correctly. > FW> > FW> Friedel > > > Hi Friedel, > > Yes, you understood perfectly what I was referring to (I'm not > always too clear :) > > The idea of a multi-lingual content manager... well, it would make > sense that just as Pootle can be localized dynamically, the > descriptive aspects of the installation too -- kind of > full-circle :) > > Regarding the "#. l10n" tag, is that consistent? (ie: does it > fully cover all the 'visual' aspects of the Pootle install?) If > so, maybe they should be tagged as fuzzy? That way the language > or server admin can quickly 'fix' them... > > As for the alternative hacks... I think that for the mometn I'll > just stick to a basic setup (and avoid learning-by-screwing for > the moment ;) > > > Cheers, > Xavier >
The l10n comments are retrieved from the Python source code when the POT file is generated with xgettext. It is supplied by the programmers and displayed along with the translation to help the translators. You could edit the Python files to change those messages, regenerate the POT file, update all the translations with pot2po, and then have translators translate it all over again. But realistically speaking it might simply mean that several languages won't have those messages translated at all, instead of simply having your small part untranslated. Perhaps the easiest is to simply add an element to the GUI with the python code and kid templates which will simply add translations to the POT file which could then be translated where there are translators available and willing to do. See if you get things working and then you can try one step at a time :-) 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
