From madsen@iki.fi Fri Mar 1 11:47:29 2002 From: madsen@iki.fi (Madsen Wikholm) Date: Fri, 1 Mar 2002 13:47:29 +0200 Subject: [Mailman-i18n] Mailman in swedish Message-ID: <20020301114729.GC4216@ummagumma> Hi! I was looking through the archives and found some references to translations to swedish being in progress. I'd like to give a hand, so if you who are in charge of the swedish translation could perhaps send me a mail i'd appreciate it. (I tried to send mail to jajoa@wmdata.com but it bounced). regrads, madsen wikholm From barry@zope.com Thu Mar 7 23:17:39 2002 From: barry@zope.com (Barry A. Warsaw) Date: Thu, 7 Mar 2002 18:17:39 -0500 Subject: [Mailman-i18n] forwarded message from Hye-Shik Chang Message-ID: <15495.62739.799026.983300@anthem.wooz.org> --V5YPYL6fTy Content-Type: text/plain; charset=us-ascii Content-Description: message body text Content-Transfer-Encoding: 7bit Do we have anybody who could do a Korean translation for Mailman? -Barry --V5YPYL6fTy Content-Type: message/rfc822 Content-Description: forwarded message Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Return-Path: Delivered-To: barry@mail.wooz.org Received: from digicool.com (unknown [63.100.190.15]) by mail.wooz.org (Postfix) with ESMTP id 6C350D35F2 for ; Thu, 7 Mar 2002 18:01:14 -0500 (EST) Received: from by digicool.com (CommuniGate Pro RULES 3.4) with RULES id 3683883; Thu, 07 Mar 2002 18:01:16 -0500 Received: from smtp.zope.com ([63.100.190.95] verified) by digicool.com (CommuniGate Pro SMTP 3.4) with ESMTP id 3683878; Thu, 07 Mar 2002 18:01:16 -0500 Received: from mail.python.org (mail.python.org [63.102.49.29]) by smtp.zope.com (8.11.6/8.11.2) with ESMTP id g27N0vf03126; Thu, 7 Mar 2002 18:00:57 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=mail.python.org) by mail.python.org with esmtp (Exim 3.35 #2) id 16j6rt-0004Gi-00; Thu, 07 Mar 2002 18:00:13 -0500 Received: from [211.216.53.129] (helo=kornet.hanirc.org ident=root) by mail.python.org with esmtp (Exim 3.35 #2) id 16j6rP-0004FC-00 for i18n-sig@python.org; Thu, 07 Mar 2002 17:59:43 -0500 Received: (from perky@localhost) by kornet.hanirc.org (8.11.6/8.11.5) id g27Mxb130392 for i18n-sig@python.org; Fri, 8 Mar 2002 07:59:37 +0900 (KST) (envelope-from perky) Message-ID: <20020308075937.A24873@fallin.lv> User-Agent: Mutt/1.2.5.1i Organization: Yonsei University Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Python internationalization and localization List-Unsubscribe: , List-Archive: From: Hye-Shik Chang Sender: i18n-sig-admin@python.org To: i18n-sig@python.org Subject: [I18n-sig] KoreanCodecs 2.0 released Date: Fri, 8 Mar 2002 07:59:37 +0900 X-Autogenerated: Mirror X-Mirrored-by: X-BeenThere: i18n-sig@python.org X-Mailman-Version: 2.0.8 (101270) X-MailScanner: Found to be clean Hello! I've released KoreanCodecs 2.0. It is reimplemented based on JapaneseCodecs 1.4. Supported Charsets: euc-kr (aliases: ksc5601, ksx1001) cp949 (aliases: uhc, ms949) iso-2022-kr johab unijohab qwerty2bul (aliases: 2bul) Additional Utility: korean.hangul : Korean character analyzer Some of those charsets doesn't have StreamWriter/Reader yet. And, it has only pure python implementation now. (Sorry (: I'll add C impl. soon.) http://sourceforge.net/projects/koco If you use FreeBSD, just do # cd /usr/ports/korean/pycodec # make install clean Ciao. -- Hye-Shik Chang Yonsei University, Seoul _______________________________________________ I18n-sig mailing list I18n-sig@python.org http://mail.python.org/mailman/listinfo/i18n-sig --V5YPYL6fTy-- From barry@zope.com Mon Mar 11 04:13:09 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sun, 10 Mar 2002 23:13:09 -0500 Subject: [Mailman-i18n] Re: [Mailman-Developers] big list References: <20020308162458.GE27629@rezo.net> <15497.26292.681882.2706@anthem.wooz.org> <20020309124033.GA31620@rezo.net> <20020309144735.GB12353@rezo.net> <15498.19452.486537.764090@anthem.wooz.org> <20020310002227.GA9790@rezo.net> <15499.58233.558446.909705@anthem.wooz.org> <15500.3352.980046.610866@localhost.localdomain> Message-ID: <15500.11989.862353.431289@anthem.wooz.org> >>>>> "OW" == Ousmane Wilane writes: OW> Thanks! I'm trying to do my best but as noted by Fil in one OW> of his messages, French is not my mother tongue, so there are OW> many imperfections laying around and I'm eager to get more OW> involvement for proofreading and alike. We may eventually want to think about joining the Translation Project: http://www.iro.umontreal.ca/contrib/po/HTML/ I don't want to think about a change like this for MM2.1, but afterwards I'm open for it, if the i18n crowd prefers. -Barry From mss@mawhrin.net Tue Mar 12 15:01:52 2002 From: mss@mawhrin.net (Mikhail Sobolev) Date: Tue, 12 Mar 2002 15:01:52 +0000 Subject: [Mailman-i18n] Re: [Mailman-Developers] Russian translation In-Reply-To: <20020312094821.GD2183@mhz.mikhail.zabaluev.name> References: <200202252018.g1PKI1Y13227@babylon5.cc.vt.edu> <5.1.0.14.2.20020225172719.04b901c0@lennier.cc.vt.edu> <5.1.0.14.2.20020226150822.04120b80@lennier.cc.vt.edu> <87it8j4ini.fsf@nausicaa.interq.or.jp> <20020312094821.GD2183@mhz.mikhail.zabaluev.name> Message-ID: <20020312150152.GA2396@mawhrin.net> I believe, mailman-i18n is a better forum for this question. :)) I'd say it's me who try to translate the mailman messages to Russian with help of others... I created a list mailman-ru@only.mawhrin.net, it's pretty quiet at the moment, but it's there for discussing the translation... -- Misha I seem to i the translation effor On Tue, Mar 12, 2002 at 12:48:21PM +0300, Mikhail Zabaluev wrote: > Hello Ben, > > On Wed, Feb 27, 2002 at 02:07:29PM +0900, Ben Gertzfield wrote: > > > > >>>>> "Ron" == Ron Jarrell writes: > > > > Ron> Took me a while to realize it was happening, because, > > Ron> screwing around, I selected Russian as my language of choice. > > Ron> Which, BTW, displayed everything in English. Does that mean > > Ron> I'm missing something in the install? When I switched to > > Ron> English for real, I got the *old* web pages... And > > Ron> immediately realized what was going on... > > > > You'll notice that some of the messages, not many, are actually > > in Russian. (Like the language pull-down box). > > > > That means that the Russian translation has been started, but is > > missing a lot of translated strings, so Mailman uses the English > > defaults for those. > > Who does the translation? Depending on the message pack size, I could > help and/or channel the work to folks over our Russian distro (ALT) > posse. > > -- > Stay tuned, > MhZ JID: mookid@jabber.org > ___________ > I live the way I type; fast, with a lot of mistakes. From barry@zope.com Tue Mar 12 19:33:36 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 12 Mar 2002 14:33:36 -0500 Subject: [Mailman-i18n] Re: [Mailman-Developers] Russian translation References: <200202252018.g1PKI1Y13227@babylon5.cc.vt.edu> <5.1.0.14.2.20020225172719.04b901c0@lennier.cc.vt.edu> <5.1.0.14.2.20020226150822.04120b80@lennier.cc.vt.edu> <87it8j4ini.fsf@nausicaa.interq.or.jp> <20020312094821.GD2183@mhz.mikhail.zabaluev.name> <20020312150152.GA2396@mawhrin.net> Message-ID: <15502.22544.26401.709272@anthem.wooz.org> >>>>> "MS" == Mikhail Sobolev writes: MS> I believe, mailman-i18n is a better forum for this MS> question. :)) MS> I'd say it's me who try to translate the mailman messages to MS> Russian with help of others... MS> I created a list mailman-ru@only.mawhrin.net, it's pretty MS> quiet at the moment, but it's there for discussing the MS> translation... I've added this mailing list to the i18n page. -Barry From mss@mawhrin.net Tue Mar 12 20:20:34 2002 From: mss@mawhrin.net (Mikhail Sobolev) Date: Tue, 12 Mar 2002 20:20:34 +0000 Subject: [Mailman-i18n] Re: [Mailman-Developers] Russian translation In-Reply-To: <15502.22544.26401.709272@anthem.wooz.org> References: <200202252018.g1PKI1Y13227@babylon5.cc.vt.edu> <5.1.0.14.2.20020225172719.04b901c0@lennier.cc.vt.edu> <5.1.0.14.2.20020226150822.04120b80@lennier.cc.vt.edu> <87it8j4ini.fsf@nausicaa.interq.or.jp> <20020312094821.GD2183@mhz.mikhail.zabaluev.name> <20020312150152.GA2396@mawhrin.net> <15502.22544.26401.709272@anthem.wooz.org> Message-ID: <20020312202034.GA3508@mawhrin.net> Barry, Please change also my e-mail address (from mikhail.sobolev@transas.com to mss@mawhrin.net). :) Thanks, -- Misha On Tue, Mar 12, 2002 at 02:33:36PM -0500, Barry A. Warsaw wrote: > MS> I created a list mailman-ru@only.mawhrin.net, it's pretty > MS> quiet at the moment, but it's there for discussing the > MS> translation... > > I've added this mailing list to the i18n page. > -Barry From mss@mawhrin.net Wed Mar 13 12:58:48 2002 From: mss@mawhrin.net (Mikhail Sobolev) Date: Wed, 13 Mar 2002 12:58:48 +0000 Subject: [Mailman-i18n] Finnish language Message-ID: <20020313125847.GA6639@mawhrin.net> I remember seeing a number of files being added for the Finnish language. While I cannot find it in Mailman/Defaults.py.in, is there any particluar reason for that? Thanks, -- Misha From barry@zope.com Wed Mar 13 14:21:16 2002 From: barry@zope.com (Barry A. Warsaw) Date: Wed, 13 Mar 2002 09:21:16 -0500 Subject: [Mailman-i18n] Finnish language References: <20020313125847.GA6639@mawhrin.net> Message-ID: <15503.24668.451831.334388@anthem.wooz.org> >>>>> "MS" == Mikhail Sobolev writes: MS> I remember seeing a number of files being added for the MS> Finnish language. While I cannot find it in MS> Mailman/Defaults.py.in, is there any particluar reason for MS> that? cvs glitches? Defaults.py.in 2.75 has this line: add_language('fi', _('Finnish'), 'iso-8859-1') -Barry From mss@mawhrin.net Wed Mar 13 14:25:57 2002 From: mss@mawhrin.net (Mikhail Sobolev) Date: Wed, 13 Mar 2002 14:25:57 +0000 Subject: [Mailman-i18n] Finnish language In-Reply-To: <15503.24668.451831.334388@anthem.wooz.org> References: <20020313125847.GA6639@mawhrin.net> <15503.24668.451831.334388@anthem.wooz.org> Message-ID: <20020313142557.GA6929@mawhrin.net> On Wed, Mar 13, 2002 at 09:21:16AM -0500, Barry A. Warsaw wrote: > MS> I remember seeing a number of files being added for the > MS> Finnish language. While I cannot find it in > MS> Mailman/Defaults.py.in, is there any particluar reason for > MS> that? > > cvs glitches? Hmm... I wonder why it did not update... Now it's OK. Thanks, -- Misha From barry@zope.com Wed Mar 13 14:25:33 2002 From: barry@zope.com (Barry A. Warsaw) Date: Wed, 13 Mar 2002 09:25:33 -0500 Subject: [Mailman-i18n] forwarded message from Bruno Haible Message-ID: <15503.24925.821668.325297@anthem.wooz.org> --zFf7J9QIZj Content-Type: text/plain; charset=us-ascii Content-Description: message body text Content-Transfer-Encoding: 7bit I haven't had time to look at this, and probably won't for several days. I like that Mailman's current tool chain works on my fairly stock, ancient RH6.1-ish system, but it also is fairly unweildy . If the new version of gettext will make /your/ lives easier, I'm happy to upgrade the Makefiles and such to rely on it. Comments are welcome. -Barry --zFf7J9QIZj Content-Type: message/rfc822 Content-Description: forwarded message Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-Path: Delivered-To: barry@mail.wooz.org Received: from digicool.com (unknown [63.100.190.15]) by mail.wooz.org (Postfix) with ESMTP id A9F8AD35F2 for ; Wed, 13 Mar 2002 08:56:36 -0500 (EST) Received: from by digicool.com (CommuniGate Pro RULES 3.4) with RULES id 3726694; Wed, 13 Mar 2002 08:56:37 -0500 Received: from smtp.zope.com ([63.100.190.95] verified) by digicool.com (CommuniGate Pro SMTP 3.4) with ESMTP id 3726691; Wed, 13 Mar 2002 08:56:35 -0500 Received: from mail.python.org (mail.python.org [63.102.49.29]) by smtp.zope.com (8.11.6/8.11.2) with ESMTP id g2DDuJf31924; Wed, 13 Mar 2002 08:56:19 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=mail.python.org) by mail.python.org with esmtp (Exim 3.35 #2) id 16l9Db-00077t-00; Wed, 13 Mar 2002 08:55:03 -0500 Received: from [193.55.64.10] (helo=sceaux.ilog.fr) by mail.python.org with esmtp (Exim 3.35 #2) id 16l9DX-00070i-00 for i18n-sig@python.org; Wed, 13 Mar 2002 08:55:00 -0500 Received: from ftp.ilog.fr (ftp.ilog.fr [193.55.64.11]) by sceaux.ilog.fr (8.11.6/8.11.6) with SMTP id g2DDq7B20015 for ; Wed, 13 Mar 2002 14:52:13 +0100 (MET) Received: from laposte.ilog.fr ([193.55.64.65]) by ftp.ilog.fr (NAVGW 2.5.1.16) with SMTP id M2002031314541010101 for ; Wed, 13 Mar 2002 14:54:10 +0100 Received: from honolulu.ilog.fr ([172.17.4.97]) by laposte.ilog.fr (8.11.6/8.11.5) with ESMTP id g2DDs9l20024; Wed, 13 Mar 2002 14:54:09 +0100 (MET) Received: (from haible@localhost) by honolulu.ilog.fr (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id OAA22889; Wed, 13 Mar 2002 14:54:51 +0100 Message-ID: <15503.23082.866066.584630@honolulu.ilog.fr> Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Python internationalization and localization List-Unsubscribe: , List-Archive: From: Bruno Haible Sender: i18n-sig-admin@python.org To: i18n-sig@python.org Subject: [I18n-sig] gettext-0.11.1 is released Date: Wed, 13 Mar 2002 14:54:50 +0100 (CET) X-Autogenerated: Mirror X-Mirrored-by: X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid X-BeenThere: i18n-sig@python.org X-Mailman-Version: 2.0.8 (101270) X-MailScanner: Found to be clean It is at ftp.gnu.org (soon also its mirrors) in gnu/gettext/gettext-0.11.1.tar.gz New in 0.11.1: * xgettext now also supports Python, Tcl, Awk and Glade. * msgfmt can create (and msgunfmt can dump) Tcl message catalogs. * msggrep has a new option -C that allows to search for strings in translator comments. * Bug fixes in the gettext.m4 autoconf macros. New in 0.11: * New programs: msgattrib - attribute matching and manipulation on message catalog, msgcat - combines several message catalogs, msgconv - character set conversion for message catalog, msgen - create English message catalog, msgexec - process translations of message catalog, msgfilter - edit translations of message catalog, msggrep - pattern matching on message catalog, msginit - initialize a message catalog, msguniq - unify duplicate translations in message catalog. * msgfmt can create (and msgunfmt can dump) Java ResourceBundles. * xgettext now also supports Lisp, Emacs Lisp, librep, Java, ObjectPascal, YCP. * The tools now know about format strings in languages other than C. They recognize new message flags named lisp-format, elisp-format, librep-format, smalltalk-format, java-format, python-format, ycp-format. When such a flag is present, the msgfmt program verifies the consistency of the translated and the untranslated format string. * The msgfmt command line options have changed. Option -c now also checks the header entry, a check which was previously activated through -v. Option -C corresponds to the compatibility checks previously activated through -v -v. Option -v now only increases verbosity and doesn't influence whether msgfmt succeeds or fails. A new option --check-accelerators is useful for GUI menu item translations. * msgcomm now writes its results to standard output by default. The options -d/--default-domain and -p/--output-dir have been removed. * Manual pages for all the programs have been added. * PO mode changes: - New key bindings for 'po-previous-fuzzy-entry', 'po-previous-obsolete-entry', 'po-previous-translated-entry', 'po-previous-untranslated', 'po-undo', 'po-other-window', and 'po-select-auxiliary'. - Support for merging two message catalogs, based on msgcat and ediff. * A fuzzy attribute of the header entry of a message catalog is now ignored by the tools, i.e. it is used even if marked fuzzy. * gettextize has a new option --intl which determines whether a copy of the intl directory is included in the package. * The Makefile variable @INTLLIBS@ is deprecated. It is replaced with @LIBINTL@ (in projects without libtool) or @LTLIBINTL@ (in projects with libtool). * New packaging hints for binary package distributors. See file PACKAGING. * New documentation sections: - Manipulating - po/LINGUAS - po/Makevars - lib/gettext.h - autoconf macros - Other Programming Languages Happy internationalization! Bonne francisation! Frohes Eindeutschen! Bruno _______________________________________________ I18n-sig mailing list I18n-sig@python.org http://mail.python.org/mailman/listinfo/i18n-sig --zFf7J9QIZj-- From mss@mawhrin.net Wed Mar 13 14:42:03 2002 From: mss@mawhrin.net (Mikhail Sobolev) Date: Wed, 13 Mar 2002 14:42:03 +0000 Subject: [Mailman-i18n] forwarded message from Bruno Haible In-Reply-To: <15503.24925.821668.325297@anthem.wooz.org> References: <15503.24925.821668.325297@anthem.wooz.org> Message-ID: <20020313144203.GA6973@mawhrin.net> The only thing that would make my life easier, is using -w 100 (or, at least, 90) while merging the catalogues. Some messages in the code hit the 79-80 limit, and as there should be '\n' after that, the line got splitted. It make the reading of the file a bit less comfortable. :)) Besides, it's fine. -- Misha On Wed, Mar 13, 2002 at 09:25:33AM -0500, Barry A. Warsaw wrote: Content-Description: message body text > > I haven't had time to look at this, and probably won't for several > days. I like that Mailman's current tool chain works on my fairly > stock, ancient RH6.1-ish system, but it also is fairly unweildy > . > > If the new version of gettext will make /your/ lives easier, I'm happy > to upgrade the Makefiles and such to rely on it. Comments are welcome. > > -Barry From che@debian.org Wed Mar 13 14:56:46 2002 From: che@debian.org (Ben Gertzfield) Date: Wed, 13 Mar 2002 23:56:46 +0900 Subject: [Mailman-i18n] Finnish language In-Reply-To: <20020313142557.GA6929@mawhrin.net> (mss@mawhrin.net's message of "Wed, 13 Mar 2002 14:25:57 +0000") References: <20020313125847.GA6639@mawhrin.net> <15503.24668.451831.334388@anthem.wooz.org> <20020313142557.GA6929@mawhrin.net> Message-ID: <87it80bjo1.fsf@nausicaa.interq.or.jp> >>>>> "Mikhail" == Mikhail Sobolev writes: MS> I remember seeing a number of files being added for the MS> Finnish language. While I cannot find it in MS> Mailman/Defaults.py.in, is there any particluar reason for MS> that? BAM> cvs glitches? MS> Hmm... I wonder why it did not update... Now it's OK. 'cvs update' will not create new directories (like those for new translations). Use 'cvs checkout' instead. Ben -- Brought to you by the letters L and Y and the number 4. "Tahiti is not in Europe." Debian GNU/Linux maintainer of Gimp and Nethack -- http://www.debian.org/ From alessio@albourne.com Wed Mar 13 14:59:38 2002 From: alessio@albourne.com (Alessio Bragadini) Date: 13 Mar 2002 16:59:38 +0200 Subject: [Mailman-i18n] Finnish language In-Reply-To: <87it80bjo1.fsf@nausicaa.interq.or.jp> References: <20020313125847.GA6639@mawhrin.net> <15503.24668.451831.334388@anthem.wooz.org> <20020313142557.GA6929@mawhrin.net> <87it80bjo1.fsf@nausicaa.interq.or.jp> Message-ID: <1016031578.29014.3348.camel@iris> On Wed, 2002-03-13 at 16:56, Ben Gertzfield wrote: > 'cvs update' will not create new directories Unless you use cvs update -d, ofcourse. -- Alessio F. Bragadini alessio@albourne.com APL Financial Services http://village.albourne.com Nicosia, Cyprus phone: +357-22-755750 "It is more complicated than you think" -- The Eighth Networking Truth from RFC 1925 From loewis@informatik.hu-berlin.de Wed Mar 13 15:00:47 2002 From: loewis@informatik.hu-berlin.de (Martin von Loewis) Date: 13 Mar 2002 16:00:47 +0100 Subject: [Mailman-i18n] forwarded message from Bruno Haible In-Reply-To: <15503.24925.821668.325297@anthem.wooz.org> References: <15503.24925.821668.325297@anthem.wooz.org> Message-ID: barry@zope.com (Barry A. Warsaw) writes: > I haven't had time to look at this, and probably won't for several > days. I like that Mailman's current tool chain works on my fairly > stock, ancient RH6.1-ish system, but it also is fairly unweildy > . > > If the new version of gettext will make /your/ lives easier, I'm happy > to upgrade the Makefiles and such to rely on it. Comments are welcome. I think the only need to change the tools may occur with the Chinese catalogs, as there are some compatibility issues with escape characters - newer tools may reject older catalogs. I don't know whether this is an issue for the current mailman CVS. Also, the newer msgfmt catches a few additional errors. Apart from that, I don't think there is any need to update gettext. Regards, Martin From mss@mawhrin.net Wed Mar 13 15:24:26 2002 From: mss@mawhrin.net (Mikhail Sobolev) Date: Wed, 13 Mar 2002 15:24:26 +0000 Subject: [Mailman-i18n] Finnish language In-Reply-To: <87it80bjo1.fsf@nausicaa.interq.or.jp> References: <20020313125847.GA6639@mawhrin.net> <15503.24668.451831.334388@anthem.wooz.org> <20020313142557.GA6929@mawhrin.net> <87it80bjo1.fsf@nausicaa.interq.or.jp> Message-ID: <20020313152426.GA7148@mawhrin.net> On Wed, Mar 13, 2002 at 11:56:46PM +0900, Ben Gertzfield wrote: > MS> Hmm... I wonder why it did not update... Now it's OK. > > 'cvs update' will not create new directories (like those for new > translations). Use 'cvs checkout' instead. I usually use '-q update -dP'... Musta forgotten to update or something. Anyway, now it's OK. :) -- Misha From barry@zope.com Wed Mar 13 16:51:21 2002 From: barry@zope.com (Barry A. Warsaw) Date: Wed, 13 Mar 2002 11:51:21 -0500 Subject: [Mailman-i18n] Finnish language References: <20020313125847.GA6639@mawhrin.net> <15503.24668.451831.334388@anthem.wooz.org> <20020313142557.GA6929@mawhrin.net> <87it80bjo1.fsf@nausicaa.interq.or.jp> Message-ID: <15503.33673.415382.542317@anthem.wooz.org> >>>>> "BG" == Ben Gertzfield writes: BG> 'cvs update' will not create new directories (like those for BG> new translations). Use 'cvs checkout' instead. Oops, hadn't thought about that. Actually it's better to use "cvs up -P -d" to prune out empty (obsolete) directories, and check out new directories. I've long buried this revelation in an alias: % alias sup alias sup='cvs -q up -P -d' :) as-in-'wassup?'-ly y'rs, -Barry From barry@zope.com Wed Mar 13 16:52:54 2002 From: barry@zope.com (Barry A. Warsaw) Date: Wed, 13 Mar 2002 11:52:54 -0500 Subject: [Mailman-i18n] forwarded message from Bruno Haible References: <15503.24925.821668.325297@anthem.wooz.org> Message-ID: <15503.33766.174864.577321@anthem.wooz.org> >>>>> "MvL" == Martin von Loewis writes: MvL> I think the only need to change the tools may occur with the MvL> Chinese catalogs, as there are some compatibility issues with MvL> escape characters - newer tools may reject older catalogs. I MvL> don't know whether this is an issue for the current mailman MvL> CVS. It is. I believe I've disabled building the Chinese catalog by default because it simply fails. MvL> Also, the newer msgfmt catches a few additional errors. MvL> Apart from that, I don't think there is any need to update MvL> gettext. I also think the way I merge the .pot file into the .po files is fairly kludgey. So that might make it worthwhile. -Barry From barry@zope.com Thu Mar 14 23:25:03 2002 From: barry@zope.com (Barry A. Warsaw) Date: Thu, 14 Mar 2002 18:25:03 -0500 Subject: [Mailman-i18n] Re: [Mailman-Developers] Bug in Chinese language selections and options page? References: <200203140323.g2E3NoWk029732@utopia.West.Sun.COM> Message-ID: <15505.12623.171701.557645@anthem.wooz.org> >>>>> "DM" == Dan Mick writes: DM> OK, I've got no idea how to browse Chinese; I'm using a DM> Netscape and OS that have no support for the font. That might DM> be the problem. DM> However: if I use my personal subscription options page: DM> http://host.dom.ain/mailman/options/listname/subscribe-addr DM> to change language to "Traditional Chinese" or "Simplified DM> Chinese", I get an expectedly-garbled page, but unfortunately DM> it appears with no "Submit My Changes" button, so if I were DM> unaware that I could use my browser's Back button, I just did DM> something I can't recover from. DM> Is that because my browser is just not capable? Even if so, DM> does this seem bad? I'm using Mozilla and when I do this, I definitely see what look to me like Chinese characters. You're right that the submit button isn't there, but that's because the Chinese templates are woefully out of date. We'll have to make a determination nearer to final release time about which languages are suitable for release and which aren't. -Barry From mss@mawhrin.net Thu Mar 14 23:53:57 2002 From: mss@mawhrin.net (Mikhail Sobolev) Date: Thu, 14 Mar 2002 23:53:57 +0000 Subject: [Mailman-i18n] A small addition to messages/Makefile.in Message-ID: <20020314235357.GA15337@mawhrin.net> Time to time, it's a good idea just to check how good the templates are. Here is a small patch that adds a target "check" for finding out the obvious errors. -- Misha Index: Makefile.in =================================================================== RCS file: /cvsroot/mailman/mailman/messages/Makefile.in,v retrieving revision 2.19 diff -u -b -r2.19 Makefile.in --- Makefile.in 6 Mar 2002 05:05:51 -0000 2.19 +++ Makefile.in 14 Mar 2002 23:51:08 -0000 @@ -74,6 +74,9 @@ catalogs: $(TARGETS) +check: + @for file in $(POFILES); do echo "Checking $$file"; msgfmt -o /dev/null --statistics -v $$file; done + install: doinstall # we should depend on the .mo files instead of making them! From max.yu@turbolinux.com.cn Fri Mar 15 02:14:37 2002 From: max.yu@turbolinux.com.cn (Max Yu) Date: Fri, 15 Mar 2002 10:14:37 +0800 Subject: [Mailman-i18n] Re: [Mailman-Developers] Bug in Chinese language selections and options page? References: <200203140323.g2E3NoWk029732@utopia.West.Sun.COM> <15505.12623.171701.557645@anthem.wooz.org> Message-ID: <3C91590D.3D756E47@turbolinux.com.cn> I am native Chinese speaker, and I have installed mailman-2.0.8 English version successfully on my computer, and I want to help building Chinese templates, what should I do then? Thanks for your attention. Best Regards Max Yu "Barry A. Warsaw" =D0=B4=B5=C0=A3=BA > >>>>> "DM" =3D=3D Dan Mick writes: > > DM> OK, I've got no idea how to browse Chinese; I'm using a > DM> Netscape and OS that have no support for the font. That might > DM> be the problem. > > DM> However: if I use my personal subscription options page: > > DM> http://host.dom.ain/mailman/options/listname/subscribe-addr > > DM> to change language to "Traditional Chinese" or "Simplified > DM> Chinese", I get an expectedly-garbled page, but unfortunately > DM> it appears with no "Submit My Changes" button, so if I were > DM> unaware that I could use my browser's Back button, I just did > DM> something I can't recover from. > > DM> Is that because my browser is just not capable? Even if so, > DM> does this seem bad? > > I'm using Mozilla and when I do this, I definitely see what look to me > like Chinese characters. You're right that the submit button isn't > there, but that's because the Chinese templates are woefully out of > date. > > We'll have to make a determination nearer to final release time about > which languages are suitable for release and which aren't. > > -Barry > > _______________________________________________ > Mailman-i18n mailing list > Mailman-i18n@python.org > http://mail.python.org/mailman/listinfo/mailman-i18n From barry@zope.com Mon Mar 25 06:47:19 2002 From: barry@zope.com (Barry A. Warsaw) Date: Mon, 25 Mar 2002 01:47:19 -0500 Subject: [Mailman-i18n] Re: [Mailman-Developers] Bug in Chinese language selections and options page? References: <200203140323.g2E3NoWk029732@utopia.West.Sun.COM> <15505.12623.171701.557645@anthem.wooz.org> <3C91590D.3D756E47@turbolinux.com.cn> Message-ID: <15518.51191.652450.567338@anthem.wooz.org> MY> I am native Chinese speaker, and I have installed MY> mailman-2.0.8 English version successfully on my computer, and MY> I want to help building Chinese templates, what should I do MY> then? Max, it would be really greate to get some updates to the Chinese templates and message catalogs. Please grab Mailman 2.1b1, and read the README-I18N.en file for instructions. Or grab them from the latest langpack file release on SF. When you're ready, you can send me updates to messages.po and the templates directory. Preferred mode of delivery is a tar file that I can un pack at the top of the source tree (i.e. in the parent directory of messages/ and templates/). Thanks, -Barry From tkikuchi@is.kochi-u.ac.jp Tue Mar 26 08:05:33 2002 From: tkikuchi@is.kochi-u.ac.jp (Tokio Kikuchi) Date: Tue, 26 Mar 2002 17:05:33 +0900 Subject: [Mailman-i18n] japanese Message-ID: <3CA02BCD.3050004@is.kochi-u.ac.jp> Hi! Barry and all, I think I've catched up my Japanese translation with 2.1beta. Please find the latest messagages and templates at http://mm.tkikuchi.net/mailman-2.1alpha.ja/mailman.i18n.ja.tar.gz (the URL is still alpha ;-< ) -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From barry@zope.com Tue Mar 26 23:06:27 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 26 Mar 2002 18:06:27 -0500 Subject: [Mailman-i18n] japanese References: <3CA02BCD.3050004@is.kochi-u.ac.jp> Message-ID: <15520.65267.438404.511682@anthem.wooz.org> >>>>> "TK" == Tokio Kikuchi writes: TK> Hi! Barry and all, TK> I think I've catched up my Japanese translation with 2.1beta. TK> Please find the latest messagages and templates at TK> http://mm.tkikuchi.net/mailman-2.1alpha.ja/mailman.i18n.ja.tar.gz Thanks! I've installed them in cvs. -Barry From andsoon@igrus.inha.ac.kr Thu Mar 28 13:01:33 2002 From: andsoon@igrus.inha.ac.kr (andsoon@igrus.inha.ac.kr) Date: Thu, 28 Mar 2002 22:01:33 +0900 (KST) Subject: [Mailman-i18n] korean translation Message-ID: hi all. I finished to translate the mailman 2.1beta in korean but not completely. find at http://igrus.inha.ac.kr/~andsoon/pds/mailman-2.1beta.ko/mailman.i18n.ko.tar.gz From che@debian.org Thu Mar 28 14:12:42 2002 From: che@debian.org (Ben Gertzfield) Date: Thu, 28 Mar 2002 23:12:42 +0900 Subject: [Mailman-i18n] korean translation In-Reply-To: ('s message of "Thu, 28 Mar 2002 22:01:33 +0900 (KST)") References: Message-ID: <877knwu6g5.fsf@nausicaa.interq.or.jp> >>>>> "andsoon" == andsoon writes: andsoon> hi all. I finished to translate the mailman 2.1beta in andsoon> korean but not completely. Thank you very much! I've been wondering, which charset and encoding do you think we should use in Mailman for Korean in email? euc-kr with base64? I know euc-kr is probably best for web pages, but I get a lot of Korean spam in some Windows character set, so I don't know which people use for email in real life. Ben -- Brought to you by the letters N and O and the number 7. "What's different, Pete, about the 69 that makes it so exciting to you?" Debian GNU/Linux maintainer of Gimp and Nethack -- http://www.debian.org/ From barry@zope.com Thu Mar 28 19:08:14 2002 From: barry@zope.com (Barry A. Warsaw) Date: Thu, 28 Mar 2002 14:08:14 -0500 Subject: [Mailman-i18n] korean translation References: <877knwu6g5.fsf@nausicaa.interq.or.jp> Message-ID: <15523.27166.335858.813858@anthem.wooz.org> >>>>> "BG" == Ben Gertzfield writes: >>>>> "andsoon" == andsoon writes: andsoon> hi all. I finished to translate the mailman 2.1beta in andsoon> korean but not completely. BG> Thank you very much! Yes, indeed! I've integrated your changes into CVS. BG> I've been wondering, which charset and encoding do you think BG> we should use in Mailman for Korean in email? euc-kr with BG> base64? Good question. We'll need to add that to the email package's Charset mapping. I'm assuming the Mailman add_language() directive should use euc-kr. BG> I know euc-kr is probably best for web pages, but I get a lot BG> of Korean spam in some Windows character set, so I don't know BG> which people use for email in real life. Another question for andsoon: what do you think of the Korean codecs in the python-codecs project: http://sf.net/projects/python-codecs Is it in a usable state? I'm happy to add this to Mailman if they are stable enough. -Barry From barry@zope.com Thu Mar 28 19:10:18 2002 From: barry@zope.com (Barry A. Warsaw) Date: Thu, 28 Mar 2002 14:10:18 -0500 Subject: [Mailman-i18n] korean translation References: Message-ID: <15523.27290.73704.300848@anthem.wooz.org> Another qeustion. I have as Korean champion song@yaimma.co.kr, but haven't heard much from them in a long time. Are you two working together? Are you aware of each other's progress? If song can't head up the Korean translation now, will you andsoon? -Barry From che@debian.org Fri Mar 29 01:47:46 2002 From: che@debian.org (Ben Gertzfield) Date: Fri, 29 Mar 2002 10:47:46 +0900 Subject: [Mailman-i18n] korean translation In-Reply-To: <15523.27166.335858.813858@anthem.wooz.org> (barry@zope.com's message of "Thu, 28 Mar 2002 14:08:14 -0500") References: <877knwu6g5.fsf@nausicaa.interq.or.jp> <15523.27166.335858.813858@anthem.wooz.org> Message-ID: <87lmccnnzx.fsf@nausicaa.interq.or.jp> >>>>> "BAW" == Barry A Warsaw writes: >>>>> "BG" == Ben Gertzfield writes: >>>>> "andsoon" == andsoon writes: BG> I've been wondering, which charset and encoding do you think BG> we should use in Mailman for Korean in email? euc-kr with BG> base64? BAW> Good question. We'll need to add that to the email package's BAW> Charset mapping. I'm assuming the Mailman add_language() BAW> directive should use euc-kr. Actually, if there's no conversion performed like the EUC-JP -> ISO-2022-JP conversion for Japanese, you don't need to modify the Charset package. If you create a Charset("euc-kr"), you will get a Base64'd header and body, because the default for unknown charsets is to Base64 encode them: Python 2.1.2 (#1, Jan 18 2002, 18:05:45) [GCC 2.95.4 (Debian prerelease)] on linux2 Type "copyright", "credits" or "license" for more information. >>> from email.Charset import Charset >>> from email.Header import Header >>> from email.Message import Message >>> c = Charset("euc-kr") >>> h = Header("This is a Korean header", c) >>> print h =?euc-kr?b?VGhpcyBpcyBhIEtvcmVhbiBoZWFkZXI=?= >>> m = Message() >>> m.set_charset(c) >>> m.add_payload("This is a Korean body") >>> m["Subject"] = h >>> print m >From nobody Fri Mar 29 10:46:33 2002 MIME-Version: 1.0 Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: base64 Subject: =?euc-kr?b?VGhpcyBpcyBhIEtvcmVhbiBoZWFkZXI=?= VGhpcyBpcyBhIEtvcmVhbiBib2R5 BAW> Another question for andsoon: what do you think of the Korean BAW> codecs in the python-codecs project: BAW> http://sf.net/projects/python-codecs I honestly have no idea how to test the stability of the Korean Unicode codecs, because I don't know how to input Korean. :/ Comments from other folks would be very appreciated. Ben -- Brought to you by the letters I and S and the number 8. "It should be illegal to yell 'Y2K' in a crowded economy." Debian GNU/Linux maintainer of Gimp and Nethack -- http://www.debian.org/ From che@debian.org Fri Mar 29 02:58:25 2002 From: che@debian.org (Ben Gertzfield) Date: Fri, 29 Mar 2002 11:58:25 +0900 Subject: [Mailman-i18n] korean translation In-Reply-To: <87lmccnnzx.fsf@nausicaa.interq.or.jp> (Ben Gertzfield's message of "Fri, 29 Mar 2002 10:47:46 +0900") References: <877knwu6g5.fsf@nausicaa.interq.or.jp> <15523.27166.335858.813858@anthem.wooz.org> <87lmccnnzx.fsf@nausicaa.interq.or.jp> Message-ID: <87adssnkq6.fsf@nausicaa.interq.or.jp> >>>>> "Ben" == Ben Gertzfield writes: >>>>> "BAW" == Barry A Warsaw writes: BG> I've been wondering, which charset and encoding do you think BG> we should use in Mailman for Korean in email? euc-kr with BG> base64? BAW> Good question. We'll need to add that to the email package's BAW> Charset mapping. I'm assuming the Mailman add_language() BAW> directive should use euc-kr. Ben> Actually, if there's no conversion performed like the EUC-JP Ben> -> ISO-2022-JP conversion for Japanese, you don't need to Ben> modify the Charset package. Of course, I forgot that EUC-KR is a multibyte charset; it's possible (although I don't know how email clients behave) that clients will screw up if we split an EUC-KR string between two bytes of a character when wrapping a long header line. We may need that Korean Unicode module after all. Ben -- Brought to you by the letters E and U and the number 14. "A baloo is a bear." Debian GNU/Linux maintainer of Gimp and Nethack -- http://www.debian.org/ From andsoon@igrus.inha.ac.kr Fri Mar 29 06:54:11 2002 From: andsoon@igrus.inha.ac.kr (andsoon@igrus.inha.ac.kr) Date: Fri, 29 Mar 2002 15:54:11 +0900 (KST) Subject: [Mailman-i18n] korean translation In-Reply-To: <877knwu6g5.fsf@nausicaa.interq.or.jp> Message-ID: On Thu, 28 Mar 2002, Ben Gertzfield wrote: > I've been wondering, which charset and encoding do you think we should > use in Mailman for Korean in email? euc-kr with base64? I think charset and enconding for Korean fits with euc-kr because most peoples use euc-kr in their mail agents > I know euc-kr is probably best for web pages, but I get a lot of > Korean spam in some Windows character set, so I don't know which > people use for email in real life. > be recommended set euc-kr in korea. From andsoon@igrus.inha.ac.kr Fri Mar 29 07:20:00 2002 From: andsoon@igrus.inha.ac.kr (andsoon@igrus.inha.ac.kr) Date: Fri, 29 Mar 2002 16:20:00 +0900 (KST) Subject: [Mailman-i18n] korean translation In-Reply-To: <15523.27166.335858.813858@anthem.wooz.org> Message-ID: On Thu, 28 Mar 2002, Barry A. Warsaw wrote: > Another question for andsoon: what do you think of the Korean codecs > in the python-codecs project: > > http://sf.net/projects/python-codecs > > Is it in a usable state? I'm happy to add this to Mailman if they are > stable enough. sorry. i don't know details about python code. so don't know it's stable or unstable. From andsoon@igrus.inha.ac.kr Fri Mar 29 07:23:43 2002 From: andsoon@igrus.inha.ac.kr (andsoon@igrus.inha.ac.kr) Date: Fri, 29 Mar 2002 16:23:43 +0900 (KST) Subject: [Mailman-i18n] korean translation In-Reply-To: <15523.27290.73704.300848@anthem.wooz.org> Message-ID: On Thu, 28 Mar 2002, Barry A. Warsaw wrote: > > Another qeustion. I have as Korean champion song@yaimma.co.kr, but > haven't heard much from them in a long time. Are you two working > together? Are you aware of each other's progress? If song can't head > up the Korean translation now, will you andsoon? > i don't know song@yaimma.co.kr. may be each progress. From loewis@informatik.hu-berlin.de Fri Mar 29 09:05:14 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 29 Mar 2002 10:05:14 +0100 Subject: [Mailman-i18n] korean translation In-Reply-To: <87adssnkq6.fsf@nausicaa.interq.or.jp> References: <877knwu6g5.fsf@nausicaa.interq.or.jp> <15523.27166.335858.813858@anthem.wooz.org> <87lmccnnzx.fsf@nausicaa.interq.or.jp> <87adssnkq6.fsf@nausicaa.interq.or.jp> Message-ID: Ben Gertzfield writes: > Of course, I forgot that EUC-KR is a multibyte charset; it's possible > (although I don't know how email clients behave) that clients will > screw up if we split an EUC-KR string between two bytes of a character > when wrapping a long header line. > > We may need that Korean Unicode module after all. I think there are other reasons for that, as well. People may use multiple encodings when posting to a mailing list, so archiving needs to perform character set conversion (see patch 510415). Likewise, removal of duplicate list names needs charset conversion, see patch 498766. Is anybody actually looking at these patches? Regards, Martin From loewis@informatik.hu-berlin.de Fri Mar 29 09:07:33 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 29 Mar 2002 10:07:33 +0100 Subject: [Mailman-i18n] korean translation In-Reply-To: References: Message-ID: writes: > On Thu, 28 Mar 2002, Barry A. Warsaw wrote: > > > Another question for andsoon: what do you think of the Korean codecs > > in the python-codecs project: > > > > http://sf.net/projects/python-codecs > > > > Is it in a usable state? I'm happy to add this to Mailman if they are > > stable enough. The Korean codecs now live in a separate project, see http://mail.python.org/pipermail/i18n-sig/2002-March/001390.html Regards, Martin From che@debian.org Fri Mar 29 09:11:14 2002 From: che@debian.org (Ben Gertzfield) Date: Fri, 29 Mar 2002 18:11:14 +0900 Subject: [Mailman-i18n] korean translation In-Reply-To: (loewis@informatik.hu-berlin.de's message of "29 Mar 2002 10:05:14 +0100") References: <877knwu6g5.fsf@nausicaa.interq.or.jp> <15523.27166.335858.813858@anthem.wooz.org> <87lmccnnzx.fsf@nausicaa.interq.or.jp> <87adssnkq6.fsf@nausicaa.interq.or.jp> Message-ID: <874rizn3gt.fsf@nausicaa.interq.or.jp> >>>>> "Martin" =3D=3D Martin v L=F6wis wri= tes: Ben> Of course, I forgot that EUC-KR is a multibyte charset; it's Ben> possible (although I don't know how email clients behave) Ben> that clients will screw up if we split an EUC-KR string Ben> between two bytes of a character when wrapping a long header Ben> line. Martin> I think there are other reasons for that, as well. People Martin> may use multiple encodings when posting to a mailing list, Martin> so archiving needs to perform character set conversion Martin> (see patch 510415). Martin> Likewise, removal of duplicate list names needs charset Martin> conversion, see patch 498766. Martin> Is anybody actually looking at these patches? I think there are a million issues with Pipermail that need to be solved for Mailman 2.2 (3.0?). These are two of them. The whole system needs to be overhauled, and lots of issues with multiple charsets in a list archive need to be dealt with. Ben --=20 Brought to you by the letters N and X and the number 17. "What's different, Pete, about the 69 that makes it so exciting to you?" Debian GNU/Linux maintainer of Gimp and Nethack -- http://www.debian.org/ From loewis@informatik.hu-berlin.de Fri Mar 29 10:25:57 2002 From: loewis@informatik.hu-berlin.de (Martin von Loewis) Date: Fri, 29 Mar 2002 11:25:57 +0100 (CET) Subject: [Mailman-i18n] korean translation In-Reply-To: <874rizn3gt.fsf@nausicaa.interq.or.jp> from Ben Gertzfield at "Mar 29, 2002 06:11:14 pm" Message-ID: <200203291025.g2TAPvpU008720@paros.informatik.hu-berlin.de> > I think there are a million issues with Pipermail that need to be > solved for Mailman 2.2 (3.0?). These are two of them. > > The whole system needs to be overhauled, and lots of issues with > multiple charsets in a list archive need to be dealt with. So what would be wrong with just applying the patches that are currently available? You can either ignore contributions and hope that you can find time to do it yourself, or you can cooperate with contributors. If you chose to ignore contributions, please atleast take the time to reject the patches that you certainly won't consider. Regards, Martin From che@debian.org Fri Mar 29 10:35:08 2002 From: che@debian.org (Ben Gertzfield) Date: Fri, 29 Mar 2002 19:35:08 +0900 Subject: [Mailman-i18n] korean translation In-Reply-To: <200203291025.g2TAPvpU008720@paros.informatik.hu-berlin.de> (Martin von Loewis's message of "Fri, 29 Mar 2002 11:25:57 +0100 (CET)") References: <200203291025.g2TAPvpU008720@paros.informatik.hu-berlin.de> Message-ID: <87vgbfll0j.fsf@nausicaa.interq.or.jp> >>>>> "Martin" == Martin von Loewis writes: Ben> I think there are a million issues with Pipermail that need Ben> to be solved for Mailman 2.2 (3.0?). These are two of them. Ben> Ben> The whole system needs to be overhauled, and lots of issues Ben> with multiple charsets in a list archive need to be dealt Ben> with. Martin> So what would be wrong with just applying the patches that Martin> are currently available? You can either ignore Martin> contributions and hope that you can find time to do it Martin> yourself, or you can cooperate with contributors. If you Martin> chose to ignore contributions, please atleast take the Martin> time to reject the patches that you certainly won't Martin> consider. Er, I'm not sure if you understand, but I'm not the Mailman maintainer, nor do I have CVS access to Mailman. I'm just letting you know that the entire system needs a huge overhaul, and that if those patches did the overhaul, I'm sure Barry would have applied them already. Ben -- Brought to you by the letters V and E and the number 18. "Elate means having wings." Debian GNU/Linux maintainer of Gimp and Nethack -- http://www.debian.org/ From loewis@informatik.hu-berlin.de Fri Mar 29 15:08:17 2002 From: loewis@informatik.hu-berlin.de (Martin von Loewis) Date: Fri, 29 Mar 2002 16:08:17 +0100 (CET) Subject: [Mailman-i18n] korean translation In-Reply-To: <87vgbfll0j.fsf@nausicaa.interq.or.jp> from Ben Gertzfield at "Mar 29, 2002 07:35:08 pm" Message-ID: <200203291508.g2TF8HtM008902@paros.informatik.hu-berlin.de> > >>>>> "Martin" == Martin von Loewis writes: > > Er, I'm not sure if you understand, but I'm not the Mailman > maintainer, nor do I have CVS access to Mailman. I'm just letting you > know that the entire system needs a huge overhaul, and that if those > patches did the overhaul, I'm sure Barry would have applied them > already. Then please take my apologies: from your response, I assumed that you would indeed co-maintain mailman. My original question remains, though: Is anybody considering these patches (not just my own; I notice that the oldest patch which had no review is dated 2000-09-21)? Regards, Martin From barry@zope.com Fri Mar 29 15:21:45 2002 From: barry@zope.com (Barry A. Warsaw) Date: Fri, 29 Mar 2002 10:21:45 -0500 Subject: [Mailman-i18n] korean translation References: <877knwu6g5.fsf@nausicaa.interq.or.jp> <15523.27166.335858.813858@anthem.wooz.org> <87lmccnnzx.fsf@nausicaa.interq.or.jp> <87adssnkq6.fsf@nausicaa.interq.or.jp> Message-ID: <15524.34441.482093.809977@anthem.wooz.org> >>>>> "MvL" =3D=3D Martin v L=F6wis wr= ites: MvL> Is anybody actually looking at these patches? I will be (when I get back to MM hacking). -B From barry@zope.com Fri Mar 29 15:48:57 2002 From: barry@zope.com (Barry A. Warsaw) Date: Fri, 29 Mar 2002 10:48:57 -0500 Subject: [Mailman-i18n] korean translation References: <87vgbfll0j.fsf@nausicaa.interq.or.jp> <200203291508.g2TF8HtM008902@paros.informatik.hu-berlin.de> Message-ID: <15524.36073.411853.571625@anthem.wooz.org> >>>>> "MvL" == Martin von Loewis writes: MvL> Then please take my apologies: from your response, I assumed MvL> that you would indeed co-maintain mailman. My original MvL> question remains, though: MvL> Is anybody considering these patches (not just my own; I MvL> notice that the oldest patch which had no review is dated MvL> 2000-09-21)? At present, I'm really the only one actually committing changes to cvs, although several people (Ben, Dan and Daniel, Ron, etc.) do provide very excellent patches. You too Martin. But this means I'm the bottleneck for getting fixes in, and that's subject to the vagaries of my "real" job. ;) One way to help out right now: I can add you as a tracker admin and you can help do triage on the bugs and patches. This actually would be an enormous help, because there's a lot of things to go through. Even weeding out those issues that are no longer relevant for MM2.1, and assigning everything that's left to me would help a lot. I'd also love it if someone would take responsibility for Pipermail. As crufty as it is, it's all we have, and it's good enough for many people. But it's a complicated system that needs its own steward. Anybody willing to put the time and effort into it, I'd be happy to add as a cvs committer (although we have to watch out about GNU issues -- but several people have already assigned their future changes to the FSF). As for the core system, I admit to being protective of it. I'm willing to loosen my grip if it helps Mailman development move along faster. There are folks in the community who know enough about the system, and whom I trust to make changes to the code. -Barry From gabrel@wp.pl Thu Mar 14 13:31:56 2002 From: gabrel@wp.pl (Mariusz Gabrel) Date: Thu, 14 Mar 2002 14:31:56 +0100 Subject: [Mailman-i18n] Polish language packs Message-ID: Hi! I'm looking for polish language pack for mailman. Where can i find it? mg From Dan Mick Fri Mar 15 02:35:23 2002 From: Dan Mick (Dan Mick) Date: Thu, 14 Mar 2002 18:35:23 -0800 (PST) Subject: [Mailman-i18n] Re: [Mailman-Developers] Bug in Chinese language selections and options page? Message-ID: <200203150235.g2F2ZTWk023329@utopia.West.Sun.COM> > I am native Chinese speaker, and I have installed mailman-2.0.8 English > version successfully on my > computer, and I want to help building Chinese templates, what should I do > then? 2.1 is the release with multi-lingual support. To help out, subscribe to mailman-i18n@python.org (see http://mail.python.org/mailman/listinfo/mailman-i18n) and volunteer; I'm sure your help would be appreciated. From std@std.priv.at Fri Mar 29 20:31:48 2002 From: std@std.priv.at (Stefan Divjak) Date: Fri, 29 Mar 2002 21:31:48 +0100 Subject: [Mailman-i18n] Re: download of german languagepack In-Reply-To: References: Message-ID: <200203292123.25319@std.priv.at> > we would like to download a german languagepack for mailman 2.1 German templates are included by default, although some files are missing in the $prefix/templates/de directory, and should be downloaded from the CVS. -- Stefan Divjak alias std@std.priv.at Graz, Austria, Europe From rodolfo@pilas.net Fri Mar 29 22:10:33 2002 From: rodolfo@pilas.net (Rodolfo Pilas) Date: 29 Mar 2002 19:10:33 -0300 Subject: [Mailman-i18n] Mailman - Spanish In-Reply-To: References: Message-ID: <1017439837.4936.94.camel@julieta> Gracias Max y Daniel por ofrecerse para cooperar con la traducci=F3n a nuestro idioma. En primer lugar les confirmo que la versi=F3n 2.1 ya tiene soporte a espa=F1ol, aunque la =FAltima la 2.1b1 tiene cosas nuevas a=FAn no traducid= as. Creo que hay mucho trabajo para hacer en la etapa de correcci=F3n m=E1s que en la de traducci=F3n. De todas formas qui=E9n coordina la traducci=F3n al espa=F1ol es Amaya . Saludos. =20 --=20 Rodolfo Pilas Quien los puso a estos tipos donde estan, rodolfo@pilas.net Quien los deja seguir en su lugar, http://rodolfo.pilas.net Quien los baja ahora de su altar, ICQ #17461636 Quien les paga para que hagan lo que haran http://xtralinux.org -=3D# Apocalipsis Now % Cuarteto de Nos #=3D- Public GnuPG key: http://www.keyserver.net 1024D/57153363 2001-06-02 key fingerprint =3D DAAE 3246 3F7D A420 B7A0 48A5 D120 C773 5715 3363 From quartertone@mac.com Sun Mar 31 10:25:53 2002 From: quartertone@mac.com (Gary Wang) Date: Sun, 31 Mar 2002 19:25:53 +0900 Subject: [Mailman-i18n] Subject lines in Archives Message-ID: hiya. I've got Mailman 2.1.b1 installed, and I was wondering about international (specifically Japanese) characters in the subject line. When recieving via e-mail (and viewing with a capable e-mail client), the subject line, text, etc are all displayed correctly. As a test, I put a few kanji in the title and message body, and hopped over to the archives. The kanji/japanese in the body showed up just fine, but the subject line became this: =?ISO-2022-JP?B?GyRCRnxLXDhsISkbKEI=?= Is this a known bug/work in progress, or is there something I can change to fix it? thanks, gary gary c wang ICQ: 4343405 From che@debian.org Sun Mar 31 11:14:33 2002 From: che@debian.org (Ben Gertzfield) Date: Sun, 31 Mar 2002 20:14:33 +0900 Subject: [Mailman-i18n] Subject lines in Archives In-Reply-To: (Gary Wang's message of "Sun, 31 Mar 2002 19:25:53 +0900") References: Message-ID: <87vgbd3s6e.fsf@nausicaa.interq.or.jp> >>>>> "Gary" == Gary Wang writes: Gary> hiya. I've got Mailman 2.1.b1 installed, and I was Gary> wondering about international (specifically Japanese) Gary> characters in the subject line. When recieving via e-mail Gary> (and viewing with a capable e-mail client), the subject Gary> line, text, etc are all displayed correctly. As a test, I Gary> put a few kanji in the title and message body, and hopped Gary> over to the archives. The kanji/japanese in the body showed Gary> up just fine, but the subject line became this: Gary> =?ISO-2022-JP?B?GyRCRnxLXDhsISkbKEI=?= Is this a known Gary> bug/work in progress, or is there something I can change to Gary> fix it? Pipermail is just not meant to work with multiple character sets, unfortunately. It needs major work. Even if we hacked it to properly decode subject/from/to/cc header lines, the first time two people posted to the list in different character sets, you would get an invalid archive! We are working on a solution, but it's going to take major major work on Pipermail. For the time being, if you would like an archiving system with ties to Mailman that supports Japanese (even in the subject line), please see my system to integrate Mailman with Hypermail: http://nausicaa.interq.or.jp/mailman/hypermail-conf/ Just turn off pipermail archiving and turn on "archive to mbox" only for all your lists, and these cron jobs will create the spool directories etc. automatically. Ben -- Brought to you by the letters O and L and the number 16. "A kinkle is a clever method." Debian GNU/Linux maintainer of Gimp and Nethack -- http://www.debian.org/ From loewis@informatik.hu-berlin.de Sun Mar 31 11:17:03 2002 From: loewis@informatik.hu-berlin.de (Martin von Loewis) Date: Sun, 31 Mar 2002 13:17:03 +0200 (CEST) Subject: [Mailman-i18n] Subject lines in Archives In-Reply-To: from Gary Wang at "Mar 31, 2002 07:25:53 pm" Message-ID: <200203311117.g2VBH3cw016477@paros.informatik.hu-berlin.de> > Is this a known bug/work in progress, or is there something I can change > to fix it? It's a known bug; please see http://sourceforge.net/tracker/index.php?func=detail&aid=510415&group_id=103&atid=300103 for a patch. I'd appreciate if you could comment on the patch on whether it works for you. Notice that you might have to regenerate the archive index. Regards, Martin From loewis@informatik.hu-berlin.de Sun Mar 31 11:33:45 2002 From: loewis@informatik.hu-berlin.de (Martin von Loewis) Date: Sun, 31 Mar 2002 13:33:45 +0200 (CEST) Subject: [Mailman-i18n] Subject lines in Archives In-Reply-To: <87vgbd3s6e.fsf@nausicaa.interq.or.jp> from Ben Gertzfield at "Mar 31, 2002 08:14:33 pm" Message-ID: <200203311133.g2VBXkWU016505@paros.informatik.hu-berlin.de> > >>>>> "Gary" == Gary Wang writes: > > Pipermail is just not meant to work with multiple character sets, > unfortunately. It needs major work. Even if we hacked it to properly > decode subject/from/to/cc header lines, the first time two people > posted to the list in different character sets, you would get an > invalid archive! > > We are working on a solution, but it's going to take major major > work on Pipermail. This is not true. Pipermail is well prepared to deal with character sets in archives; it just needs little fixing. Regards, Martin From che@debian.org Sun Mar 31 11:57:08 2002 From: che@debian.org (Ben Gertzfield) Date: Sun, 31 Mar 2002 20:57:08 +0900 Subject: [Mailman-i18n] Subject lines in Archives In-Reply-To: <200203311133.g2VBXkWU016505@paros.informatik.hu-berlin.de> (Martin von Loewis's message of "Sun, 31 Mar 2002 13:33:45 +0200 (CEST)") References: <200203311133.g2VBXkWU016505@paros.informatik.hu-berlin.de> Message-ID: <87r8m13q7f.fsf@nausicaa.interq.or.jp> >>>>> "Martin" == Martin von Loewis writes: Martin> This is not true. Pipermail is well prepared to deal with Martin> character sets in archives; it just needs little fixing. You tell me what happens when I post in Japanese, then the next person posts in Chinese, then the next person posts in German. You get an unreadable, illegally encoded HTML file that may scramble peoples' terminals or crash them. If you have found a solution for this other than converting everything to UTF-8, I would love to hear it. Ben -- Brought to you by the letters Z and J and the number 12. "A yonker is a young man." Debian GNU/Linux maintainer of Gimp and Nethack -- http://www.debian.org/ From loewis@informatik.hu-berlin.de Sun Mar 31 12:49:59 2002 From: loewis@informatik.hu-berlin.de (Martin von Loewis) Date: Sun, 31 Mar 2002 14:49:59 +0200 (CEST) Subject: [Mailman-i18n] Subject lines in Archives In-Reply-To: <87r8m13q7f.fsf@nausicaa.interq.or.jp> from Ben Gertzfield at "Mar 31, 2002 08:57:08 pm" Message-ID: <200203311249.g2VCnxic016571@paros.informatik.hu-berlin.de> > You tell me what happens when I post in Japanese, then the next person > posts in Chinese, then the next person posts in German. > > You get an unreadable, illegally encoded HTML file that may scramble > peoples' terminals or crash them. > > If you have found a solution for this other than converting > everything to UTF-8, I would love to hear it. Just try my patch. As usual, pipermail will count the number of articles by encoding, and select the majority encoding as the encoding of the index. All messages in other encodings will be converted to that encoding. If conversion fails, HTML character references are emitted. It requires a codec for all encodings but the majority encoding. Look Ma, no UTF-8. Regards, Martin From che@debian.org Sun Mar 31 14:15:59 2002 From: che@debian.org (Ben Gertzfield) Date: Sun, 31 Mar 2002 23:15:59 +0900 Subject: [Mailman-i18n] Subject lines in Archives In-Reply-To: <200203311249.g2VCnxic016571@paros.informatik.hu-berlin.de> (Martin von Loewis's message of "Sun, 31 Mar 2002 14:49:59 +0200 (CEST)") References: <200203311249.g2VCnxic016571@paros.informatik.hu-berlin.de> Message-ID: <87n0wo4ycg.fsf@nausicaa.interq.or.jp> >>>>> "Martin" == Martin von Loewis writes: Martin> Just try my patch. As usual, pipermail will count the Martin> number of articles by encoding, and select the majority Martin> encoding as the encoding of the index. All messages in Martin> other encodings will be converted to that encoding. If Martin> conversion fails, HTML character references are Martin> emitted. It requires a codec for all encodings but the Martin> majority encoding. I'm a bit confused. How exactly do you propose converting non-Latin encoded text to Latin? Since it cannot ever be converted, are you going to emit Unicode HTML character references? Also, what do you do to map charsets to Python Unicode codecs? They're not one-to-one; for example, ISO-2022-JP goes to japanese.iso-2022-jp. Anyway, the patch sounds very nice, and I'm sure Barry is just waiting for you to report that it works fine with Mailman 2.1 beta. It's a lot like one I sent him a while ago, but sounds much further along. Ben -- Brought to you by the letters W and V and the number 2. "Wuzzle means to mix." Debian GNU/Linux maintainer of Gimp and Nethack -- http://www.debian.org/ From loewis@informatik.hu-berlin.de Sun Mar 31 15:47:35 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 31 Mar 2002 17:47:35 +0200 Subject: [Mailman-i18n] Subject lines in Archives In-Reply-To: <87n0wo4ycg.fsf@nausicaa.interq.or.jp> References: <200203311249.g2VCnxic016571@paros.informatik.hu-berlin.de> <87n0wo4ycg.fsf@nausicaa.interq.or.jp> Message-ID: Ben Gertzfield writes: > Martin> If > Martin> conversion fails, HTML character references are > Martin> emitted. > I'm a bit confused. How exactly do you propose converting non-Latin > encoded text to Latin? Since it cannot ever be converted, are you > going to emit Unicode HTML character references? Yes, that's what I said, and that's what it does. > Also, what do you do to map charsets to Python Unicode codecs? codecs.lookup (actually, just unicode(str, encoding)). > They're not one-to-one; for example, ISO-2022-JP goes to > japanese.iso-2022-jp. That is actually a bug in the Japanese codecs package; it ought to register a lookup function, instead of relying on the default lookup function. If that bug is not fixed, modifying codecs.encodings.aliases.aliases might be appropriate. Regards, Martin