![](https://secure.gravatar.com/avatar/fbc0e910a6333a7b9af6b993358f4d38.jpg?s=120&d=mm&r=g)
Tzipi, I hope this is all making sense to you. :) Please ask if something is difficult to understand. We're giving you a lot of information all at once, so I will understand completely if you need to take it one piece at a time. Just ask for something to be explained, or for help with any task. :) On 25/04/2006, at 12:00 PM, Barry Warsaw wrote:
I don't think an entire translation would be needed, but you could start with say, all messages in listinfo.py and the listinfo.html template. That would be enough to give us a sense for how well the web u/i handles RTL. You might also try some of the messages in admin.py, then take a look at that.
I'd also suggest translating one or two of the command line scripts, then seeing how well those work. Follow that by some of the messages sent to users over email and you basically have coverage for the major touch points for RTL i18n.
This means, when you have read the Internationalization page and howto, and downloaded the Mailman 2.2 package, and created your directories, and have your own copy of mailman.po ready to translate, that in order to test Mailman's RTL support, you don't need to translate the whole file first. Each string in a .po file has an identification header. For example, the first string in the Mailman 2.2 mailman.po file is: #:Mailman/Archiver/HyperArch.py:122 msgid "size not available" msgstr "" The first line, starting with #. is the identification header of the string. It comes from a Python file (.py) named "HyperArch", and this string is line 122 in that file. What Barry is saying is, that for us to be able to test RTL support in Mailman, you only need to go through the mailman.po file and translate all the strings which have identification headers ending in: listinfo.py listinfo.html (one single, long string) admin.py plus one or two strings which are administrative scripts. They look like this (am I right, Barry? Or are the scripts different strings from this type?) : #:bin/config_list:117 msgid "" "# -*- python -*-\n" "# -*- coding: %(charset)s -*-\n" "## \"%(listname)s\" mailing list configuration settings\n" "## captured on %(when)s\n" msgstr "" and you simply copy the original string, then translate the parts that aren't %(placeholder)s and don't -*- look like this -*-. My translation for that string looks like this: #:bin/config_list:117 msgid "" "# -*- python -*-\n" "# -*- coding: %(charset)s -*-\n" "## \"%(listname)s\" mailing list configuration settings\n" "## captured on %(when)s\n" msgstr "# -*- python -*-\n" "# -*- coding: %(charset)s -*-\n" "## thiết lập cấu hình của hộp thư chung « %(listname)s »\n" "## bắt vào %(when)s\n" You must keep all the unusual characters in the original string, because they have their own jobs to do ... just like we do. ;) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN