From che@debian.org Fri Feb 1 00:37:42 2002 From: che@debian.org (Ben Gertzfield) Date: Fri, 01 Feb 2002 09:37:42 +0900 Subject: [Mailman-i18n] HTML entities (é) in es, it, no translations In-Reply-To: (Martin von Loewis's message of "31 Jan 2002 17:24:53 +0100") References: <87u1t26ggh.fsf@nausicaa.interq.or.jp> <87lmee69jk.fsf@nausicaa.interq.or.jp> <87aduu62al.fsf@nausicaa.interq.or.jp> Message-ID: <87665i5961.fsf@nausicaa.interq.or.jp> >>>>> "Martin" == Martin von Loewis writes: Martin> I can't see any reason why gettext(3) would have any Martin> difficulties with iso-2022-jp. It's possible that " could exist within a iso-2022-jp string, I believe; this would probably throw off gettext's parsing when you get a string like: "\eB(stuff stuff stuff " more stuff stuff\eb" It's too bad that gettext doesn't seem to have an alternate quoting mechanism. Ben -- Brought to you by the letters G and V and the number 9. "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 tkikuchi@is.kochi-u.ac.jp Fri Feb 1 00:44:53 2002 From: tkikuchi@is.kochi-u.ac.jp (Tokio Kikuchi) Date: Fri, 01 Feb 2002 09:44:53 +0900 Subject: [Mailman-i18n] HTML entities (é) in es, it, no translations References: <87u1t26ggh.fsf@nausicaa.interq.or.jp> <87lmee69jk.fsf@nausicaa.interq.or.jp> <87aduu62al.fsf@nausicaa.interq.or.jp> Message-ID: <3C59E505.5010608@is.kochi-u.ac.jp> Hi, > I'm not surprised. The traditional encoding on Unix is eucJP; and > gettext/libc can transparently recode the message to any target > format. So the catalog could be in eucJP, or utf-8, and you still > could produce messages in iso-2022-jp. > > I just tried it on a catalog; msgfmt complained about two problems: > for one thing, it complains that iso-2022-jp is not a portable > character set name, i.e. that many systems apparently don't recognize > this character set name. The other problem is that it complains about > illegal escape sequences. I don't know where this comes from; it might > be a gettext mbcs bug, or a glibc bug, or an error in my data. If you > have real data which are not properly processed by msgfmt, please > report that bug to Bruno Haible. > > I can't see any reason why gettext(3) would have any difficulties with > iso-2022-jp. iso-2022-jp conatins " and \ in the second byte. Big5 also. I think iso-2022-jp is only for message transportation and not good for text manipulation like within Mailman. I still recommend all the messages and templates should be encoded in EUC-JP within Mailman and Web Interfaces, and converting them into iso-2022-jp when mail is in and out. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From che@debian.org Fri Feb 1 01:27:41 2002 From: che@debian.org (Ben Gertzfield) Date: Fri, 01 Feb 2002 10:27:41 +0900 Subject: [Mailman-i18n] HTML entities (é) in es, it, no translations In-Reply-To: <3C59E505.5010608@is.kochi-u.ac.jp> (Tokio Kikuchi's message of "Fri, 01 Feb 2002 09:44:53 +0900") References: <87u1t26ggh.fsf@nausicaa.interq.or.jp> <87lmee69jk.fsf@nausicaa.interq.or.jp> <87aduu62al.fsf@nausicaa.interq.or.jp> <3C59E505.5010608@is.kochi-u.ac.jp> Message-ID: <87sn8m3saa.fsf@nausicaa.interq.or.jp> >>>>> "Tokio" == Tokio Kikuchi writes: Tokio> I still recommend all the messages and templates should be Tokio> encoded in EUC-JP within Mailman and Web Interfaces, and Tokio> converting them into iso-2022-jp when mail is in and out. This is exactly what the patch I sent to the list yesterday does. Ben -- Brought to you by the letters L and O and the number 11. "It is sad. *Campers* cannot *dance*. Not even a *party*." Debian GNU/Linux maintainer of Gimp and Nethack -- http://www.debian.org/ From tkikuchi@is.kochi-u.ac.jp Fri Feb 1 01:33:40 2002 From: tkikuchi@is.kochi-u.ac.jp (Tokio Kikuchi) Date: Fri, 01 Feb 2002 10:33:40 +0900 Subject: [Mailman-i18n] HTML entities (é) in es, it, no translations References: <87u1t26ggh.fsf@nausicaa.interq.or.jp> <87lmee69jk.fsf@nausicaa.interq.or.jp> <87aduu62al.fsf@nausicaa.interq.or.jp> <3C59E505.5010608@is.kochi-u.ac.jp> <87sn8m3saa.fsf@nausicaa.interq.or.jp> Message-ID: <3C59F074.5040408@is.kochi-u.ac.jp> Ben Gertzfield wrote: >>>>>>"Tokio" == Tokio Kikuchi writes: >>>>>> > > Tokio> I still recommend all the messages and templates should be > Tokio> encoded in EUC-JP within Mailman and Web Interfaces, and > Tokio> converting them into iso-2022-jp when mail is in and out. > > This is exactly what the patch I sent to the list yesterday does. Well then, why do you need iso-2022-jp in gettext messages ? -- Tokio Kikuchi From che@debian.org Fri Feb 1 02:46:18 2002 From: che@debian.org (Ben Gertzfield) Date: Fri, 01 Feb 2002 11:46:18 +0900 Subject: [Mailman-i18n] HTML entities (é) in es, it, no translations In-Reply-To: <3C59F074.5040408@is.kochi-u.ac.jp> (Tokio Kikuchi's message of "Fri, 01 Feb 2002 10:33:40 +0900") References: <87u1t26ggh.fsf@nausicaa.interq.or.jp> <87lmee69jk.fsf@nausicaa.interq.or.jp> <87aduu62al.fsf@nausicaa.interq.or.jp> <3C59E505.5010608@is.kochi-u.ac.jp> <87sn8m3saa.fsf@nausicaa.interq.or.jp> <3C59F074.5040408@is.kochi-u.ac.jp> Message-ID: <87ofj9537p.fsf@nausicaa.interq.or.jp> >>>>> "Tokio" == Tokio Kikuchi writes: Tokio> Well then, why do you need iso-2022-jp in gettext messages Tokio> ? I don't.. The discussion was just about how it was interesting that gettext does not/can not support iso-2022-jp. We have no need of using iso-2022-jp gettext strings in Mailman. Sorry if I confused you. Ben -- Brought to you by the letters M and L and the number 9. "It makes my nipples hard!" Debian GNU/Linux maintainer of Gimp and Nethack -- http://www.debian.org/ From loewis@informatik.hu-berlin.de Fri Feb 1 10:39:47 2002 From: loewis@informatik.hu-berlin.de (Martin von Loewis) Date: 01 Feb 2002 11:39:47 +0100 Subject: [Mailman-i18n] HTML entities (é) in es, it, no translations In-Reply-To: <87665i5961.fsf@nausicaa.interq.or.jp> References: <87u1t26ggh.fsf@nausicaa.interq.or.jp> <87lmee69jk.fsf@nausicaa.interq.or.jp> <87aduu62al.fsf@nausicaa.interq.or.jp> <87665i5961.fsf@nausicaa.interq.or.jp> Message-ID: Ben Gertzfield writes: > Martin> I can't see any reason why gettext(3) would have any > Martin> difficulties with iso-2022-jp. > > It's possible that " could exist within a iso-2022-jp string, I > believe; this would probably throw off gettext's parsing when > you get a string like: That would be a msgfmt(1) problem, right? I doubt gettext(3) has any problems if you manage to compile the catalog. As for the msgfmt problem, I think msgfmt uses the mbcs routines of the C library, which should be capable of distinguishing between a byte that is part of a multi-byte character, and an individual ASCII byte. So I think this should be implementable without any change to the syntax; if it still fails, you might want to submit a bug report. Regards, Martin From loewis@informatik.hu-berlin.de Fri Feb 1 11:05:10 2002 From: loewis@informatik.hu-berlin.de (Martin von Loewis) Date: 01 Feb 2002 12:05:10 +0100 Subject: [Mailman-i18n] HTML entities (é) in es, it, no translations In-Reply-To: <3C59E505.5010608@is.kochi-u.ac.jp> References: <87u1t26ggh.fsf@nausicaa.interq.or.jp> <87lmee69jk.fsf@nausicaa.interq.or.jp> <87aduu62al.fsf@nausicaa.interq.or.jp> <3C59E505.5010608@is.kochi-u.ac.jp> Message-ID: Tokio Kikuchi writes: > iso-2022-jp contains " and \ in the second byte. Big5 also. That should not be a problem: the MBCS routines of the C library (or, rather, iconv) should be able to take care of that (if the encoding is known); so the problem can be solved. I know it isn't, but anybody interested in solving it could either report a bug or maybe even design a patch. Regards, Martin From james@daa.com.au Sun Feb 3 02:43:45 2002 From: james@daa.com.au (James Henstridge) Date: Sun, 03 Feb 2002 10:43:45 +0800 (WST) Subject: [Mailman-i18n] HTML entities (é) in es, it, no translations In-Reply-To: <3C59E505.5010608@is.kochi-u.ac.jp> References: <87u1t26ggh.fsf@nausicaa.interq.or.jp> <87lmee69jk.fsf@nausicaa.interq.or.jp> <87aduu62al.fsf@nausicaa.interq.or.jp> <3C59E505.5010608@is.kochi-u.ac.jp> Message-ID: <1012704225.3c5ca3e19a1ed@www.daa.com.au> Quoting Tokio Kikuchi : > iso-2022-jp conatins " and \ in the second byte. Big5 also. > > I think iso-2022-jp is only for message transportation and > not good for text manipulation like within Mailman. > > I still recommend all the messages and templates should > be encoded in EUC-JP within Mailman and Web Interfaces, and > converting them into iso-2022-jp when mail is in and out. The GNU gettext utilities should be able to handle these charsets without problem (provided you have gettext >= 0.10.36). There were a number of changes between 0.10.35 and 36, so that it takes the encoding into account when processing the file (so that the second byte of a multi-byte character doesn't need to be escaped; in fact, if you did escape bytes like that, the file won't work with newer gettext). Whether the python tools do the same when processing a message catalog is another matter. James. -- James Henstridge From che@debian.org Mon Feb 4 03:48:51 2002 From: che@debian.org (Ben Gertzfield) Date: Mon, 04 Feb 2002 12:48:51 +0900 Subject: [Mailman-i18n] Japanese mailman.po file (EUC-JP) has JIS ^[)B in it Message-ID: <87lme9ykik.fsf@nausicaa.interq.or.jp> Kikuchi-san, I noticed today that CVS Mailman's mailman.po translation for Japanese has a single iso-2022-jp escape on line 3043: "削除されませ. ^[)B$3$NCM\n" ^^^ euc-jp ^^^ iso-2022-jp This makes it very hard to edit the mailman.po file in emacs, as it tries to switch to iso-2022-jp mode after this line. It looks like that line of the translation is just not finished.. perhaps you should just remove it from the file completely? Thanks, Ben -- Brought to you by the letters V and I and the number 4. "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 tkikuchi@is.kochi-u.ac.jp Mon Feb 4 05:10:28 2002 From: tkikuchi@is.kochi-u.ac.jp (Tokio Kikuchi) Date: Mon, 04 Feb 2002 14:10:28 +0900 Subject: [Mailman-i18n] Japanese mailman.po file (EUC-JP) has JIS ^[)B in it References: <87lme9ykik.fsf@nausicaa.interq.or.jp> Message-ID: <3C5E17C4.1020609@is.kochi-u.ac.jp> Ben, Sorry for the inconvenience. I'm catching up. Ben Gertzfield wrote: > Kikuchi-san, > > I noticed today that CVS Mailman's mailman.po translation for Japanese > has a single iso-2022-jp escape on line 3043: > > "削除されませ. ^[)B$3$NCM\n" > > ^^^ euc-jp ^^^ iso-2022-jp funny 'cause I didn't mixed iso... -- 菊地時夫 tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ 〒780-8520 高知大学理学部情報科学教室 From epulido@grancanaria.com Mon Feb 4 14:07:56 2002 From: epulido@grancanaria.com (Esther Pulido (SERVINFO)) Date: Mon, 4 Feb 2002 14:07:56 +0000 Subject: [Mailman-i18n] Spanish translation? Message-ID: <1012831676.3c5e95bc42a67@mail.grancanaria.com> Hallo! I have just subscribed to the list. Whatis the current status of the Spanish translation? Is it available for= =20 download somewhere? Thanks in advance for your help. Cheers, Esther Hola. Me acabo de suscribir a la lista. =BFCu=E1n avanzada est=E1 la traducci=F3n al castellano? =BFSe puede desc= argar desde=20 alg=FAn sitio?=20 Gracias de antemano por tu ayuda. Saludos, Esther ------------------------------------------------- Este email ha sido enviado a trav=E9s de http://www.grancanaria.com From tkikuchi@is.kochi-u.ac.jp Tue Feb 5 02:25:15 2002 From: tkikuchi@is.kochi-u.ac.jp (Tokio Kikuchi) Date: Tue, 05 Feb 2002 11:25:15 +0900 Subject: [Mailman-i18n] japanese update Message-ID: <3C5F428B.4050202@is.kochi-u.ac.jp> Hi, I think I have now catched up the CVS. Please find the latest Japanese translation from: http://mm.tkikuchi.net/mailman-2.1alpha.ja/mailman.i18n.ja.tar.gz Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From jcrey@uma.es Tue Feb 5 08:34:41 2002 From: jcrey@uma.es (Juan Carlos Rey Anaya) Date: Tue, 05 Feb 2002 09:34:41 +0100 Subject: [Mailman-i18n] Spanish translation? References: <1012831676.3c5e95bc42a67@mail.grancanaria.com> Message-ID: <3C5F9921.3F2C3234@uma.es> I have just finished it. I will send it to Barry today. Cheers --=20 ___ / F \ [[[]]]] ( O O ) #----------------0000--(_)--0000---------------# | Juan Carlos Rey Anaya (jcrey@uma.es) | | Servicio Central de inform=E1tica | | Universidad de M=E1laga - Espa=F1a | #----------------------------------------------# From jcrey@uma.es Mon Feb 11 10:39:42 2002 From: jcrey@uma.es (Juan Carlos Rey Anaya) Date: Mon, 11 Feb 2002 11:39:42 +0100 Subject: [Mailman-i18n] New spanish champion Message-ID: <3C679F6E.CB1393F4@uma.es> There has been a change in spanish champion. The person in charge of spanish translation is Amaya . Cheers --=20 ___ / F \ [[[]]]] ( O O ) #----------------0000--(_)--0000---------------# | Juan Carlos Rey Anaya (jcrey@uma.es) | | Servicio Central de inform=E1tica | | Universidad de M=E1laga - Espa=F1a | #----------------------------------------------# From barry@zope.com Wed Feb 20 22:02:22 2002 From: barry@zope.com (Barry A. Warsaw) Date: Wed, 20 Feb 2002 17:02:22 -0500 Subject: [Mailman-i18n] New spanish champion References: <3C679F6E.CB1393F4@uma.es> Message-ID: <15476.7406.75367.520389@geddy.wooz.org> >>>>> "JCRA" == Juan Carlos Rey Anaya writes: JCRA> There has been a change in spanish champion. The person in JCRA> charge of spanish translation is Amaya . Very good, thanks for the update. -Barry From max@sinapsisglobal.com Mon Feb 18 16:37:03 2002 From: max@sinapsisglobal.com (Max Esquivel) Date: Mon, 18 Feb 2002 10:37:03 -0600 Subject: [Mailman-i18n] Mailman - Spanish Message-ID: Hi: I would like to volunteer to help translate Mailman into spanish. Please advise Thanks _______________________________ Max Esquivel Sinapsis Global S.A max@sinapsisglobal.com www.sinapsisglobal.com From adkor@maxkor.com Tue Feb 26 14:53:28 2002 From: adkor@maxkor.com (Adrian Kornhauser) Date: Tue, 26 Feb 2002 08:53:28 -0600 (CST) Subject: [Mailman-i18n] Spanish version of mailman. Message-ID: Hi! I wanted to know if there is any effort to translate mailman to spanish,=20 and if the group needs help. I need to have a translated mailman so if=20 there is no effort I would like to know if there is a possiblility for me= =20 to do it. Best Regards. Adri=E1n From dcanas@intnet.co.cr Wed Feb 27 07:26:18 2002 From: dcanas@intnet.co.cr (Daniel Canas) Date: Wed, 27 Feb 2002 02:26:18 -0500 Subject: [Mailman-i18n] (no subject) Message-ID: <4A96FE9A-2B53-11D6-B2BB-0030657E2F48@intnet.co.cr> I would like information on a Spanish translation of Mailman. Is there one available, if not i would volunteer do doone. Daniel Canas dcanas@intnet.co.cr From office@atvirtual.net Wed Feb 13 22:01:24 2002 From: office@atvirtual.net (ATvirtual.NET) Date: Wed, 13 Feb 2002 23:01:24 +0100 Subject: [Mailman-i18n] download of german languagepack Message-ID: we would like to download a german languagepack for mailman 2.1 best regards martin fischer -------------------------------------------- ATvirtual.NET Pumpernig & Fischer OEG Rechte Wienzeile 173/16 A - 1050 Wien Austria Tel.: +43 1 9743858 Fax: +43 1 9667559 Mobile: +43 676 6136552 E-Mail: office@atvirtual.net WWW: http://www.atvirtual.net/ --------------------------------------------