Dominique | 6 Nov 17:49 2000
Picon

please procure us one french translation! thanks

 
 
 
            
 
 
 
hello manager for mailing list!
LET US BETTER UNDERSTEEN IF YOU SEND US ONE PERSONALISED ANSWER IN THE FRENCH TRANSLATION!
THANKS
DACHI
CHAIRMAN H.C.
9.40 PM TAHITI-TIME
Diego Brouard | 8 Nov 16:08 2000

traducción al español

hi, we are begining to work with Mailman inside our server, and we are going to traduce
the Mailman archives to spanish. If someone has do it now, or is working in the same way,
please contact me, so we can work together.

Thanks, Gracias

Greetings, Saludos
					Diego Brouard

Juan Carlos Rey Anaya | 8 Nov 18:46 2000
Picon

Re: traducción al español

Diego Brouard wrote:
> 
> hi, we are begining to work with Mailman inside our server, and we are going to traduce
> the Mailman archives to spanish. If someone has do it now, or is working in the same way,
> please contact me, so we can work together.

Where were you two weeks ago?.
We are going (soon, very soon...) to start to internationalize mailman
2.0. I must suppose you are willing to help :-)

I shall send you homework ;-)

Seeing that you are going to translate templates, it must be noted that
spanish templates are translated yet. I will send you translated
templates so you can upgrade them.

Cheers
--

-- 
                          ___
                         / F \
                        [[[]]]]
                        ( O O )
   #----------------0000--(_)--0000---------------#
   |    Juan Carlos Rey Anaya (jcrey <at> uma.es)      |
   |      Servicio Central de informática         |
   |       Universidad de Málaga - España         |
   #----------------------------------------------#
   #      Solo se que cada vez se menos :-|       #
   #----------------------------------------------#

Juan Carlos Rey Anaya | 8 Nov 20:06 2000
Picon

Mailman i18n - First piece

On Wed, 25 Oct 2000, Barry A. Warsaw wrote:

> 
> One piece is marking all the translatable text in the Mailman sources.
> You should work on this last and don't spend much time on it.  I'm
> actually starting to do that myself, as I'm playing with the i18n
> infrastructure.

Hello everybody.

I have been reading source files and determining which ones must be
marked because they have translatable messages.

I resolve to mark the following ones (I have skipped files not related
with translation): I ask for mailman developers to confirm.

notation:

N - new file in version 2, it didn't exist in 1.2, it must be marked
from scratch
Z - created in internationalization of version 1.2
? - I really don't know if it should be marked
L - Already marked in internationalized 1.2 version - Needs to be
upgraded.

|-- Mailman
|   |-- Archiver
|   |   |-- Archiver.py      (L)
|   |   |-- HyperArch.py     (N?)
|   |   |-- HyperDatabase.py (N?)
|   |   `-L pipermail.py     (L)
|   |-- Autoresponder.py     (N)
|   |-- Bouncer.py           (L)
|   |-- Bouncers
|   |   |-- SimpleMatch.py   (N?)
|   |-- Cgi
|   |   |-- Auth.py          (N)
|   |   |-- admin.py         (L)
|   |   |-- admindb.py       (L)
|   |   |-- edithtml.py      (L)
|   |   |-- handle_opts.py   (L)
|   |   |-- listinfo.py      (L)
|   |   |-- options.py       (L)
|   |   |-- private.py       (L)
|   |   |-- roster.py        (L)
|   |   `-- subscribe.py     (L)
|   |-- Defaults.py          (L)
|   |-- Deliverer.py         (L)
|   |-- Digester.py          (L)
|   |-- GatewayManager.py    (L)
|   |-- HTMLFormatter.py     (L)
|   |-- Handlers
|   |   |-- Acknowledge.py (L)
|   |   |-- CookHeaders.py (L)
|   |   |-- HandlerAPI.py  (L)
|   |   |-- Hold.py        (L)
|   |   |-- ToDigest.py    (L)
|   |   |-- ToUsenet.py    (L)
|   |-- ListAdmin.py       (L)
|   |-- MailCommandHandler.py (L)
|   |-- MailList.py           (L)
|   |-- Utils.py              (L)
|   |-- htmlformat.py         (L)
# jcrey
# this ones only must be translated/upgraded not marked
`-- templates
    |-- admindbpreamble.html    (L)
    |-- adminsubscribeack.txt   (L)
    |-- adminunsubscribeack.txt (L)
    |-- admlogin.txt            (L)
    |-- approve.txt             (L)
    |-- bounce.txt              (L)
    |-- checkdbs.txt            (L)
    |-- convert.txt             (L)
    |-- cronpass.txt            (L)
    |-- handle_opts.html        (L)
    |-- headfoot.html           (N)
    |-- help.txt                (L)
    |-- listinfo.html           (L)
    |-- masthead.txt            (L)
    |-- newlist.txt             (L)
    |-- nopass.txt              (L)
    |-- options.html            (L)
    |-- postack.txt             (L)
    |-- postauth.txt            (L)
    |-- postheld.txt            (L)
    |-- reenable.txt            (L)
    |-- refuse.txt              (L)
    |-- roster.html             (L)
    |-- subauth.txt             (L)
    |-- subscribe.html          (L)
    |-- subscribeack.txt        (L)
    |-- userpass.txt            (L)
    |-- verify.txt              (L)
    |-- msgdecorationote.txt    (Z)
    |-- private.txt             (Z)

I think the process should be like this:
I will mark New files (marked as N), and volunteers will upgrade files
marked yet in i18n version (marked as L).

Volunteers will mark files to be updated (marked as L). I will send to
this list, i18n file and file to be marked in order to get the final
process easier. Changes should be sent to either my e-mail or to this
list.

Subsequent changes are subordinated to CVS updates :-(

Some informational status...

Templates to be updated:
------------------------
- Spanish
- Italian (Pioppo  <pioppo <at> ferrara.linux.it> Where are you? :-)

templates to be translated from scratch
---------------------------------------
Remaining languages...

Catalog to be updated:
----------------------
- German (last translation done by Peter Muessig-Trapp and company)
- Danish (last translation done by Mads Kiilerich)
- Italian (last translation done by Pioppo)
- Spanish (last translation performed by Eduardo Fernandez Corrales and
me)

Catalog to be translated from scratch:
--------------------------------------
Remaining languages...

--------------------------
Work to actual volunteers:
--------------------------
1) Félix Sánchez: Archiver.py, pipermail.py and Bouncer.py
2) Omar Walid Llorente: Deliverer.py, Digester.py and GatewayManager.py
3) Eric de Hont: HTMLFormatter.py, Acknowledge.py and CookHeaders.py
4) Diego Brouard: upgrade templates in spanish and translate new file
(headfoot.html)
5) Juan C Rey: HyperArch.py, Autoresponder.py and Auth.py

More volunteers?

Cheers
--

-- 
                          ___
                         / F \
                        [[[]]]]
                        ( O O )
   #----------------0000--(_)--0000---------------#
   |    Juan Carlos Rey Anaya (jcrey <at> uma.es)      |
   |      Servicio Central de informática         |
   |       Universidad de Málaga - España         |
   #----------------------------------------------#
   #      Solo se que cada vez se menos :-|       #
   #----------------------------------------------#

Simone Piunno | 8 Nov 21:44 2000
Picon

Re: Mailman i18n - First piece

mercoledì, 08 novembre 2000 alle 20:06:39, Juan Carlos Rey Anaya ha scritto:

> Templates to be updated:
> ------------------------
> - Italian (Pioppo  <pioppo <at> ferrara.linux.it> Where are you? :-)

> Catalog to be updated:
> ----------------------
> - Italian (last translation done by Pioppo)

here I am! :)
I can update my previous work and I'm waiting instructions.
For templates I can start from the standard MM 2.0 tar.gz 
but for the catalog I have to wait your work.
Is this correct?

--

-- 
If the human brain were so simple that we could understand it,
we would be so simple we couldn't.

Barry A. Warsaw | 9 Nov 02:32 2000

Re: Mailman i18n - First piece

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

>>>>> "JCRA" == Juan Carlos Rey Anaya <jcrey <at> uma.es> 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 | 9 Nov 02:39 2000

Re: Internationalized Mailman

    BAW> One piece is marking all the translatable text in the
    BAW> Mailman sources.  You should work on this last and don't
    BAW> spend much time on it.  I'm actually starting to do that
    BAW> myself, as I'm playing with the i18n infrastructure.

    VG> This is the cornerstone of the I18N effort. The problem is
    VG> that it can block the testing of the other pieces.

Not necessarily.  We don't have to have absolutely all of the code
marked to start integrating the pieces and making sure the
infrastructure works as intended.

    VG> This part has, also, been done with 1.2, which we have
    VG> successfully put into production due to managerial decisions
    VG> in our University. It works like charm, except some glitches
    VG> that Juan C. has patched.

Cool!

    VG> To get this functionallity we have
    VG> done the following changes and additions:

    | + To the list object:
    | - Added 'preferred_language' attribute, for the list default
    | language
    | - Added 'language' dictionary with the users' preferred language,
    | the user mailaddress is the key to get the language she
    | has set for the list.
    | - Added the neccesary methods for setting and getting these.
    | - Added a method for listing the available languages for the list.

Looks good.

    | + Created functions in Utilites for:
    | - Getting the server available languages.
    | - Getting the language descriptions.
    | - Getting the language charset.

Looks good.

    | + HTML formatting.
    | - Add the necesary code for generating selects.

Cool.

    | + Default.py
    | - Some Barry Warsaw, decided to put the common code for language
    | initialization at the bottom of this module.

:)

    | + Showering all over the code.
    | - Added the necesary changes for language selection.

Okay, I'd definitely like to see this part.

    | + Storage.
    | - Creating directories for holding language specific files in
    | every list.
    | - Creating directory hierarchy for catalogs and templates.

And this.

    | + Support scripts.
    | - newlang, to add languages to a list.
    | - rmlang, opposite of above.

Good.

    | + gettext.py
    | - Modify to addapt to our requirements. (Changes sent to author).

Okay.  Here we want to use Python 2.0's gettext module.  If there are
problems with that, then we want to fix it (and if necessary, ship the
fixed version in pythonlib for a while).  Mailman is going to be one
of the first Python applications I can think of that will be
internationalized, so it's a guinea pig for Python's i18n support too!

    VG> As you can see this is a surgeon's task. This part must be
    VG> carefully done by a very reduced team ( = JCR+VG :)

Completely agree!  And I'm going to have to spend some serious time
integrating and proofing it all too.  I have to understand how it all
works.  That's where breaking it down into the smallest cohesive chunks
possible will really help.

    VG> We have a good team of volunteers for some languages, which
    VG> have already done translations of the .po files for 1.2 into
    VG> danish, english, german, italian, spanish and mostly
    VG> czec. Some others have shown interest in languages as
    VG> gallician, basque, japanesse, brazilian/portuguesse and
    VG> dutch. We think this could proceed in parallel with the second
    VG> piece, of course, it cannot start before we have done the
    VG> first piece.

Awesome.
-Barry

Juan Carlos Rey Anaya | 9 Nov 14:38 2000
Picon

Re: Mailman i18n - First piece

Simone Piunno wrote:
> 
> here I am! :)
Hello again ;-)

> I can update my previous work and I'm waiting instructions.
Well, because you already have italian templates, you can start to
upgrade templates. You had i18n stuff inside v1.2 templates, so (I
suppose) you have to correct minor changes.

> For templates I can start from the standard MM 2.0 tar.gz
I will send you the ones I have here. I'm updating CVS every morning.

> but for the catalog I have to wait your work.
> Is this correct?
Correct

Cheers
--

-- 
                          ___
                         / F \
                        [[[]]]]
                        ( O O )
   #----------------0000--(_)--0000---------------#
   |    Juan Carlos Rey Anaya (jcrey <at> uma.es)      |
   |      Servicio Central de informática         |
   |       Universidad de Málaga - España         |
   #----------------------------------------------#
   #      Solo se que cada vez se menos :-|       #
   #----------------------------------------------#

Juan Carlos Rey Anaya | 9 Nov 14:43 2000
Picon

Re: Mailman i18n - First piece

Dan Ohnesorg wrote:
> 
> On Wed, 8 Nov 2000, Juan Carlos Rey Anaya wrote:
> 
> > templates to be translated from scratch
> > ---------------------------------------
> > Remaining languages...
> 
> Czech will be ready soon, but the templates chnged betwwen 1.x and 2.x is
> there some internationalized templates in 2.x format?
No

> > More volunteers?
> 
> Yes, I
Ok. I will send you v1.2 English templates. Your work consist in
upgrading to v2.0 templates and inserting i18n stuff inside templates
(and of course translate :-D)

Catalog will be forward.

Cheers
--

-- 
                          ___
                         / F \
                        [[[]]]]
                        ( O O )
   #----------------0000--(_)--0000---------------#
   |    Juan Carlos Rey Anaya (jcrey <at> uma.es)      |
   |      Servicio Central de informática         |
   |       Universidad de Málaga - España         |
   #----------------------------------------------#
   #      Solo se que cada vez se menos :-|       #
   #----------------------------------------------#

Juan Carlos Rey Anaya | 9 Nov 15:07 2000
Picon

Re: traducción al español

Leo Mauro wrote:
> 
> Would you mind keeping me on the loop?

Welcome!

Your work consists marking:
HandlerAPI.py, Hold.py and ToDigest.py

I shall send to your private e-mail both v1.2 i18n files and v2.0 ones.

Cheers
--

-- 
                          ___
                         / F \
                        [[[]]]]
                        ( O O )
   #----------------0000--(_)--0000---------------#
   |    Juan Carlos Rey Anaya (jcrey <at> uma.es)      |
   |      Servicio Central de informática         |
   |       Universidad de Málaga - España         |
   #----------------------------------------------#
   #      Solo se que cada vez se menos :-|       #
   #----------------------------------------------#


Gmane