Op Dinsdag 2007-10-23 skryf Xavier Alvarez: > Hi! > > This may sound a bit weird, but... how does one localize the > server itself? > > I don't mean the strings that are shown in the web-gui to the user > that are inherently a part of the server, but rather the strings > that describe the *project* for which the server was set up. Some > would call this the "parameterization" of the server. > > IOW, in the main admin page you have entry fields for Home Page, > Description, Base URL, and Title. Which as far as I can tell, are > bound to the pootle.prefs file. Fine, but it's a single language > (afaik). > > Another alternative is to modify the html pages themselves (quite > absurd if you ask me ;) Again, a single language. > > But looking into the pootle.pot file you find some of the same > strings there (amongst all the other msgids[1]). Some seem to be > preceded by a "#. l10n:" comment that identifies them. > > I like the idea of using Pootle as a meta-localization server that > allows its own parameterization in multiple languages, but using > the same .POT for both functional and site localization is both > tricky and confusing, because when you start out in the > parameterization process, the 'default' strings have all been > translated to the other languages... and you don't want that text > to show. So how can one 'reset' them and define new defaults? > > BTW, I don't know much about Pootle itself and may've gotten > everything wrong; but if I haven't, I would strongly suggest > splitting the pootle.pot and create a new POT exclusively for the > "parameterization strings" (that also need to be localized) and > that is clearly isolated from the 'functionality' localization. > > So, in the meantime, how could one go about it? > > > Cheers, > Xavier >
Hi Xavier Yes, your observations are correct. Currently we only do the UI localisation properly. My idea for doing the rest is exactly as you suggest: a separate PO / POT file that the server admin can augment manually to enter things like the server description, project descriptions, etc. Currently it is not possible. I have considered simply putting more than one language in the same description, but that is quite clumsy, and one probably has to limit it to a single few languages. On the other hand, we'll have to stop somewhere short of making a complete multilingual content management system ;-) For now I'll recommend to keep things very simple on the server and to link to an appropriate wiki / existing documentation site where things can be explained in more detail, where multilingual content might already be solved better. I would still like to implement it properly for Pootle, but for the time being, you'll have to resort to hacks (unless you want to implement the proper solution with an extra PO file in the pootle project. One hack that might look correct to users is to use javascript to detect the lang attribute in the surrounding xhtml and to hide the strings in the other languages, but that is just messy anyway... I hope I understood your question and suggestions correctly. 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
