I've almost completed the norwegian translation for mailman-1.2a2. I will soon merge message.pot for mailman-1.2a3 with my message.po, but I want to finish message.po for the mailman-1.2a2 version first. But I need a little help with a few strings, because I don't know what they're being used for or where they appear. (Which is essential to know to be able to translate them). If someone could help me out, it would be great. What I would like to know is where these strings appear, and how to produce them. (e.g. what to do to make them appear in the context they are supposed to appear) 1. #: Mailman/Archiver/pipermail.py:276 msgid "Reloading pickled archive state" 2. #: Mailman/Archiver/pipermail.py:303 msgid "Pickling archive state into " 3. #: Mailman/Bouncer.py:220 msgid "BUT: %(succeeded)s" 4. #: Mailman/Cgi/admin.py:311 msgid "No valid variable details request not found: %(path_info)s" (I didn't really understand this one, is this a typo?) 5. #: Mailman/Handlers/Acknowledge.py:57 msgid "%(realname)s post acknowledgement" I now have have 763 translated strings in my message.po :) I'm skipping all docstrings and the strings for bin/pygettext.py. I'm also wondering how to make translated strings appear when running any of the commands in <mailman-dir>/bin. When I run e.g. check_perms, I still get "No problems found", not my translated norwegian string... And I have some suggestions/questions about some of the strings in message.po (my examples are for 2.1a2, some of these have been moved to other files in 2.1a3): 1. These two strings are the same, right? #: Mailman/MailCommandHandler.py:411 msgid "%(origsender)s isn't subscribed to this list." and #: Mailman/MailCommandHandler.py:436 msgid "%(origsender)s is not subscribed to this list." Maybe one of these could be chosen, so the same string is used both places? (In norwegian, for example, the translation of these to strings would be the same.) 2. Mailman/MailList.py:390 reads: "[...] In order to split the list ownership duties into administrators and moderators, you must set a separate moderator password in the section below, and also provide the email addresses of the list moderators in this section. [...]" I think this text maybe should be rewritten a bit, because the text does not appear where the user is setting the moderator password, it appears in the help/details page for providing email addresses of the list administrators. Maybe just removing "in the section below" would do be enough... (The same goes for Mailman/MailList.py:414) 3. Mailman/MailList.py:623 (2.1a2), Mailman/Gui/General.py:295 (2.1a3) Maybe reverse the order of 'Yes' an 'No' for this options, so they are put in the same order as the other options that appear above it? 4. Mailman/MailList.py:672 Maybe mention list moderator(s) in the text? Because it could be the list moderator that approves the posting, not the list admin... Like this: "require approval - require list administrator or moderator approval for subscriptions<br>." 5. Mailman/MailList.py:734 There is a typo here. "to to": "[...] The intention is to to prevent the addresses [...]" 6. Mailman/MailList.py:743 reads: "Must posts be approved by an administrator?" Maybe mention the list moderator here too? Like: "Must posts be approved by an administrator (or possibly a moderator)?" 7. Mailman/MailList.py:755 This is really a minor cosmetic detail. The string is missing a ')', which should be added at the end of it. -- Daniel B. db@bibsys.no
"DB" == Daniel Buchmann <Daniel.Buchmann@bibsys.no> writes:
| 1. #: Mailman/Archiver/pipermail.py:276 | msgid "Reloading pickled archive state" I believe this is printed during bin/arch runs. | 2. #: Mailman/Archiver/pipermail.py:303 | msgid "Pickling archive state into " As is this, probably. | 3. #: Mailman/Bouncer.py:220 | msgid "BUT: %(succeeded)s" This is sent as part of the bounce.txt, when an address gets too many bounces and is disabled. | 4. #: Mailman/Cgi/admin.py:311 | msgid "No valid variable details request not found: %(path_info)s" | (I didn't really understand this one, is this a typo?) You're right, that makes no sense. :) | 5. #: Mailman/Handlers/Acknowledge.py:57 | msgid "%(realname)s post acknowledgement" If a user turns on their "Receive acknowledgement mail when you send mail to the list?" option, this gets sent to them when they post to the list. DB> I now have have 763 translated strings in my message.po :) I'm DB> skipping all docstrings and the strings for bin/pygettext.py. Good! DB> I'm also wondering how to make translated strings appear when DB> running any of the commands in <mailman-dir>/bin. When I run DB> e.g. check_perms, I still get "No problems found", not my DB> translated norwegian string... What I do is set the `LANGUAGE' environment variable to the language I want to test. E.g. % LANGUAGE=no bin/list_lists 1 matching mailing lists found: Stage - [ingen beskrivelse tilgjengelig] or % LANGUAGE=es bin/list_lists 1 Las siguientes listas de distribución coinciden: Stage - descripción: | 1. These two strings are the same, right? | #: Mailman/MailCommandHandler.py:411 | msgid "%(origsender)s isn't subscribed to this list." | and | #: Mailman/MailCommandHandler.py:436 | msgid "%(origsender)s is not subscribed to this list." DB> Maybe one of these could be chosen, so the same string is used DB> both places? (In norwegian, for example, the translation of DB> these to strings would be the same.) Yes, in fact there are other problems with the marked up strings in MailCommandHandler.py (not to mention that the whole module needs a serious rewrite... sigh). I'll try to fix the most egregious of the problems. | 2. Mailman/MailList.py:390 reads: | "[...] In order to split the list ownership duties into | administrators and moderators, you must set a separate moderator | password in the section below, and also provide the email | addresses of the list moderators in this section. [...]" DB> I think this text maybe should be rewritten a bit, because the DB> text does not appear where the user is setting the moderator DB> password, it appears in the help/details page for providing DB> email addresses of the list administrators. Maybe just removing DB> "in the section below" would do be enough... (The same goes DB> for Mailman/MailList.py:414) Good point, thanks. I think I can do a little bit better with some judicious hyperlinking. DB> 3. Mailman/MailList.py:623 (2.1a2), Mailman/Gui/General.py:295 DB> (2.1a3) DB> Maybe reverse the order of 'Yes' an 'No' for this options, DB> so they are put in the same order as the other options that DB> appear above it? Another good point, requiring some kludgery to get right though. :/ DB> 4. Mailman/MailList.py:672 DB> Maybe mention list moderator(s) in the text? Because it DB> could be the list moderator that approves the posting, not the DB> list admin... Like this: "require approval - require list DB> administrator or moderator approval for subscriptions<br>." Another good point, although I think it's fine just to say "list moderator". The user doesn't necessarily need to know about or understand the distinction (at this point). DB> 5. Mailman/MailList.py:734 DB> There is a typo here. "to to": DB> "[...] The intention is to to prevent the addresses [...]" Ah, thanks! DB> 6. Mailman/MailList.py:743 reads: DB> "Must posts be approved by an administrator?" Maybe DB> mention the list moderator here too? Like: "Must posts be DB> approved by an administrator (or possibly a moderator)?" Again, I think it's fine just to say "list moderator". DB> 7. Mailman/MailList.py:755 DB> This is really a minor cosmetic detail. The string is DB> missing a ')', which should be added at the end of it. Thanks, I've also added a hyperlink. Excellent feedback, thanks! -Barry
participants (2)
-
barry＠zope.com -
Daniel Buchmann