I'm creating a dutch translation of Mailman (as I already have a partly
translated Mailman installation (2.0b2-based) to start with) but I ran into
a couple of issues. Specifically, it took me a while to figure out how to
translate :) It would be helpful if there was a README file in, say,
messages/, explaining how to do it. I found helpful notes in the archives of
this list, though.
The other thing is that some messages need rewriting in the english in order
for it to fit in Dutch; For instance,
msgid "Creating archive directory "
The extra space after the 'directory' suggests, to me, that Mailman will
append the directory name. In Dutch, the best translation would be
msgstr "Maak archief directory %(directory)s aan."
but that won't work, the way it's done now... Should I deal (I can, in this
case, but I'm not done translating, so it might end up being a real problem
later on) or fix (by changing the english string) ? :)
--
Thomas Wouters
Thomas Wouters wrote:
The other thing is that some messages need rewriting in the english in order for it to fit in Dutch; For instance,
msgid "Creating archive directory "
The extra space after the 'directory' suggests, to me, that Mailman will append the directory name. In Dutch, the best translation would be
msgstr "Maak archief directory %(directory)s aan."
Almost all translated messages are intented to be shown in web pages. Another amount of messages must be written verbatim, bacause they will be either to be shown in screen or to be sent by email to users. When I'm in doubt about how to write some messages, I give a glance to source code in order to see the destination of the intended message. In this particular case, msgid "Creating archive directory " is contained in Archiver/pipermail.py in a line with: self.message(_('Creating archive directory ') + self.basedir) This code must be rewritten to solve this particular problem as done with greetings page in 'listinfo.py', to somethig like: dir = self.basedir self.message(_('Creating archive directory %(dir)s')) so you can write: msgid "Creating archive directory %(dir)s" msgstr "Maak archief directory %(dir)s aan." Cheers -- ___ / F \ [[[]]]] ( O O ) #----------------0000--(_)--0000---------------# | Juan Carlos Rey Anaya (jcrey@uma.es) | | Servicio Central de informática | | Universidad de Málaga - España | #----------------------------------------------#
"TW" == Thomas Wouters
writes:
TW> I'm creating a dutch translation of Mailman (as I already have TW> a partly translated Mailman installation (2.0b2-based) to TW> start with) but I ran into a couple of issues. Specifically, TW> it took me a while to figure out how to translate :) It would TW> be helpful if there was a README file in, say, messages/, TW> explaining how to do it. I found helpful notes in the archives TW> of this list, though. Excellent idea. I will try write something up tonight. TW> The other thing is that some messages need rewriting in the TW> english in order for it to fit in Dutch; For instance, TW> msgid "Creating archive directory " TW> The extra space after the 'directory' suggests, to me, that TW> Mailman will append the directory name. In Dutch, the best TW> translation would be TW> msgstr "Maak archief directory %(directory)s aan." TW> but that won't work, the way it's done now... Should I deal (I TW> can, in this case, but I'm not done translating, so it might TW> end up being a real problem later on) or fix (by changing the TW> english string) ? :) I think the right thing to do is to fix the English string in the code. I've already done this in a few places to aid the Japanese translations, where using Python's implicit string concatenation, e.g. "this is a sentence which" "spans two lines but acts as one" basically made the Japanese translation impossible. I'm not opposed to fixing the English strings to make translations easier. Thomas can send me patches, or just check them in himself. :) -Barry
"TW" == Thomas Wouters
writes:
TW> Specifically, it took me a while to figure out how to TW> translate :) It would be helpful if there was a README file TW> in, say, messages/, explaining how to do it. I found helpful TW> notes in the archives of this list, though.
"BAW" == Barry A Warsaw
writes:
BAW> Excellent idea. I will try write something up tonight. D'oh! Shows you how tired I was. There's a README-I18N.en file in the top level directory (cvs) that should explain how to get started. I'm about to upload a "translation pack" to SF which will contain README-I18n.en, templates/en, messages/mailman.pot, and messages/*/LC_MESSAGES/mailman.po. This should be easier for translators to use than grabbing them out of CVS. -Barry
participants (3)
-
barry@zope.com
-
Juan Carlos Rey Anaya
-
Thomas Wouters