Re: [Mailman-i18n] Using Pootle
On Mon, Jun 30, 2008 at 05:02:34PM +0000, "Sveinn í Felli (IMAP)" wrote:
Hi there:
Dov Zamir wrote:
<snip />
I'd be happy to add my 2 cents, but I really have no idea what this means :-(
Well, I don't really know the meaning excact of this string, but in headers of hebrew KDE.po files there's often the following line:
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
Best is to check with other translation groups (KDE, GNOME, GNU or whatever) or contact academic/linguistic specialists.
Well, using that as a base, I'm sure we can adjust if there's a problem. Once I added Hebrew as a language option from the pootle interface, it picked up what was on disk right away: http://pootle.metalab.unc.edu/he/mailman/LC_MESSAGES/? Any other languages missing? Cheers, -- Cristóbal Palmer ibiblio.org systems administrator
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cristóbal Palmer wrote: | Any other languages missing? There are several in the table at <http://garp.metalab.unc.edu:8080/projects/mailman/> that seem to be pointing at empty or non-existent mailman.po files or have some other problem which results in all zeros in the table. These are Danish, French, German, Hungarian, Lithuanian, Slovenian, Spanish and Swedish. The following languages which have translations on both the 2.1 branch and the 3.0 branch are totally missing: Estonian (et), Croatian (hr), Interlingua (ia) and Norwegian (no). There are three 2.1 translations that are not currently in 3.0. These are Galician (gl), Hebrew (he) and Slovak (sk), although all three are in the table at <http://garp.metalab.unc.edu:8080/projects/mailman/>. There are issues between 2.1 and 3.0 that will be resolved, but aren't yet. A couple of years ago the trunk which became the 3.0 branch was changed to include the templates in the message catalog. This is good as it puts all the translation in one place. However, since that was done, there has been much updating including the addition of the above mentioned three languages which is not reflected in the 3.0 branch. So, we need to make a consistent base to work from. This could be the 2.1 branch as it has the most up to date translations, but it doesn't have the templates in the message catalog. I am willing to work on this, but right now, I need a little break. - -- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFIaX5/VVuXXpU7hpMRAuvLAJ9bzFzWQkDPaCu88W3eZ24lliV+MACghRZr Qn2FDGxliwtX4DDiHj8mXJU= =cD57 -----END PGP SIGNATURE-----
On Mon, Jun 30, 2008 at 05:46:55PM -0700, Mark Sapiro wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Cristóbal Palmer wrote:
| Any other languages missing?
There are several in the table at <http://garp.metalab.unc.edu:8080/projects/mailman/> that seem to be pointing at empty or non-existent mailman.po files or have some other problem which results in all zeros in the table.
These are Danish, French, German, Hungarian, Lithuanian, Slovenian, Spanish and Swedish.
Fixed. Having talked to the pootle devs, it seems the problem had to do with the translate toolkit assuming utf8 until it got to the header that declares the charset, which was Bad (tm). I've updated pootle.metalab to use a newer version of the toolkit that closes that bug. Those languages all show up properly now.
The following languages which have translations on both the 2.1 branch and the 3.0 branch are totally missing: Estonian (et), Croatian (hr), Interlingua (ia) and Norwegian (no).
There are three 2.1 translations that are not currently in 3.0. These are Galician (gl), Hebrew (he) and Slovak (sk), although all three are in the table at <http://garp.metalab.unc.edu:8080/projects/mailman/>.
(et), (hr), (ia), and (no) can be resolved by adding those languages within pootle, but that may require knowing a bit about how plurals are computed in those languages and some other details that I'm loathe to guess at on my own. Anybody who has admin access to the pootle.metalab web interface (currently me, Barry & Clytie) can add those languages, but I'm not sure any of us knows what the "proper" values are for the blanks in the form at the bottom of http://pootle.metalab.unc.edu/admin/languages.html to add a language.
There are issues between 2.1 and 3.0 that will be resolved, but aren't yet. A couple of years ago the trunk which became the 3.0 branch was changed to include the templates in the message catalog. This is good as it puts all the translation in one place. However, since that was done, there has been much updating including the addition of the above mentioned three languages which is not reflected in the 3.0 branch.
So, we need to make a consistent base to work from. This could be the 2.1 branch as it has the most up to date translations, but it doesn't have the templates in the message catalog. I am willing to work on this, but right now, I need a little break.
Take your time. :) Let me know what my next step is if y'all need me to make changes on my end of things. Cheers, -- Cristóbal Palmer ibiblio.org systems administrator
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 2, 2008, at 2:03 PM, Cristóbal Palmer wrote:
Let me know what my next step is if y'all need me to make changes on my end of things.
I feel like a complete idiot because I simply cannot find where to download the .po files from. Have you figured that out yet? Thanks, - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSGxmJnEjvBPtnXfVAQL0xAQAp70q2sGC54pCrpfoS7jRcbXco7E3sQy5 jaceKSCP9/GaPd3jHvnOetrIZl0/Fr++W0ozEQ4Lm8Na3myDefrvWl/2Ui6X/Nem UIbLz3z/DLAul6kDrTW1KmLIlLB7HNhnHRNfAtpdmlkZfR6rPF0EuhUnYrhtIH+/ wWlLz4o4aW0= =Lh7D -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jun 30, 2008, at 8:46 PM, Mark Sapiro wrote:
There are issues between 2.1 and 3.0 that will be resolved, but aren't yet. A couple of years ago the trunk which became the 3.0 branch was changed to include the templates in the message catalog. This is good as it puts all the translation in one place. However, since that was done, there has been much updating including the addition of the above mentioned three languages which is not reflected in the 3.0 branch.
So, we need to make a consistent base to work from. This could be the 2.1 branch as it has the most up to date translations, but it doesn't have the templates in the message catalog. I am willing to work on this, but right now, I need a little break.
I agree that we should use the 2.1 branch as the best basis from which to start. I think there will be much more similarity between the 2.1 and (hopeful) 2.2 branches, all depending on what happens with the web u/i. As for the templates, while I think moving them into the catalogs is a win over what we had, I still hope that we'll eventually (maybe just for 3.0) switch to a i18n-friendly templating engine, where only the translatable strings will be extracted into the catalog, with all the other HTML goo stripped out. A translator should not have to worry about that stuff! 3.0 is a long way from needing translation, so let's concentrate on getting a good prototype based on the 2.1 strings, eventually migrating them to 2.2 as development on that branch ramps up. I suspect there will be some decent overlap between 2.2 and 3.0. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSGxjBHEjvBPtnXfVAQKaFgQAmZzVd2sDXQ18HtltJPPSLpEAqBLbqzwb Kcyhh+s8VOd30EKbG830rvpEBjmYLAqVfEFfoyP+RUIYTnRxDaVA+Ct/a3VTRSzN om+hUIxXzy/7lhdkjxC9BrUfWsniVwG2DpyB/krBaChMIQyp/iekAfFaUuAUgbPp cI02UjafwI4= =F5im -----END PGP SIGNATURE-----
participants (3)
-
Barry Warsaw -
Cristóbal Palmer -
Mark Sapiro