Faq-O-Matic Faq-O-Matic : Administrators' Guide : In Development : Translations and text interface :
How to implement a translation into existing version of FOM ? | |
On about line 715 of install.pm, you'll see an entry: ci('language', '-sort'=>'k-m00', '-choices'=>[ "'en'", "'de_iso8859_1'", "'fr'"], '-desc'=> gettext("Select the display language."), '-default'=>"'en'"), Add "'pl'" to the list where en, de_ise8859_1, and fr appear. (This assumes your translation module is named `Language_pl.pm'.) In the exemple : pl means the country Poland. de - Germany. fr - France. | |
The language translations do not seem to work anymore. Translation files give a "bad translations" n "pair 16 as coded to report. I am to lazy to find out how to resolve this (or to busy sleeping). I do not know that much of perl coding. Tried out uncommenting some pairs, only confused me more. Think that this is because the making of the language_ files are not related to the ongoing coding of the programmers. Is there not a way to solve this with a meta-solution for more programmers? Encode gettext with readable strings you invent. Decode it to variables. Any new string added is a new xyxyxyxyxy variable in the language file. Programmer codes with the language she likes to abuse, users are responsible to take "diff"actions to maintain there own use of the program there own language preferences. I know. 387 strings of gettext if you grep the files is hard to decode to variables. I spent last night translating it to dutch. Only to find out that I should have started with checking the the file I was translating. FR an DE_isoblah Still: this program will stay with bags or with however i will call them thanx for making it in the first place | |
here's a patch against this problem: <file=1406>
| |
[Append to This Answer] |
Previous: | in Finnish (partial) |
Next: | Patch: Language_de Language_fr |
|