Hello girlz and boyzz ... I want to start a slovenian translation of Mailman ... I have some problems starting ... I have read the manual 'How to start' from Simone, but I have some question about encoding of the .po file. Which encoding should I use ? I wanted to use ISO-8859-2 but then the msgfmt complained first and I couldn't force it to make the right .mo file (such that could display chars correct the page ;) I got only strange chars instead our local chars ... The source of the HTML (mailman page displayed in the browser) shows that encoding is set OK in the HTML (iso-8859-2) ... Should I use UTF-8 instead ? Why doesnt KBabel offer me to save the .po file in my encoding , only UTF-8 is to choose ? Iztok
Iztok Stotl wrote:
Which encoding should I use ?
I wanted to use ISO-8859-2 but then the msgfmt complained first and I couldn't force it to make the right .mo file (such that could display chars correct the page ;)
ISO-8859-2 should work fine. How precisely did msgfmt complain? And what precisely is the PO header that you have been using?
Why doesnt KBabel offer me to save the .po file in my encoding , only UTF-8 is to choose ?
I'm not a KBabel user, but if KBabel indeed behaves that way, that would be a bug. I use Emacs po-mode. Regards, Martin
Martin v. Löwis wrote:
Why doesnt KBabel offer me to save the .po file in my encoding , only UTF-8 is to choose ?
I'm not a KBabel user, but if KBabel indeed behaves that way, that would be a bug. I use Emacs po-mode.
It probably saves in UTF-8 because KDE uses uses unicode internally (by having the catalog in UTF-8, gettext won't need to do a codeset conversion during translation). From the documentation, it sounds like you can set a preference to leave the text encoding unchanged when saving. This might help. James. -- Email: james@daa.com.au WWW: http://www.daa.com.au/~james/
Thank you for your answers ;) I managed to convince KBabel to work with iso-8859-2 ;)) I have translated the first 250 pieces... Now I have the problem that some things get translated and some don't ... For example ... On the listinfo page ... The whole page get translated except "GNU is not unix", "Powered by Python" and "trasfered my Mailman version ..." I have translated them in the .po file ??? And the texts in the archive don't translate at all ?? In Defaults.py I have : Default language = 'en' Add language 'sl' .... iso-8859-2 and in mm_....py where I should put my personal settings I have : Default language = 'sl' Is this correct ? Iztok (Slovenia)
Iztok Stotl <iztok.stotl@guest.arnes.si> writes:
The whole page get translated except "GNU is not unix", "Powered by Python" and "trasfered my Mailman version ..."
I have translated them in the .po file ???
It's your choice. I would leave "GNU is not unix" untranslated. If you can find something equally punching like "Powered by Python" in Slovenian, feel free to use that; in German, "Angetrieben durch Python" doesn't sound quite convincing.
And the texts in the archive don't translate at all ??
You mean, the messages themselves? Certainly not - you can only translate the user interface, there is no way to automatically translate the messages that people have sent to the mailing list. Notice that the navigational aspects of the pipermail archive are generated HTML, so they don't change when the user changes the language. If you want the list archive in a different language, you have to regenerate the entire archive. Regards, Martin
On Thu, 2003-05-01 at 03:56, Iztok Stotl wrote:
I wanted to use ISO-8859-2 but then the msgfmt complained first and I couldn't force it to make the right .mo file (such that could display chars correct the page ;)
Take a look at the Polish, Czech, or Hungarian .po files. All use iso-8859-2 also. You'll need to make sure you have a header like Content-Type: text/plain; charset=iso-8859-2 In the empty-string msgstr (gettext convention for providing catalog metadata). And be sure to send me any translations you make when they're ready! -Barry
participants (5)
-
"Martin v. Löwis" -
Barry Warsaw -
Iztok Stotl -
James Henstridge -
martin＠v.loewis.de