I'm sending this here because it is language related, sorry if this is not
the list to post it.
First I see that for the Spanish language we are having iso-8859-1 instead
of iso-8859-15 which would allow us to use the euro symbol and all that.
Second, I see an anoyance when running lists in a country that different
language are used, or even with certain mailers alone, the problem is this:
Suppose I have a list which default language is using charset iso-8859-1,
then somebody comes and posts in iso-8859-15 and you get it all in three
mime parts, one for the header, in iso-8859-1, one for the body in
iso-8859-15 and then the footer in iso-8859-1 again. This seems quite
anoying, at least when yo look at it. I was wondering if there is, or if it
would make sense to add, something so that this doesn't happen.
Also I see something that is for sure doable, and it is that when the same
person writes with some mailers like mutt and doesn't use any 8 bits
character, then the mailer would encode the text as us-ascii, which if I'm
not wrong, should mix ok with iso-8859-1, I mean that the hole message could
come as one using iso-8859-1, and that is not done right now.
Well, just a couple of ideas, that's all.
Manty/BestiaTester -> http://manty.net
I am HAPPY TO do this ! What can i do ? Translate all files in the folder message and template ?
======= 2003-09-22 18:47:00 =======
>On Fri, 2003-09-19 at 04:19, 刘策 wrote:
>> Hello,Tokio Kikuchi！
>> Thank you again.
>> I set DEFAULT_SERVER_LANGUAGE='gb', and then all be ok.
>I get the feeling that Mailman's Chinese support isn't very good. Would
>you guys help me improve things for Mailman 2.1.4?
In the file $mailman/Mailman/Queue/ArchRunner.py , the __doc__ is """Outgoing queue runner.""". IS the __doc__ """Arch queue runner"""?
When a mail with a attachment, and the attachment name is encoding by base64, mailman can't generate a right link to this attachment in the page in Archives.
= = = = = = = = = = = = = = = = = = = = = =
北 京 华 晨 阳 通 信 技 术 有 限 责 任 公 司
Beijing HCYCOM Communication Technologies Co.,LTD.
地 址: 北京市海淀区塔院朗秋园甲8号
邮 编: 100083
电 话: (010) 62018037―1024
网 址: www.hcycom.com
I'm trying to get started in the translation work for Swedish, but I'm not
too friendly with the CVS system... I use TortoiseCVS for Windows to check
out files, and I wonder HOW DO I DO...? To just check out the latest files?
There are several branches in the CVS tree, but I can't see the use of
downloading them all, just the latest versions, both production and
I'm almost finish with croatian translation (without unix scripts
translations) but i'm having some troubles making it work. I tried msgfmt
the croatian.po file and it was processed normally, without errors,
creating the proper mailman.mo file. I also added add_language line to
the Defaults.py, but when I chose Croatian language for default (from
the web page interface) I still got those pages in english? So, what's
wrong here? I did everything like in README-I18N.txt
One of the biggest pains for me lately has been managing the .po file
catalogs across the HEAD and the 2.1-maint branch. Don't get me wrong,
you guys have done a superb job of managing the i18n stuff, and you have
definitely helped make my life easier, but it seems that the po files,
the templates, and cvs just don't mix well.
Things are going to get worse as the head diverges from the 2.1-maint
branch. This is going to start happening soon as I start to work on
Mailman 2.2. We had talked before about moving Mailman's i18n work to
the Translation Project, and I think now's the perfect time to
I don't have any direct experience with TP, so first, I'm wondering who
out there has, and what you think about it. My impressions from reading
the site are that, while incomplete in some ways, it provides some
useful facilities that will help separate the concerns of translators
and Mailman developers. The major trade-off appears to be that you
translators will lose a bit of independence, since you'll be working
within the umbrella of TP language teams. What you gain for that is
hopefully more help from other members of your language team. I'm
pretty sure you can still concentrate your volunteer efforts on
translating Mailman though.
The alternative for going to TP would be for me to pull the messages
subdir out of the top-level directory, and manage that outside of any
CVS branches. It would take a little bit of cvs weaving to get a source
build of Mailman from CVS, but I don't think that would be too painful.
Note that I'm already planning on doing some CVS reorganization in
preparation for 2.2 (more on that to the -developers list later).
The other i18n change I'm planning is to adopt ZPT for the templates. I
think we don't have to wait for MM3.0 for that, and it will have many
great advantages. For i18n, the major advantages is that it means you
will no longer have to translate whole templates -- we can mark
translatable strings in the ZPT, and extract them to the .pot file, so
there's only one set of texts you need to translate.
Thoughts? It seems relatively easy to register with TP, and start
working with them, and if you all are generally in favor of this, I'd
like to do it sooner rather than later.
We have the .po file already translated into catalan and one of the testers is asking me whether that file contains the text for the mails mailman sends and the html templates text. Checking the mailman files, I can see these files:
Do we need to translate those files as well?
Is there any possible place where we could test the translation as it progresses?
Maybe you can set up something temporary at your place, Barry?
I' ve talked to the hosting company who I'm paying for webspace, but they told me it's impossible to arrange that kind of testing, because it invloves root access...
Simone Piunno wrote:
> > Is there any possible place where we could test the translation as it
> > progresses? Maybe you can set up something temporary at your place, Barry?
> I believe the best you can do is... to install it on your own PC!
I am in an urge need of the instructions, how the hell one can tweak the Windows station to be able to run Mailman and *nix commands!