I know I've been fairly quiet on these lists lately. More on that
later. For now, I've done a bit of triage on the SF bug reports, and
I hope to have some free time over the Thanksgiving holiday weekend,
so my priority will be to nail as many bugs as possible, and get
another beta out asap. It's likely that unless I screw up royally,
that that will be the last beta. We need a period of time where the
translators can do their final updates before the final release, and
time's running short.
Here's my self-imposed schedule:
rc2: 16-Dec-2002 (if necessary)
This gives me some Xmas slip time if there are critical last minute
bugs. My intention is for translators to get their last updates in
between rc1 and final (but don't wait if you have stuff ready!). I'll
be very reluctant to change any templates or marked strings between
rc1 and final.
Cheers, and happy holidays,
From: "Barry A. Warsaw" <barry(a)python.org>
> It will be before the end of the year, or I'm selling my computers to
> become a sea monkey tycoon.
> I think we still have some i18n issues to iron out (big surprise, eh?
Maybe a good idea to freeze some period CVS changes. In that time all
translators can review his/her trasnlations and submit them.
(give the translators a deadline for submitting).
And after that, you may release 2.1 :)
btw just upgraded from b4+ to b5+, no problems (anymore).
still a make install error on a fresh clean RH8 system. (see my message at
My name is Jaime and I would like to know, if someone is working in the translation of the Mailman archives to spanish or is working in the same way,
please contact me....
$ecrets 2 $uccess Inc.
Check out the information that will unlock your doors to success and money. IT'S FREE!!
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now
It appears that pipermail does not work will with the message catalogs.
Please have a look at
This HTML page is formatted as KOI-8R, but that encoding is nowhere
declared. More disturbingly,
has the body of the message encoded as UTF-8. However, the rest of the
page is still encoded as KOI8-R.
It appears that we need either to recode the message in the encoding
of the HTML header/footer, or recode the HTML header/footer to the
encoding of body of the message (using character references where
Which one would you prefer?
İ have been excitedly , following your code updates, regarding the international charset improvements.
can we expect, considerable improvement in the beta 5 version,regarding charset in archiving and message header,footer output in non digest sends ?
I have to let you know that I can no longer head up the French
translation effort because:
1- My girlfriend is pregnant and the baby will be here real soon.
2- I left my last job and my actual Internet connection isn't famous
(56K analog with an HCF modem), my `cvs -q up -P -d's are now endless.
I had a wonderful time working with this amazing software, it's for me
the best Mailing List software and a nice `Python Cookbook', I'll be
I posted on traduc(a)traduc.org (fr language team) and
mailman-fr(a)rezo.net to find a taker, I'll let you know as soon as I
find another champion.
Am Sonntag, 17 November 2002 schrieb barry(a)python.org (Barry A. Warsaw)
>Yes it would. Question, should we copy all the outer message headers
>to the inner message, or just some subset? And if a subset, which
It think finding the minimum subset would be best: all MIME headers
must be present (Content-Type, Content-transfer-encoding, perhaps
Content-disposition, but not MIME-Version). All other headers belong
to the outer chrome, AFAICT.
EASY and FREE access to your email anywhere: http://Mailreader.com/
I made a patch
which recodes the pipermail HTML templates and gettext messages if the charset
of the page-under-creation is different from the charset of the templates. It uses
HTML character references if the template characters are not supported in the
target character set, so it should work fine if the template charset and the
target charset are both known to Python. If the template charset and the target
charset match, no conversion happens. If the message has no decared charset, but
the templates use a non-ASCII charset, a META tag is now inserted into the page.