Bugs item #1453049, was opened at 2006-03-18 18:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1453049&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Clytie Siddall (clytie) Assigned to: Nobody/Anonymous (nobody) Summary: Typos in the Mailman 2.1.8a PO file Initial Comment: 1. po:670 reference: ⑤ Mailman/Gui/ContentFilter.py:130 Original: ⌘0 One of these actions is take when the message matches one of\n the content filtering rules, <snip> - is take + is taken 2. po:717 reference: ⑤ Mailman/Gui/General.py:143 Original: ⌘0 This text will be prepended to subject lines of messages \n posted to the list, to distinguish mailing list messages in in\n mailbox summaries. Brevity is premium here, it's ok to shorten\n long mailing list names to something more concise, as long as it\n still identifies the mailing list.\n You can also add a sequencial number <snip> - messages in in mailbox summaries + messages in mailbox summaries - sequencial + sequential 3. po:785 reference: ⑤ Mailman/Gui/NonDigest.py:129 Original: ⌘0 Text prepended to the top of every immediately-delivery \n message. - immediately-delivery + immediate-delivery (OR + immediately-delivered) Also in this string: .po:787 reference: ⑤ Mailman/Gui/NonDigest.py:134 Original: ⌘0 Text appended to the bottom of every immediately- delivery\n message. 4. po:789 reference: ⑤ Mailman/Gui/NonDigest.py:141 Original: ⌘0 When you scrub attachments, they are stored in archive\n area and links are made in the message so that the member can\n access via web browser. If you want the attachments totally\n disappear, you can use content filter options. + When you scrub attachments, they are stored in the archive and accessible to the member via web-browser links in the message. If you want to get rid of attachments completely, you can use the content filter options. 5. po:828 reference: ⑤ Mailman/Gui/Privacy.py:244 Original: ⌘0 Postings from any of these non-members will be automatically\n accepted with no further moderation applied. Add member\n addresses one per line; start the line with a ^ character to\n designate a regular expression match. In several strings about "non-members", the sentence beginning "Add member addresses one per line" still occurs. It should probably be changed, in those strings, to "Add non-member addresses one per line". The other strings are: .po:830 reference: ⑤ Mailman/Gui/Privacy.py:253 Original: ⌘0 Postings from any of these non-members will be immediately\n and automatically held for moderation by the list moderators. \n The sender will receive a notification message which will allow\n them to cancel their held message. Add member addresses one per\n line; start the line with a ^ character to designate a regular\n expression match. .po:832 reference: ⑤ Mailman/Gui/Privacy.py:264 Original: ⌘0 Postings from any of these non-members will be automatically\n rejected. In other words, their messages will be bounced back to\n the sender with a notification of automatic rejection. This\n option is not appropriate for known spam senders; their messages\n should be\n <a href=\"?VARHELP=privacy/sender/ discard_these_nonmembers\"\n >automatically discarded</a>.\n \n <p>Add member addresses one per line; start the line with a ^\n character to designate a regular expression match. po:834 reference: ⑤ Mailman/Gui/Privacy.py:279 Original: ⌘0 Postings from any of these non-members will be automatically\n discarded. That is, the message will be thrown away with no\n further processing or notification. The sender will not receive\n a notification or a bounce, however the list moderators can\n optionally <a href=\"?VARHELP=privacy/sender/ forward_auto_discards\"\n >receive copies of auto-discarded messages.</a>.\n \n <p>Add member addresses one per line; start the line with a ^\n character to designate a regular expression match. 6. Here you create two strings to show plural forms: po:892 reference: ⑤ Mailman/HTMLFormatter.py:80 Original: ⌘0 <em>(1 private member not shown)</em> .po:893 reference: ⑤ Mailman/HTMLFormatter.py:82 Original: ⌘0 <em>(%(num_concealed)d private members not shown) </em> but this is not effective for translation. The gettext plurals feature makes it possible for translators to input the correct number of plurals for their language. English may need two forms, singular and plural, but my language is one of several which have _no_ plural forms in this sense, and there are European languages which have more than two forms. If you don't use the gettext plurals feature, we can't translate those strings effectively. Gettext will output the correct number of plurals fields for each language, by parsing the plurals string in the PO file header. In my case, that will avoid me inputting the same translation twice in several places in this file. In the case of languages with more plural forms than English, it will avoid incomplete translations or translations that simply don't make sense. Please see the gettext manual for further information: http://www.gnu.org/software/gettext/manual/html_mono/ gettext.html#SEC150 7. po:906 reference: ⑤ Mailman/HTMLFormatter.py:195 Mailman/ HTMLFormatter.py:202 Original: ⌘0 also po:908 reference: ⑤ Mailman/HTMLFormatter.py:206 Original: ⌘0 This is %(also)sa private list, which means that the\n list of members is not available to non-members. This is likely to cause errors in translation. Although it means translating six strings instead of three, we can cut and paste most of the string, and we can be sure, that way, of correct translations. Please don't take short-cuts on translation, unless you are sure they will not affect the quality of the translation. 8. Original: ⌘0 Rebuild a list's archive.\n \n <snip> -e M\n --end=M\n End indexing at article M. This script is not very efficient with\n respect to memory management, and for large archives, it may not be\n possible to index the mbox entirely. For that reason, you can specify\n the start and end article numbers.\n \n Where <mbox> is the path to a list's complete mbox archive. Usually this will\n There seems to be something missing here, between "the start and end article numbers" and "Where <mbox> is the path", because "where" in this context is a conjunction, joining a previous statement to this one. However, there is a full stop and two line breaks in between, indicating a statement well and truly finished. What is missing here? 9. po:1069 reference: ⑤ bin/b4b5-archfix:19 Original: ⌘0 Fix the MM2.1b4 archives.\n \n Usage: %(PROGRAM)s [options] file ...\n \n Where options are:\n -h / --help\n Print this help message and exit.\n \n Only use this to `fix' some archive database files that may have gotten \n written in Mailman 2.1b4 with some bogus data. Use like this from your\n $PREFIX directory\n<snip> - Use like this + Use it like this OR + Use the command like this (Syntax error: transitive verb must have object.) 10. po:1111 reference: ⑤ bin/clone_member:19 Original: ⌘0 Clone a member address.\n <snip> Usage:\n clone_member [options] fromoldaddr tonewaddr\n \n Where:\n \n --listname=listname\n -l listname\n <snip> - Where + Options Also occurs in these strings: po:1149 reference: ⑤ bin/find_member:19 Original: ⌘0 Find all lists that a member's address is on.\n \n Usage:\n find_member [options] regex [regex [...]]\n \n Where:\n --listname=listname\n -l listname\n .po:1161 reference: ⑤ bin/list_admins:19 Original: ⌘0 List all the owners of a mailing list.\n \n Usage: %(program)s [options] listname ...\n \n Where:\n \n --all-vhost=vhost\n -v=vhost\n po:1163 reference: ⑤ bin/list_lists:19 Original: ⌘0 List all mailing lists.\n \n Usage: %(program)s [options]\n \n Where:\n \n -a / --advertised\n List only those mailing lists that are publically advertised\n .po:1166 reference: ⑤ bin/list_members:19 Original: ⌘0 List all the members of a mailing list.\n \n Usage: %(PROGRAM)s [options] listname\n \n Where:\n \n --output file\n -o file\n po:1220 reference: ⑤ bin/rmlist:19 Original: ⌘0 Remove the components of a mailing list with impunity - beware!\n \n This removes (almost) all traces of a mailing list. By default, the lists\n archives are not removed, which is very handy for retiring old lists.\n \n Usage:\n rmlist [-a] [-h] listname\n \n Where:\n --archives\n -a\n po:1254 reference: ⑤ bin/unshunt:19 Original: ⌘0 Move a message from the shunt queue to the original queue.\n \n Usage: %(PROGRAM)s [options] [directory]\n \n Where:\n \n -h / --help\n Print help and exit.\n 11. po:1142 reference: ⑤ bin/dumpdb:19 Original: ⌘0 Dump the contents of any Mailman `database' file.\n \n Usage: %(PROGRAM)s [options] filename\n \n Options:\n \n --marshal/-m\n Assume the file contains a Python marshal, overridding any automatic\n guessing.\n<snip> - overridding + overriding 12. (Also from the above string...) The interaction between -l and -x is as follows. If any -l option is given\n then only the named list will be included in the search. If any -x option is\n given but no -l option is given, then all lists will be search except those \n specifically excluded.\n - all lists will be search + all lists will be searched 13. .po:1166 reference: ⑤ bin/list_members:19 Original: ⌘0 List all the members of a mailing list.\n <snip> Print the members that have delivery disabled. Optional argument can\n be \"byadmin\", \"byuser\", \"bybounce\", or \"unknown\" which prints just the\n users who have delivery disabled for that reason. It can also be\n \"enabled\" which prints just those member for whom delivery is \n enabled.\n<snip> - the members that have delivery disabled + the members who have delivery disabled - which prints just those member + which prints just those members 14. po:1170 reference: ⑤ bin/list_owners:19 Original: ⌘0 List the owners of a mailing list, or all mailing lists.\n \n Usage: %(PROGRAM)s [options] [listname ...]\n Options:\n \n -w / --with-listnames\n Group the owners by list names and include the list names in the \n output. Otherwise, the owners will be sorted and uniquified based on\n the email address.\n - uniquified + identified There is no such word "uniquify" in common usage. Identification within a group is based on unique qualities, so "identified" is appropriate. 15. .po:1171 reference: ⑤ bin/mailmanctl:19 Original: ⌘0 Primary start-up and shutdown script for Mailman's qrunner daemon.\n \n<snip> Note though, that if you run with -u and are not in the mailman group,\n you may have permission problems, such as begin unable to delete a\n list's archives through the web. Tough luck!\n<snip> - such as begin unable to + such as being unable to 16. po:1200 reference: ⑤ bin/newlist:19 Original: ⌘0 Create a new, unpopulated mailing list.\n \n Usage: %(PROGRAM)s [options] [listname [listadmin-addr [admin- password]]]\n \n<snip> E.g. with this setting people will view the general list\n overviews at http://www.mydom.ain/mailman/listinfo. Also, www.mydom.ain\n should be a key in the VIRTUAL_HOSTS mapping in mm_cfg.py/ Defaults.py if\n the email hostname to be automatically determined.\n - if the email hostname to be automatically determined.\n + if the email hostname is to be automatically determined.\n 17. Options:\n \n -r runner[:slice:range]\n --runner=runner[:slice:range]\n Run the named qrunner, which must be one of the strings returned by\n the -l option. Optional slice:range if given, is used to assign\n multiple qrunner processes to a queue. range is the total number of\n qrunners for this queue while slice is the number of this qrunner from\n [0..range).\n \n If using the slice:range form, you better make sure that each qrunner\n for the queue is given the same range value. If slice:runner is not\n given, then 1:1 is used.\n - If slice:runner is not given + If slice:range is not given 18. po:1283 reference: ⑤ bin/update:585 Original: ⌘0 Ignoring bad pended data: %(key)s: %(val)s - pended data + pending data OR + appended data OR (prepended/suspended etc.) 19. po:1300 reference: ⑤ bin/withlist:19 Original: ⌘0 General framework for interacting with a mailing list object.\n <snip l-o-n-g string in between> Now, from the command line you can print the list's posting address by running\n the following from the command line:\n - Now, from the command line you can print the list's posting address by running\n the following from the command line:\n + Now, you can print the list's posting address by running\n the following from the command line:\n (you've repeated "from the command-line" in this string) from Clytie, Vietnamese translator (I'm about to add the Vietnamese translation) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1453049&group_id=103