[Aside: I've created a Wiki page on the i18n effort. Please see http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/InternationalizedMail... for details, and remember! Anybody can edit these pages.]

...

...

...

...

"JCRA" == Juan Carlos Rey Anaya writes:

JCRA> I have been reading source files and determining which ones JCRA> must be marked because they have translatable messages. JCRA> I resolve to mark the following ones (I have skipped files JCRA> not related with translation): I ask for mailman developers JCRA> to confirm. Cool. I notice that you left all the bin scripts out. I wanted to get some personal experience marking and i18n'ing Mailman so I actually started with those and the cron scripts. As you know I'm also planning to require Python 2.0 for Mailman 2.1, so I've been rewriting some of these scripts to use the friendlier Python 2.0 features. I have spent a little time trying to mark files inside the Mailman dir, but not much really. Fortunately, I think our efforts overlap nicely. I think the way to proceed is to get the marking diffs into my tree asap, so that I can continue with my Python-2.0-ification. I need to integrate your markings first because otherwise I won't be able to apply your patches to my tree. So one question is whether you can split the marking changes from the other changes you've made to support i18n? One suggestion then would be for you to /not/ mark any files outside of the Mailman dir. I'll take care of those, and then we can fix any mistakes I make later. Second, don't mark any files inside Mailman that you haven't already marked (i.e. any that you labeled `N' as new for version 2). Similarly for the files you labeled `?'. I will do these. Third, any file that you labeled `L', that you've already marked for 1.2, you should go ahead and update those for Mailman 2.0. I will not touch those until I've integrated your patches. For the templates that just need translating, yes, please go ahead and do those. I think realistically, revamping the UI will likely be a 2.2 project. JCRA> I think the process should be like this: I will mark New JCRA> files (marked as N), and volunteers will upgrade files JCRA> marked yet in i18n version (marked as L). See above. Don't mark `N' or `?' files, but do update `L' files. | Templates to be updated | templates to be translated from scratch | Catalog to be updated: | Catalog to be translated from scratch: Okay, looks good. -Barry

"Barry A. Warsaw" wrote:

I notice that you left all the bin scripts out. I wanted to get some personal experience marking and i18n'ing Mailman so I actually started with those and the cron scripts.

Of course, feel like your own home :-)

Fortunately, I think our efforts overlap nicely. I think the way to proceed is to get the marking diffs into my tree asap, so that I can continue with my Python-2.0-ification. I need to integrate your markings first because otherwise I won't be able to apply your patches to my tree. So one question is whether you can split the marking changes from the other changes you've made to support i18n?

Well, I have said to contributors ONLY to mark. Other stuff like template selection or language selections shouldn't be done. That stuff will be added in a latter stage. Don't worry. I will send patches as soon as I have marked files. So the answer is Yes :-)

One suggestion then would be for you to /not/ mark any files outside of the Mailman dir. I'll take care of those, and then we can fix any mistakes I make later.

All right.

Second, don't mark any files inside Mailman that you haven't already marked (i.e. any that you labeled `N' as new for version 2). Similarly for the files you labeled `?'. I will do these.

Ok. -------------------------- Work to actual volunteers: -------------------------- 5) Juan C Rey: admin.py, admindb.py and edithtml.py

Third, any file that you labeled `L', that you've already marked for 1.2, you should go ahead and update those for Mailman 2.0. I will not touch those until I've integrated your patches.

For the templates that just need translating, yes, please go ahead and do those. I think realistically, revamping the UI will likely be a 2.2 project.

Ok. We will try to be faster than <em> we </em> can, won't be guys? :-) Cheers -- ___ / F \ [[[]]]] ( O O ) #----------------0000--(_)--0000---------------# | Juan Carlos Rey Anaya (jcrey@uma.es) | | Servicio Central de informática | | Universidad de Málaga - España | #----------------------------------------------# # Solo se que cada vez se menos :-| # #----------------------------------------------#

-------------------------- Work to actual volunteers: -------------------------- 2) Omar Walid Llorente: handle_opts.py, listinfo.py and options.py 12) Vizi Szilard: private.py, roster.py and subscribe.py There are no more files to assign for marking :-) I would like to send patches to Barry this weekend... cheers -- ___ / F \ [[[]]]] ( O O ) #----------------0000--(_)--0000---------------# | Juan Carlos Rey Anaya (jcrey@uma.es) | | Servicio Central de informática | | Universidad de Málaga - España | #----------------------------------------------# # Solo se que cada vez se menos :-| # #----------------------------------------------#