From wilane@cyg.sn Sun Nov 3 17:29:10 2002 From: wilane@cyg.sn (Ousmane Wilane) Date: Sun, 03 Nov 2002 17:29:10 +0000 Subject: [Mailman-i18n] Another fr champion Message-ID: Hi, 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 back ASAP. I posted on traduc@traduc.org (fr language team) and mailman-fr@rezo.net to find a taker, I'll let you know as soon as I find another champion. Cheers. From mantas@akl.lt Mon Nov 4 11:49:36 2002 From: mantas@akl.lt (Mantas Kriauciunas) Date: Mon, 4 Nov 2002 13:49:36 +0200 Subject: [Mailman-i18n] Starting a Lithuanian (lt) translation Message-ID: <20021104114936.GA23024@berzas.akl.lt> Hi, Lithuanian open source organization (www.akl.lt) decided to translate mailman to Lithuanian (lt) language. As I know there are no Lithuanian translations of mailman, aren't it ? Is there anything else we should know, besides what's in README-I18N.en and list.org/MM21/i18n.html? Mantas Kriauciunas From cerdil@ttnet.net.tr Sun Nov 3 15:32:50 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Sun, 3 Nov 2002 17:32:50 +0200 Subject: [Mailman-i18n] how to encode in iso-8859-9 charset Message-ID: <001801c2834e$45ef17a0$6501a8c0@coco> This is a multi-part message in MIME format. ---------------------- multipart/alternative attachment i, have installed the , revolutionary 2.1b+ version,its = perfect, but one minor thing , for me is the lack of iso-8859-9 = charset support. i want to integrate the usage of turkish iso- 8859-9 charset = encoding with the characters like, =FC,=F6, c with a comma at = the bottom, s with a comma at the bottom, g with a comma at top. how can i do this? how to we enable a charset, other than writing templates ? thank you shann ---------------------- multipart/alternative attachment An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-i18n/attachments/20021103/55dfd68e/attachment.html ---------------------- multipart/alternative attachment-- From che@debian.org Mon Nov 4 17:59:19 2002 From: che@debian.org (Ben Gertzfield) Date: Mon, 04 Nov 2002 09:59:19 -0800 Subject: [Mailman-i18n] how to encode in iso-8859-9 charset In-Reply-To: <001801c2834e$45ef17a0$6501a8c0@coco> References: <001801c2834e$45ef17a0$6501a8c0@coco> Message-ID: <3DC6B577.3030700@debian.org> shawn Erdil wrote: > i, have installed the , revolutionary 2.1b+ version,its =20 > perfect, but one minor thing , for me is the lack of =20 > iso-8859-9 charset support. > =20 > i want to integrate the usage of turkish iso- 8859-9 charset =20 > encoding with the characters like, =FC,=F6, c with a comma at =20 > the bottom, s with a comma at the bottom, g with a comma at top. > =20 > how can i do this? > how to we enable a charset, other than writing templates ? Mail to and from a list in iso-8859-9 will work just fine, and the HTML=20 archives for Pipermail should be able to handle iso-8859-9 emails with=20 no problem. The web and email interfaces have not yet been translated to Turkish, so=20 we would need someone (like you!) to translate the Mailman templates and=20 catalog files. Please download the 2.1b4 Mailman source code and read the file=20 README-I18N.en if you want to help translate Mailman to Turkish. Thanks, Ben From loewis@informatik.hu-berlin.de Mon Nov 4 18:07:32 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 04 Nov 2002 19:07:32 +0100 Subject: [Mailman-i18n] how to encode in iso-8859-9 charset In-Reply-To: <3DC6B577.3030700@debian.org> References: <001801c2834e$45ef17a0$6501a8c0@coco> <3DC6B577.3030700@debian.org> Message-ID: Ben Gertzfield writes: > > i, have installed the , revolutionary 2.1b+ version,its > > perfect, but one minor thing , for me is the lack of > > iso-8859-9 charset support. [...] > Mail to and from a list in iso-8859-9 will work just fine, and the > HTML archives for Pipermail should be able to handle iso-8859-9 emails > with no problem. Or, to put it in different words: Nothing needs to be done; Mailman supports iso-8859-9 out of the box, no configuration required. If you observe differently, please report in detail where this did not work as expected. Regards, Martin From barry@python.org Mon Nov 4 20:59:08 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 4 Nov 2002 15:59:08 -0500 Subject: [Mailman-i18n] Welcome to Mailman 2.1 References: <15805.55591.47010.608367@gargle.gargle.HOWL> <3DBDE16B.3020509@debian.org> <15806.428.793814.661653@gargle.gargle.HOWL> <3DBE366D.4020103@debian.org> Message-ID: <15814.57244.792534.417096@gargle.gargle.HOWL> >>>>> "BG" == Ben Gertzfield writes: BG> OK! I went to the user options page and went through a number BG> of languages to see what interfaces I got. To be extra mean BG> to the page, I entered my real name with Japanese characters BG> (from the US English page!) and the Unicode character BG> references came through perfectly. Good job with that! Cool! BG> Two issues: BG> I selected Simplified Chinese as my interface at BG> http://mail.python.org/mailman/options/mailman-i18n/che@debian.org BG> and got: BG> Bug in Mailman version 2.1b4+ We're sorry, we hit a bug! If BG> you would like to help us identify the problem, please email a BG> copy of this page to the webmaster for this site with a BG> description of what happened. Thanks! Traceback: Traceback BG> (most recent call last): File BG> "/usr/local/mailman-2.1/scripts/driver", line 87, in run_main BG> main() File "/usr/local/mailman-2.1/Mailman/Cgi/options.py", BG> line 594, in main options_page(mlist, doc, user, cpuser, BG> userlang, msg) File BG> "/usr/local/mailman-2.1/Mailman/Cgi/options.py", line 616, in BG> options_page fullname = BG> Utils.uncanonstr(mlist.getMemberName(user), userlang) File BG> "/usr/local/mailman-2.1/Mailman/Utils.py", line 768, in BG> uncanonstr return s.encode(charset) LookupError: unknown BG> encoding BG> [snip] BG> I wonder if I didn't confuse it with my Unicode real BG> name.. want to give it a look, Barry? Nope, the problem is that Python doesn't come with Chinese support out of the box so if you haven't installed the Chinese codecs, you shouldn't be allowed to choose that your list supports that language. I believe I have code in the Language category that tightens this up (although it won't de-select Simplified Chinese for you by default). If the list admin doesn't enable a language, then users can't choose it either. BG> Other than that, looks pretty good. I think the Korean BG> translation is a bit out of date (English peeks through here BG> and there) but the Japanese one looks great! Cool! We just need to get updated Korean translations. -Barry From barry@python.org Mon Nov 4 21:14:49 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 4 Nov 2002 16:14:49 -0500 Subject: [Mailman-i18n] Another fr champion References: Message-ID: <15814.58185.655937.793787@gargle.gargle.HOWL> >>>>> "OW" == Ousmane Wilane writes: OW> I have to let you know that I can no longer head up the French OW> translation effort because: OW> 1- My girlfriend is pregnant and the baby will be here real OW> soon. OW> 2- I left my last job and my actual Internet connection isn't OW> famous (56K analog with an HCF modem), my `cvs -q up -P -d's OW> are now endless. OW> I had a wonderful time working with this amazing software, OW> it's for me the best Mailing List software and a nice `Python OW> Cookbook', I'll be back ASAP. I wish you all the best in your new life adventures, and I can only say that being a father is one of the most amazing and rewarding experiences I've ever had. I hope you'll come back soon -- you've done a wonderful job on the French translations. OW> I posted on traduc@traduc.org (fr language team) and OW> mailman-fr@rezo.net to find a taker, I'll let you know as soon OW> as I find another champion. Maybe we should sign up for Translation Project support? -Barry From barry@python.org Mon Nov 4 21:17:12 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 4 Nov 2002 16:17:12 -0500 Subject: [Mailman-i18n] Starting a Lithuanian (lt) translation References: <20021104114936.GA23024@berzas.akl.lt> Message-ID: <15814.58328.304566.280431@gargle.gargle.HOWL> >>>>> "MK" == Mantas Kriauciunas writes: MK> Lithuanian open source organization (www.akl.lt) decided to MK> translate mailman to Lithuanian (lt) language. As I know there MK> are no Lithuanian translations of mailman, aren't it ? MK> Is there anything else we should know, besides what's in MK> README-I18N.en and list.org/MM21/i18n.html? Not unless you guys hit stumbling blocks. Do you have anything ready? I'd be happy to integrate either templates or catalogs, even if they're not complete. Looks like Lithuanian is Latin4, right? MK> Mantas Kriauciunas Shall I add you and www.akl.lit to the Mailman I18n champions page? -Barry From cerdil@ttnet.net.tr Mon Nov 4 21:36:26 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Mon, 4 Nov 2002 23:36:26 +0200 Subject: [Mailman-i18n] how to encode in iso-8859-9 charset References: <001801c2834e$45ef17a0$6501a8c0@coco><3DC6B577.3030700@debian.org> Message-ID: <003001c2844a$3b8232f0$6501a8c0@coco> MY CURRENT ARCHIVE OUTPUT AT THE MOMENT : ---------------------------------------------------------------------------- --------------------------------------- This is a multi-part message in MIME format. ---------------------- multipart/alternative attachment Merakla beklenen bir se=E7im yasadik. Merakla beklenmesinin sebebi yeni y=FCzlerin olmasi ve muhtesem d=F6rtl=FC olarak tanimlanan malum = siyaset=E7i dedelerimizin bir kisminin siyaset sahnesinden tasfiye olmus olmalari ---------------------------------------------------------------------------- ------------------------------------------ Martin & Ben, First of all, i'll ve glad to translate the templates to our language.you guys have written, such an advanced script.it'll be my pleasure to make a tiny contribution. NON DIGEST MODE This is the output i get in the pipermail archives, when i post a message, from outlook express with 8859-9 encoding, as you have mentioned , no problem in the return emails to an email client, such as outlook express, or etc.the encoding is OKAY, but , the header and footer don't show up, i think since the message, is in a different charset than us-ascii- the footer and header don't show up.i just get the message, i have sent to the list, NOTHING ELSE. the encoding , in the received email header shows as: Content-Type: multipart/alternative; İf i send the message as plain text, it comes out- okay with the header and footer included. but you know than i can't show the ı,ü,ç etc. Since everybody will send in mime with encoding 8859-9 windows -1254 charset,around here, these results wil show up, with the current config. the header and footer are important for me, since i want to put some adserver tags, in text format. ARCHIVES: in the archives - as you can see above, it shows quoted,and funky characters ,when the message is in mime format. when it is sent in plain text, it comes out okay. DIGEST MODE: it comes out OKAY with good encoding also, with the added header and footer. MY QUESTION? 1- how to show the header and footer ,in outlook ? when sending with 8859-9 mime from outlook?,when in non -digest mode 2- how to make it look formatted-presentable in the pipermail archives?when sending with mime 8859-9. Translation will be no problem, if we can get these to produce a correct output , as they are in your other language packs. EFFORTS: 1-should i try to put [iso-8859-9] in the mm-cfg.py to change defaults? thank you shawn Erdil. e-z banner internet media company Techifirm Retail solutions www.e-zbanner.com www.techifirm.com www.e-zbanner.com/bannerspace Mobile: +90 532 2637999 Direct: +90 212 3515656 Fax: +90 212 3513150 Address:Çevre sitesi 15- D/9 Akatlar,Istanbul- Turkey 80630 -------------------------------------------------------- ----- Original Message ----- From: "Martin v. Löwis" To: "Ben Gertzfield" Cc: "shawn Erdil" ; Sent: Monday, November 04, 2002 8:07 PM Subject: Re: [Mailman-i18n] how to encode in iso-8859-9 charset > Ben Gertzfield writes: > > > > i, have installed the , revolutionary 2.1b+ version,its > > > perfect, but one minor thing , for me is the lack of > > > iso-8859-9 charset support. > [...] > > Mail to and from a list in iso-8859-9 will work just fine, and the > > HTML archives for Pipermail should be able to handle iso-8859-9 emails > > with no problem. > > Or, to put it in different words: Nothing needs to be done; Mailman > supports iso-8859-9 out of the box, no configuration required. > > If you observe differently, please report in detail where this did not > work as expected. > > Regards, > Martin From che@debian.org Mon Nov 4 22:05:50 2002 From: che@debian.org (Ben Gertzfield) Date: Mon, 04 Nov 2002 14:05:50 -0800 Subject: [Mailman-i18n] how to encode in iso-8859-9 charset In-Reply-To: <001801c2834e$45ef17a0$6501a8c0@coco> References: <001801c2834e$45ef17a0$6501a8c0@coco><3DC6B577.3030700@debian.org> <003001c2844a$3b8232f0$6501a8c0@coco> Message-ID: <3DC6EF3E.10703@debian.org> shawn Erdil wrote: >MY CURRENT ARCHIVE OUTPUT AT THE MOMENT : >---------------------------------------------------------------------------- >--------------------------------------- >This is a multi-part message in MIME format. > >---------------------- multipart/alternative attachment >Merakla beklenen bir se=E7im yasadik. Merakla beklenmesinin sebebi yeni >y=FCzlerin olmasi ve muhtesem d=F6rtl=FC olarak tanimlanan malum = >siyaset=E7i >dedelerimizin bir kisminin siyaset sahnesinden tasfiye olmus olmalari >---------------------------------------------------------------------------- >------------------------------------------ > > It looks like there are some more pipermail (Mailman's default archiver) problems that we need to fix. I'll hopefully be able to take a look at the system this week, and work out the last of the internationalization bugs. Ben From loewis@informatik.hu-berlin.de Mon Nov 4 23:14:06 2002 From: loewis@informatik.hu-berlin.de (Martin von Loewis) Date: Tue, 5 Nov 2002 00:14:06 +0100 (CET) Subject: [Mailman-i18n] how to encode in iso-8859-9 charset Message-ID: <200211042314.gA4NE6GL013149@paros.informatik.hu-berlin.de> shawn, I still don't understand your problem. It seems we have difficulties to communicate, so please don't get annoyed by my lengthy questions. > --------------------------------------- > This is a multi-part message in MIME format. > > ---------------------- multipart/alternative attachment > Merakla beklenen bir se=E7im yasadik. Merakla beklenmesinin sebebi yeni > y=FCzlerin olmasi ve muhtesem d=F6rtl=FC olarak tanimlanan malum = > siyaset=E7i > dedelerimizin bir kisminin siyaset sahnesinden tasfiye olmus olmalari > ---------------------------------------------------------------------------- > ------------------------------------------ Where does this text come from? Is that some you have entered yourself (if so, where?), is this a header or footer? Who has created the multipart/alternative attachment? Can you perhaps send us the original message, ideally in a uuencoded form? > This is the output i get in the pipermail archives, when i post a > message, from outlook express with 8859-9 encoding, as you have > mentioned , no problem in the return emails to an email client, such as > outlook express, or etc.the encoding is OKAY, but , the header and > footer don't show up Which of the following two is the case: A: The header and footer do not appear in the message sent to each subscriber. B: The header and footer do not appear in the pipermail archives. If you have observed B, then this is correct behaviour: the header and footer is omitted from the pipermail archive on purpose. >, i think since the message, is in a different > charset than us-ascii- the footer and header don't show up.i just > get the message, i have sent to the list, NOTHING ELSE. > the encoding , in the received email header shows as: Content-Type: > multipart/alternative; Again, I don't understand: First you say that you do not see the header. Then you say that the header is transmitted as multipart/alternative. Which of these is the case? > _f i send the message as plain text, it comes out- okay with the > header and footer included. > but you know than i can't show the _,_,_ etc. I can't quote them right now (as elm does not support -9), but please have a look at http://mail.python.org/pipermail/mailman-i18n/2002-November/000708.html This message was correctly archived, as far as I can tell. Do you agree? > the header and footer are important for me, since i want to put some > adserver tags, in text format. Ok, it seems that your problem is somehow with the header and footer. Can you please post the text that you want to use as the header and footer? Don't hesitate to have this encoded as plain text in iso-8859-9: some of our mail readers will support this well, as will the archive. > ARCHIVES: > > in the archives - as you can see above, it shows quoted,and funky > characters ,when the message is in mime format. > when it is sent in plain text, it comes out okay. Unfortunately, I cannot see this from above. Are you saying you have copied this text from a archive web page? > 1- how to show the header and footer ,in outlook ? when sending with > 8859-9 mime from outlook?,when in non -digest mode Can you please send a message that you consider "8859-9" to this list? It seems to me that this message (i.e. the one I'm responding to) was a MIME message, and it was encoded as iso-8859-9. So you must be talking about something else. > 2- how to make it look formatted-presentable in the pipermail > archives?when sending with mime 8859-9. AFAICT, this works fine: no additional configuration needed. > 1-should i try to put [iso-8859-9] in the mm-cfg.py to change > defaults? I don't think you should change anything. First, we need to understand what you do before we can tell you what to change. Regards, Martin From loewis@informatik.hu-berlin.de Mon Nov 4 22:56:36 2002 From: loewis@informatik.hu-berlin.de (Martin von Loewis) Date: Mon, 4 Nov 2002 23:56:36 +0100 (CET) Subject: [Mailman-i18n] how to encode in iso-8859-9 charset In-Reply-To: <003001c2844a$3b8232f0$6501a8c0@coco> from shawn Erdil at "Nov 4, 2002 11:36:26 pm" Message-ID: <200211042309.gA4N9fpf012862@paros.informatik.hu-berlin.de> shawn, I still don't understand your problem. It seems we have difficulties to communicate, so please don't get annoyed by my lengthy questions. > --------------------------------------- > This is a multi-part message in MIME format. > > ---------------------- multipart/alternative attachment > Merakla beklenen bir se=E7im yasadik. Merakla beklenmesinin sebebi yeni > y=FCzlerin olmasi ve muhtesem d=F6rtl=FC olarak tanimlanan malum = > siyaset=E7i > dedelerimizin bir kisminin siyaset sahnesinden tasfiye olmus olmalari > ---------------------------------------------------------------------------- > ------------------------------------------ Where does this text come from? Is that some you have entered yourself (if so, where?), is this a header or footer? Who has created the multipart/alternative attachment? Can you perhaps send us the original message, ideally in a uuencoded form? > This is the output i get in the pipermail archives, when i post a > message, from outlook express with 8859-9 encoding, as you have > mentioned , no problem in the return emails to an email client, such as > outlook express, or etc.the encoding is OKAY, but , the header and > footer don't show up Which of the following two is the case: A: The header and footer do not appear in the message sent to each subscriber. B: The header and footer do not appear in the pipermail archives. If you have observed B, then this is correct behaviour: the header and footer is omitted from the pipermail archive on purpose. >, i think since the message, is in a different > charset than us-ascii- the footer and header don't show up.i just > get the message, i have sent to the list, NOTHING ELSE. > the encoding , in the received email header shows as: Content-Type: > multipart/alternative; Again, I don't understand: First you say that you do not see the header. Then you say that the header is transmitted as multipart/alternative. Which of these is the case? > _f i send the message as plain text, it comes out- okay with the > header and footer included. > but you know than i can't show the _,_,_ etc. I can't quote them right now (as elm does not support -9), but please have a look at http://mail.python.org/pipermail/mailman-i18n/2002-November/000708.html This message was correctly archived, as far as I can tell. Do you agree? > the header and footer are important for me, since i want to put some > adserver tags, in text format. Ok, it seems that your problem is somehow with the header and footer. Can you please post the text that you want to use as the header and footer? Don't hesitate to have this encoded as plain text in iso-8859-9: some of our mail readers will support this well, as will the archive. > ARCHIVES: > > in the archives - as you can see above, it shows quoted,and funky > characters ,when the message is in mime format. > when it is sent in plain text, it comes out okay. Unfortunately, I cannot see this from above. Are you saying you have copied this text from a archive web page? > 1- how to show the header and footer ,in outlook ? when sending with > 8859-9 mime from outlook?,when in non -digest mode Can you please send a message that you consider "8859-9" to this list? It seems to me that this message (i.e. the one I'm responding to) was a MIME message, and it was encoded as iso-8859-9. So you must be talking about something else. > 2- how to make it look formatted-presentable in the pipermail > archives?when sending with mime 8859-9. AFAICT, this works fine: no additional configuration needed. > 1-should i try to put [iso-8859-9] in the mm-cfg.py to change > defaults? I don't think you should change anything. First, we need to understand what you do before we can tell you what to change. Regards, Martin From barry@zope.com Mon Nov 4 23:26:36 2002 From: barry@zope.com (Barry A. Warsaw) Date: Mon, 4 Nov 2002 18:26:36 -0500 Subject: [Mailman-i18n] how to encode in iso-8859-9 charset References: <001801c2834e$45ef17a0$6501a8c0@coco> <3DC6B577.3030700@debian.org> <003001c2844a$3b8232f0$6501a8c0@coco> <3DC6EF3E.10703@debian.org> Message-ID: <15815.556.7700.354389@gargle.gargle.HOWL> >>>>> "BG" == Ben Gertzfield writes: BG> It looks like there are some more pipermail (Mailman's default BG> archiver) problems that we need to fix. BG> I'll hopefully be able to take a look at the system this week, BG> and work out the last of the internationalization bugs. Ben, can you do me a favor? While you're at it, can you see if we still need the EncWord.py module? It's still used in HyperArch.py but I suspect the email package provides everything we need already. Thanks, -Barry From che@debian.org Tue Nov 5 00:06:42 2002 From: che@debian.org (Ben Gertzfield) Date: Mon, 04 Nov 2002 16:06:42 -0800 Subject: [Mailman-i18n] how to encode in iso-8859-9 charset In-Reply-To: <001801c2834e$45ef17a0$6501a8c0@coco> References: <001801c2834e$45ef17a0$6501a8c0@coco> <3DC6B577.3030700@debian.org> <003001c2844a$3b8232f0$6501a8c0@coco> <3DC6EF3E.10703@debian.org> <15815.556.7700.354389@gargle.gargle.HOWL> Message-ID: <3DC70B92.6060402@debian.org> Barry A. Warsaw wrote: >Ben, can you do me a favor? While you're at it, can you see if we >still need the EncWord.py module? It's still used in HyperArch.py but >I suspect the email package provides everything we need already. > > From a cursory first glance, it looks like EncWord.decode() is the only method used in HyperArch.py, and we can already do that with email.Header.decode_header(). Ben From loewis@informatik.hu-berlin.de Tue Nov 5 12:04:19 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 05 Nov 2002 13:04:19 +0100 Subject: [Mailman-i18n] Re: encoding on list home page In-Reply-To: <001f01c284c4$215fad10$6501a8c0@coco> References: <001f01c284c4$215fad10$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > other problem with encoding is that.when i make the home page for a > list ,the local 8859-9 characters look bad. as seen below, Do you have this page online, for us to look at? What do you mean by "i make the home page", and where exactly did you put 8859-9 characters into it? Please describe the exact sequence of steps that you did to create the home page, including the text that you put into each field of a web form, and so on. Regards, Martin From loewis@informatik.hu-berlin.de Tue Nov 5 13:30:02 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 05 Nov 2002 14:30:02 +0100 Subject: [Mailman-i18n] Re: encoding on list home page In-Reply-To: <000b01c284cc$7596d810$6501a8c0@coco> References: <001f01c284c4$215fad10$6501a8c0@coco> <000b01c284cc$7596d810$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > you can take a look at the page and the mailing list i'm trying > to make, at this adress, > the home page i mean is fancy html . you can notive the characters > here. when you switch to german, you will notice the change for > the good, on some characters. > > > http://digitiy.com/digitiygroups/listinfo/list1 I'm getting more and more confused. How did you manage to create those pages? Did you edit the templates, e.g. by modifying templates/en/listinfo.html? If not, how did you manage to get the two lines into the page? If you did edit the template pages: It appears that the templates contains the text "ilk liste about, buraya liste bilgileri gelir.?,?,?,?,?," literally. If you want to appear other characters there, why not just modify the template again, and put in the right characters??? Confusedly yours, Martin From loewis@informatik.hu-berlin.de Tue Nov 5 13:42:38 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: Tue, 5 Nov 2002 14:42:38 +0100 (CET) Subject: [Mailman-i18n] Archiving multipart/alternative messages Message-ID: <200211051342.gA5DgclS003471@paros.informatik.hu-berlin.de> It appears that shawn's archiving problems all originate from the processing of multipart/alternative messages in pipermail. For reference, please have a look at http://digitiy.com/posts/list1.mbox/list1.mbox and the corresponding message http://digitiy.com/posts/list1/2002-November/000000.html I would suggest that pipermail looks for a text-plain part in the message, and tries to render that into HTML, ignoring all other parts. Regards, Martin From barry@zope.com Tue Nov 5 13:53:01 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 5 Nov 2002 08:53:01 -0500 Subject: [Mailman-i18n] Re: encoding on list home page References: <001f01c284c4$215fad10$6501a8c0@coco> <000b01c284cc$7596d810$6501a8c0@coco> Message-ID: <15815.52541.228305.135153@gargle.gargle.HOWL> >>>>> "MvL" =3D=3D Martin v L=F6wis wr= ites: MvL> literally. If you want to appear other characters there, why MvL> not just modify the template again, and put in the right MvL> characters??? BTW, if I view that page in Moz1.1 and manually set my browser's charset to iso-8859-9, I get the right characters instead of ?'s that I usually get (since my browser's usually set to us-ascii). -Barry From loewis@informatik.hu-berlin.de Tue Nov 5 14:21:29 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 05 Nov 2002 15:21:29 +0100 Subject: [Mailman-i18n] Re: encoding on list home page In-Reply-To: <15815.52541.228305.135153@gargle.gargle.HOWL> References: <001f01c284c4$215fad10$6501a8c0@coco> <000b01c284cc$7596d810$6501a8c0@coco> <15815.52541.228305.135153@gargle.gargle.HOWL> Message-ID: barry@zope.com (Barry A. Warsaw) writes: > BTW, if I view that page in Moz1.1 and manually set my browser's > charset to iso-8859-9, I get the right characters instead of ?'s that > I usually get (since my browser's usually set to us-ascii). Interesting. This sounds like a Mailman bug/misfeature/misconfiguration. In the HTTP envelope, mailman claims that the page is us-ascii, even though the page itself has a META header claiming otherwise (actually, two of them). It appears that the browser takes the HTTP header for truth, instead of the META http-equiv. It might be useful for Mailman to look for META tags, and omit the Content-type header if there is a META http-equiv in the page. In any case, shawn, for putting Turkish characters on an English Web page, please use HTML character references. Please have a look at http://mail.python.org/mailman/listinfo/playground which displays the characters just fine even on the English page; this is done through character references. If you want to use iso-8859-9 natively on a page, you need to create proper Turkish templates. Regards, Martin From mantas@akl.lt Tue Nov 5 14:25:39 2002 From: mantas@akl.lt (Mantas Kriauciunas) Date: Tue, 5 Nov 2002 16:25:39 +0200 Subject: [Mailman-i18n] Starting a Lithuanian (lt) translation In-Reply-To: <15814.58328.304566.280431@gargle.gargle.HOWL> References: <20021104114936.GA23024@berzas.akl.lt> <15814.58328.304566.280431@gargle.gargle.HOWL> Message-ID: <20021105142539.GA1897@berzas.akl.lt> Hi again, On Mon, Nov 04, 2002 at 04:17:12PM -0500, Barry A. Warsaw wrote: > > Not unless you guys hit stumbling blocks. What "stumbling blocks" ? > > Do you have anything ready? I'd be happy to integrate either > templates or catalogs, even if they're not complete. Looks like > Lithuanian is Latin4, right? No, as I know Lithuanian and Latvian is Latin7 (ISO-8859-13 encoding). Where you find that Lithuanian is Latin4 ? We will traslate some templates tomorrow. When next mailman 2.1 beta will be released ? > > Shall I add you and www.akl.lit to the Mailman I18n champions page? > -Barry what mean "Mailman I18n champions" and where is this page ? Bye, Mantas From loewis@informatik.hu-berlin.de Tue Nov 5 14:45:42 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 05 Nov 2002 15:45:42 +0100 Subject: [Mailman-i18n] Adding non-ASCII headers Message-ID: I just tried to configure the playground list to use non-ASCII headers, and failed. First, I tried to add Turkish letters, without having Turkish templates. This failed, and not surprisingly so: The admin/playground/nondigest form was encoded in us-ascii, so it was not capable of properly transmitting the header contents (it was surprising that Mailman sent out a garbage message, though). Then, I changed the list to Russian, and got a Koi8-r form, in which I successfully entered a Cyrillic text (this text is still configured at the moment). However, when sending a message in non-digest mode, neither a header nor a footer was added by mailman. Can somebody explain this behaviour? Regards, Martin From cerdil@ttnet.net.tr Tue Nov 5 08:39:48 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Tue, 5 Nov 2002 10:39:48 +0200 Subject: [Mailman-i18n] test message for 8859-9 Message-ID: <007b01c284a6$e7557450$6501a8c0@coco> This is a multi-part message in MIME format. ---------------------- multipart/alternative attachment to martin for test purpose- 1- to check if the message header and footer will be visible in = outlook or etc. 2- what will the encoding look like in pipermail archives. - this is message sent from outlook exp with 8859-9 encoding in = mime .in my installation, a non digest subscriber cannot get the = message headers and footers .only sees this message . but a digest customer can see.because the encodings , in the = received message come out different. i think mailman look for the default us-ascii encoding to show the = header and footer. ************************ here we go... Art=FDk, kolay eri=FEilebilir ve do=F0ru bilginin, daha ak=FDll=FD = m=FC=FEteriler ve daha rekabet=E7i bir i=FE ortam=FD yaratt=FD=F0=FD, = =E7a=F0a giriyoruz. Bu yeni jenerasyon d=FCnyada, reklamveren pazarlama = uzmanlar=FD , m=FC=FEterileri ile kesintisiz bir ileti=FEim = sa=F0layacaklar.Bu ileti=FEim, web siteleri, e-mail , b=FCy=FCk web = portallar=FD'ndan, =E7ok k=FDsa bir s=FCrede, televizyonunuza, gsm = telefonunuza, =E7a=F0r=FD cihaz=FDn=FDza , palm tipi PDA cihaz=FDn=FDza = kadar uzanacak. =E7a=F0an Erdil. Digitiy web solutions =20 e-z banner internet media company www.e-zbanner.com www.techifirm.com www.e-zbanner.com/bannerspace *********************** ---------------------- multipart/alternative attachment An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-i18n/attachments/20021105/8d234447/attachment.html ---------------------- multipart/alternative attachment-- From cerdil@ttnet.net.tr Tue Nov 5 08:49:13 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Tue, 5 Nov 2002 10:49:13 +0200 Subject: [Mailman-i18n] how to encode in iso-8859-9 charset References: <200211042256.gA4MuaHm012053@paros.informatik.hu-berlin.de> Message-ID: <007c01c284a8$3bf3a2b0$6501a8c0@coco> Martin, i have sent a test message to the list - these are the problems i encounter in my installation this is a folllow up 1 on your questions. ******** A: The header and footer do not appear in the message sent to each digest subscriber. header and footer i talk about is the message header and footer, that is visible to the subscriber. like this id the ..... list you can subcribe or non... at ... @.com i refer to non visible envelope header as "background". sorry for the confusion. 1- PROBLEMS IN THE OUTLOOK or etc. A-NON DIGEST SUBSCRİBER when i send a post from outlook in 8859-9 encoding, this is what the LIST SUBSCRIBER IN A NON-DIGEST gets. in their outlook. problem: the encoding is good, but there is no header or footer . i mean the message header , that is visible to the recepient. what the background looks like----- ---------------------------------------------- Content-Type: multipart/related; type="multipart/alternative" This is a multi-part message in MIME format. ------=_NextPart_000_002B_01C284B1.4C76FF20 Content-Type: multipart/alternative; boundary="----=_NextPart_001_002C_01C284B1.4C76FF20" ------=_NextPart_001_002C_01C284B1.4C76FF20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------------------ visible to subscriber --------------------------------- E-zbanner web marketing , interaktif ürün ve hizmetleriyle, markalara katma değer yaratan bir internet medyası ajansıdır.E-z banner katma değer zinciri, internette kaliteli web sitelerinden oluşan bir network ve bu altyapıyı oluşturan teknolojisidir. E-zbanner, reklamveren pazarlama uzmanları için ,interaktif pazarlama stratejileri , kampanyaları geliştirir ,markalarının değerini arttırır, ve site yayıncılarına da reklam geliri elde eder. ------------------------------------ B -DIGEST SUBSCRİBER THİS LOOK PERFECT when i send a post from outlook in 8859-9 encoding, this is what the LIST SUBSCRIBER IN A DIGEST gets. in their outlook. Content-Type: text/plain; charset="us-ascii" -- in the background the visible part Header added to every digest (Details for digest_header some ad can be placed here http://adserver.e-zbanner.com/cgi-bin/admonitor.cgi?e-zbannernetwork&gid=56& sid=23&cid=45&mid=136&id=943 E-zbanner web marketing , interaktif ürün ve hizmetleriyle, markalara katma değer yaratan bir internet medyası ajansıdır.E-z banner katma değer zinciri, internette kaliteli web sitelerinden oluşan bir network ve bu altyapıyı oluşturan teknolojisidir. E-zbanner, reklamveren pazarlama uzmanları için ,interaktif pazarlama stratejileri , kampanyaları geliştirir ,markalarının değerini arttırır, ve site yayıncılarına da reklam geliri elde eder. Footer added to every digest (Details for digest_footer) no problems 2- MESSAGE IN PİPERMAIL ****************** same output for the message coming from a digest or non digest subscriber. ----------------------------------------------------------------- This is a multi-part message in MIME format. ---------------------- multipart/related attachment ------=_NextPart_001_002C_01C284B1.4C76FF20 E-zbanner web marketing , interaktif =FCr=FCn ve hizmetleriyle, = markalara katma deger yaratan bir internet medyasi ajansidir.E-z banner = katma deger zinciri, internette kaliteli web sitelerinden olusan bir = network ve bu altyapiyi olusturan teknolojisidir. E-zbanner, reklamveren = pazarlama uzmanlari i=E7in ,interaktif pazarlama stratejileri , = kampanyalari gelistirir ,markalarinin degerini arttirir, ve site = ********************************************* OKAY, THE HEADER & FOOTER IS STRİPPED- THE PROBLEM IN ARCHIVES İS *ONLY ENCODING* *********************message ends. ----- Original Message ----- From: "Martin von Loewis" To: "shawn Erdil" Sent: Tuesday, November 05, 2002 12:56 AM Subject: Re: [Mailman-i18n] how to encode in iso-8859-9 charset > shawn, > > I still don't understand your problem. It seems we have difficulties > to communicate, so please don't get annoyed by my lengthy questions. > > > > --------------------------------------- > > This is a multi-part message in MIME format. > > > > ---------------------- multipart/alternative attachment > > Merakla beklenen bir se=E7im yasadik. Merakla beklenmesinin sebebi yeni > > y=FCzlerin olmasi ve muhtesem d=F6rtl=FC olarak tanimlanan malum = > > siyaset=E7i > > dedelerimizin bir kisminin siyaset sahnesinden tasfiye olmus olmalari > > -------------------------------------------------------------------------- -- > > ------------------------------------------ > > Where does this text come from? Is that some you have entered yourself (if so, > where?), is this a header or footer? Who has created the multipart/alternative > attachment? Can you perhaps send us the original message, ideally in a uuencoded > form? > > > This is the output i get in the pipermail archives, when i post a > > message, from outlook express with 8859-9 encoding, as you have > > mentioned , no problem in the return emails to an email client, such as > > outlook express, or etc.the encoding is OKAY, but , the header and > > footer don't show up > > Which of the following two is the case: > A: The header and footer do not appear in the message sent to each subscriber. > B: The header and footer do not appear in the pipermail archives. > > If you have observed B, then this is correct behaviour: the header and footer > is omitted from the pipermail archive on purpose. > > >, i think since the message, is in a different > > charset than us-ascii- the footer and header don't show up.i just > > get the message, i have sent to the list, NOTHING ELSE. > > the encoding , in the received email header shows as: Content-Type: > > multipart/alternative; > > Again, I don't understand: First you say that you do not see the header. > Then you say that the header is transmitted as multipart/alternative. > Which of these is the case? > > > _f i send the message as plain text, it comes out- okay with the > > header and footer included. > > but you know than i can't show the _,_,_ etc. > > I can't quote them right now (as elm does not support -9), but please > have a look at > > http://mail.python.org/pipermail/mailman-i18n/2002-November/000708.html > > This message was correctly archived, as far as I can tell. Do you agree? > > > the header and footer are important for me, since i want to put some > > adserver tags, in text format. > > Ok, it seems that your problem is somehow with the header and footer. > Can you please post the text that you want to use as the header and footer? > Don't hesitate to have this encoded as plain text in iso-8859-9: some > of our mail readers will support this well, as will the archive. > > > ARCHIVES: > > > > in the archives - as you can see above, it shows quoted,and funky > > characters ,when the message is in mime format. > > when it is sent in plain text, it comes out okay. > > Unfortunately, I cannot see this from above. Are you saying you have copied > this text from a archive web page? > > > 1- how to show the header and footer ,in outlook ? when sending with > > 8859-9 mime from outlook?,when in non -digest mode > > Can you please send a message that you consider "8859-9" to this list? > > It seems to me that this message (i.e. the one I'm responding to) was a MIME > message, and it was encoded as iso-8859-9. So you must be talking about > something else. > > > 2- how to make it look formatted-presentable in the pipermail > > archives?when sending with mime 8859-9. > > AFAICT, this works fine: no additional configuration needed. > > > 1-should i try to put [iso-8859-9] in the mm-cfg.py to change > > defaults? > > I don't think you should change anything. First, we need to understand what > you do before we can tell you what to change. > > Regards, > Martin > From cerdil@ttnet.net.tr Tue Nov 5 12:08:59 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Tue, 5 Nov 2002 14:08:59 +0200 Subject: [Mailman-i18n] encoding on list home page Message-ID: <001f01c284c4$215fad10$6501a8c0@coco> This is a multi-part message in MIME format. ---------------------- multipart/related attachment ------=_NextPart_001_001C_01C284D4.E3644E10 hello , Martin and Ben, i' ve sent a test message to the list i18n - 4 hours ago, but = its not in the list yet.probably your cron intervals. anyway, it will be there eventually. other problem with encoding is that.when i make the home page = for a list ,the local 8859-9 characters look bad. as seen = below,=20 but when i see that page in german, since they have some of = our characters, some letters look okay, in german=20 v,|,g,p,}, english =F6,=FC,=E7,?,y, - german Bu bir reklamd}r-text olarak kullan}l}r=20 i'm sure when we make the tempate , for the iso-8859-9 charset, = they will look okay. shawn Erdil. e-z banner internet media company Techifirm Retail solutions www.e-zbanner.com www.techifirm.com www.e-zbanner.com/bannerspace =20 Address:=C7evre sitesi 15- D/9 Akatlar,Istanbul- Turkey 80630 -------------------------------------------------------- ------=_NextPart_001_001C_01C284D4.E3644E10 An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-i18n/attachments/20021105/00f83ff6/attachment.html ------=_NextPart_001_001C_01C284D4.E3644E10-- ---------------------- multipart/related attachment A non-text attachment was scrubbed... Name: not available Type: application/octet-stream Size: 69 bytes Desc: not available Url : http://mail.python.org/pipermail/mailman-i18n/attachments/20021105/00f83ff6/attachment.exe ---------------------- multipart/related attachment-- From cerdil@ttnet.net.tr Tue Nov 5 13:08:36 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Tue, 5 Nov 2002 15:08:36 +0200 Subject: [Mailman-i18n] Re: encoding on list home page References: <001f01c284c4$215fad10$6501a8c0@coco> Message-ID: <000b01c284cc$7596d810$6501a8c0@coco> Martin, you can take a look at the page and the mailing list i'm trying to make, at this adress, the home page i mean is fancy html . you can notive the characters here. when you switch to german, you will notice the change for the good, on some characters. http://digitiy.com/digitiygroups/listinfo/list1 thank you, shawn Erdil. e-z banner internet media company Techifirm Retail solutions www.e-zbanner.com www.techifirm.com www.e-zbanner.com/bannerspace Address:Çevre sitesi 15- D/9 Akatlar,Istanbul- Turkey 80630 -------------------------------------------------------- ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: ; "Ben Gertzfield" Sent: Tuesday, November 05, 2002 2:04 PM Subject: Re: encoding on list home page > "shawn Erdil" writes: > > > other problem with encoding is that.when i make the home page for a > > list ,the local 8859-9 characters look bad. as seen below, > > Do you have this page online, for us to look at? > > What do you mean by "i make the home page", and where exactly did you > put 8859-9 characters into it? Please describe the exact sequence of > steps that you did to create the home page, including the text that > you put into each field of a web form, and so on. > > Regards, > Martin From barry@python.org Tue Nov 5 16:04:30 2002 From: barry@python.org (Barry A. Warsaw) Date: Tue, 5 Nov 2002 11:04:30 -0500 Subject: [Mailman-i18n] Starting a Lithuanian (lt) translation References: <20021104114936.GA23024@berzas.akl.lt> <15814.58328.304566.280431@gargle.gargle.HOWL> <20021105142539.GA1897@berzas.akl.lt> Message-ID: <15815.60430.809412.726107@gargle.gargle.HOWL> >>>>> "MK" == Mantas Kriauciunas writes: >> Not unless you guys hit stumbling blocks. MK> What "stumbling blocks" ? I don't know. :) Just let us know if you have any problems. >> Do you have anything ready? I'd be happy to integrate either >> templates or catalogs, even if they're not complete. Looks >> like Lithuanian is Latin4, right? MK> No, as I know Lithuanian and Latvian is Latin7 (ISO-8859-13 MK> encoding). Where you find that Lithuanian is Latin4 ? http://czyborra.com/charsets/iso8859.html#ISO-8859-4 MK> We will traslate some templates tomorrow. When next mailman MK> 2.1 beta will be released ? Within a few days. Likely Friday. >> Shall I add you and www.akl.lit to the Mailman I18n champions >> page? -Barry MK> what mean "Mailman I18n champions" and where is this page ? A language champion is just my term for the leader of a particular translation effort. See http://list.org/MM21/i18n.html I'd like to add an entry for Lithuanian. -Barry From loewis@informatik.hu-berlin.de Tue Nov 5 17:44:41 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 05 Nov 2002 18:44:41 +0100 Subject: [Mailman-i18n] Starting a Lithuanian (lt) translation In-Reply-To: <15815.60430.809412.726107@gargle.gargle.HOWL> References: <20021104114936.GA23024@berzas.akl.lt> <15814.58328.304566.280431@gargle.gargle.HOWL> <20021105142539.GA1897@berzas.akl.lt> <15815.60430.809412.726107@gargle.gargle.HOWL> Message-ID: barry@python.org (Barry A. Warsaw) writes: > MK> What "stumbling blocks" ? > > I don't know. :) Just let us know if you have any problems. I think this really was an English-language question: A "stumbling block" is a hindrance (impediment, barrier) that stops you from making progress. So if all works out just fine, you should not need additional information. Regards, Martin From loewis@informatik.hu-berlin.de Tue Nov 5 18:03:03 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 05 Nov 2002 19:03:03 +0100 Subject: [Mailman-i18n] Pipermail and non-English lists Message-ID: It appears that pipermail does not work will with the message catalogs. Please have a look at http://mail.python.org/pipermail/playground/ This HTML page is formatted as KOI-8R, but that encoding is nowhere declared. More disturbingly, http://mail.python.org/pipermail/playground/2002-November/000018.html 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 necessary). Which one would you prefer? Regards, Martin From cerdil@ttnet.net.tr Tue Nov 5 19:18:33 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Tue, 5 Nov 2002 21:18:33 +0200 Subject: [Mailman-i18n] progress on 8859-9 charset? References: <007f01c284e9$8e3ddae0$6501a8c0@coco> Message-ID: <018d01c28500$22eb10c0$6501a8c0@coco> Martin, Thank you for your messages? since i'm in & out of the office i can't reply quickly. you said, A- ******************** If you want to use iso-8859-9 natively on a page, you need to create proper Turkish templates. ********************** do you mean, that the pipermail page, should have the in the header. is this what you mean by templates? B- did we get any progress, can i provide any help, in helping you guys diagnose ,some internalization problems ? C- in my second subscription -the messages i get as a non -digest subscriber - "FROM I18N " were also with no message headers. my first subscription as a DIGEST customer, gets the message headers and footers with no problem. **any progress on the message headers, in DIGEST versus NON DIGEST customers?** D- http://mail.python.org/pipermail/playground/ the messages in this pipermail archive were all turkish charset compatible. RESULT: are you , making some changes for the in your next version?could we expect, a progress? is there anything, you advise me to change ? just a note: *************** Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by e-zbanner.com id gA5Ej5q02314 this is what yahoogroups send , to their digest subscriber. ***************** thank you, shawn erdil ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Sent: Tuesday, November 05, 2002 7:49 PM Subject: Re: [Playground] Sending a KOI8-R message > "shawn Erdil" writes: > > > it is this with korean encoding > > > > Content-Type: text/plain; charset=utf-8 > > UTF-8 is not a korean encoding :-) Instead, it is an encoding that > works for all languages: Turkish, German, Russian, Korean. > > I thought Emacs would send this as koi8-r, but it picked UTF-8 instead > :-( > > Regards, > Martin > From loewis@informatik.hu-berlin.de Tue Nov 5 19:42:17 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 05 Nov 2002 20:42:17 +0100 Subject: [Mailman-i18n] Re: progress on 8859-9 charset? In-Reply-To: <018d01c28500$22eb10c0$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > ******************** > If you want to use iso-8859-9 natively on a page, you need to create > proper Turkish templates. > ********************** > do you mean, that the pipermail page, should have the > > in the header. > is this what you mean by templates? Not at all. You need to create a directory templates/tr, copying all the pages from templates/en. Then you need to add a line add_language('tr', _('Turkish'), 'iso-8859-9') to Mailman/Defaults.py. Then you need to select Turkish as the default language in your mailing list. > B- > did we get any progress, can i provide any help, in helping you > guys diagnose ,some internalization problems ? The steps above should solve most of your problems. It should allow: - to use iso-8859-9 in all Web pages, and - to use Turkish characters in headers and footers. > in my second subscription -the messages i get as a non -digest > subscriber - "FROM I18N " were also with no message headers. > my first subscription as a DIGEST customer, gets the message > headers and footers with no problem. > **any progress on the message headers, in DIGEST versus NON DIGEST > customers?** Yes. With Turkish templates, the headers should work fine. > are you , making some changes for the in your next version?could we > expect, a progress? Not for the next version, no. Regards, Martin From cerdil@ttnet.net.tr Tue Nov 5 19:55:04 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Tue, 5 Nov 2002 21:55:04 +0200 Subject: [Mailman-i18n] Re: progress on 8859-9 charset? References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco> Message-ID: <008e01c28505$3ce77e50$6501a8c0@coco> Thanks chief, i'll folloow right on :)) thank you, shawn erdil ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: "Ben Gertzfield" ; Sent: Tuesday, November 05, 2002 9:42 PM Subject: Re: progress on 8859-9 charset? > "shawn Erdil" writes: > > > ******************** > > If you want to use iso-8859-9 natively on a page, you need to create > > proper Turkish templates. > > ********************** > > do you mean, that the pipermail page, should have the > > > > in the header. > > is this what you mean by templates? > > Not at all. You need to create a directory templates/tr, copying all the pages > from templates/en. Then you need to add a line > > add_language('tr', _('Turkish'), 'iso-8859-9') > > to Mailman/Defaults.py. Then you need to select Turkish as the default language > in your mailing list. > > > B- > > did we get any progress, can i provide any help, in helping you > > guys diagnose ,some internalization problems ? > > The steps above should solve most of your problems. It should allow: > - to use iso-8859-9 in all Web pages, and > - to use Turkish characters in headers and footers. > > > in my second subscription -the messages i get as a non -digest > > subscriber - "FROM I18N " were also with no message headers. > > my first subscription as a DIGEST customer, gets the message > > headers and footers with no problem. > > **any progress on the message headers, in DIGEST versus NON DIGEST > > customers?** > > Yes. With Turkish templates, the headers should work fine. > > > are you , making some changes for the in your next version?could we > > expect, a progress? > > Not for the next version, no. > > Regards, > Martin From cerdil@ttnet.net.tr Tue Nov 5 20:48:33 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Tue, 5 Nov 2002 22:48:33 +0200 Subject: [Mailman-i18n] error on tr language References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco> Message-ID: <000701c2850c$b5f5c5c0$6501a8c0@coco> martin , i have tried this before also, what do you think i am missing ? to get this error? Traceback: Traceback (most recent call last): File "/usr/local/digitiygroups/scripts/driver", line 63, in run_main from Mailman.Logging.StampedLogger import StampedLogger File "/usr/local/digitiygroups/Mailman/Logging/StampedLogger.py", line 20, in ? from Mailman.Logging.Logger import Logger File "/usr/local/digitiygroups/Mailman/Logging/Logger.py", line 24, in ? from Mailman import mm_cfg File "/usr/local/digitiygroups/Mailman/mm_cfg.py", line 52, in ? add_language('tr', _('Turkish'), 'iso-8859-9') NameError: name '_' is not defined -------------------- what have i done? 1-copied the eng directory and renamed to tr 2- add_language('tr', _('Turkish'), 'iso-8859-9') in mm_cfg.py nodirectly to defaults.py thank you shawn erdil ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: "Ben Gertzfield" ; Sent: Tuesday, November 05, 2002 9:42 PM Subject: Re: progress on 8859-9 charset? > "shawn Erdil" writes: > > > ******************** > > If you want to use iso-8859-9 natively on a page, you need to create > > proper Turkish templates. > > ********************** > > do you mean, that the pipermail page, should have the > > > > in the header. > > is this what you mean by templates? > > Not at all. You need to create a directory templates/tr, copying all the pages > from templates/en. Then you need to add a line > > add_language('tr', _('Turkish'), 'iso-8859-9') > > to Mailman/Defaults.py. Then you need to select Turkish as the default language > in your mailing list. > > > B- > > did we get any progress, can i provide any help, in helping you > > guys diagnose ,some internalization problems ? > > The steps above should solve most of your problems. It should allow: > - to use iso-8859-9 in all Web pages, and > - to use Turkish characters in headers and footers. > > > in my second subscription -the messages i get as a non -digest > > subscriber - "FROM I18N " were also with no message headers. > > my first subscription as a DIGEST customer, gets the message > > headers and footers with no problem. > > **any progress on the message headers, in DIGEST versus NON DIGEST > > customers?** > > Yes. With Turkish templates, the headers should work fine. > > > are you , making some changes for the in your next version?could we > > expect, a progress? > > Not for the next version, no. > > Regards, > Martin From danny@terweij.nl Tue Nov 5 20:52:00 2002 From: danny@terweij.nl (Danny Terweij) Date: Tue, 5 Nov 2002 21:52:00 +0100 Subject: [Mailman-i18n] error on tr language References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> Message-ID: <004801c2850d$30323120$1e00a8c0@onsnet.org> From: "shawn Erdil" > i have tried this before also, what do you think i am missing ? > to get this error? > Traceback: > what have i done? > 1-copied the eng directory and renamed to tr > 2- add_language('tr', _('Turkish'), 'iso-8859-9') > > in mm_cfg.py nodirectly to defaults.py Just do it at the Defaults.py then it works. I did have the same error when i did this a long time ago :) Danny. From cerdil@ttnet.net.tr Tue Nov 5 21:44:32 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Tue, 5 Nov 2002 23:44:32 +0200 Subject: [Mailman-i18n] error on tr language-new problem References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> Message-ID: <005201c28514$88254820$6501a8c0@coco> Danny, thank you for the hint, it works now,like a charm!! the encoding also looks good. Martin, PROBLEM: now the default lang is Turkish, but the mail does not get sent, now. when i switch back into eng , the mail gets sent. any idea on what it could be ? thank you shawn erdil. Cc: Sent: Tuesday, November 05, 2002 10:52 PM ----- Original Message ----- From: "Danny Terweij" To: "shawn Erdil" ; "Martin v. Löwis" Subject: Re: [Mailman-i18n] error on tr language > From: "shawn Erdil" > > > i have tried this before also, what do you think i am missing ? > > to get this error? > > Traceback: > > what have i done? > > 1-copied the eng directory and renamed to tr > > 2- add_language('tr', _('Turkish'), 'iso-8859-9') > > > > in mm_cfg.py nodirectly to defaults.py > > Just do it at the Defaults.py then it works. > > I did have the same error when i did this a long time ago :) > > Danny. > > From loewis@informatik.hu-berlin.de Tue Nov 5 22:27:42 2002 From: loewis@informatik.hu-berlin.de (Martin von Loewis) Date: Tue, 5 Nov 2002 23:27:42 +0100 (CET) Subject: [Mailman-i18n] Multipart/alternative in pipermail Message-ID: <200211052227.gA5MRgqm003989@paros.informatik.hu-berlin.de> I have created a patch to fix the multipart/alternative problem, see http://sourceforge.net/tracker/index.php?func=detail&aid=634109&group_id=103&atid=300103 With that patch, text parts of multipart messages are now properly MIME-decoded. Reprocessing shawn's mailbox with that patch shows that all messages get archived properly. Regards, Martin From loewis@informatik.hu-berlin.de Wed Nov 6 08:32:42 2002 From: loewis@informatik.hu-berlin.de (Martin von Loewis) Date: Wed, 6 Nov 2002 09:32:42 +0100 (CET) Subject: [Mailman-i18n] Recode pipermail templates Message-ID: <200211060832.gA68WgRE008907@paros.informatik.hu-berlin.de> I made a patch http://sourceforge.net/tracker/index.php?func=detail&aid=634303&group_id=103&atid=300103 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. HTH, Martin From loewis@informatik.hu-berlin.de Wed Nov 6 09:57:40 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 06 Nov 2002 10:57:40 +0100 Subject: [Mailman-i18n] error on tr language-new problem In-Reply-To: <005201c28514$88254820$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > now the default lang is Turkish, but the mail does not get sent, > now. > > when i switch back into eng , the mail gets sent. > > any idea on what it could be ? Sorry, I have no idea. Can you check all relevant log files? Regards, Martin From rcm@sasaska.net Tue Nov 5 15:19:18 2002 From: rcm@sasaska.net (Rafael Cordones Marcos) Date: Tue, 5 Nov 2002 16:19:18 +0100 (CET) Subject: [Mailman-i18n] Translation in E-mail Message-ID: <4529.213.100.45.224.1036509558.squirrel@sasaska.net> Hi folks, I have been searching the Mailman website and have not found any reference to what I am looking for, i.e. translating e-mail. I am not talking about translating the Mailman software or documentation (i18n) but translating the e-mails that people send to the mailing list. I am looking for the following functionality in a mailing list software: - As an administrator: - set up some default machine translation (MT) engine. For example, I want to use Babelfish for translating between English and Spanish but I wat to use some other engine for translating between German and Swedish. - specify the subject of the mailing list and thus improving the translation results. For instance, I can specify that the mailing list is about "Technical -> Operating Systems -> Minix" (just kidding). - As a user: - I want to subscribe to the mailing list and specify my language (natural) language preferences. Say I want specify {Catalan, Spanish, German}. - e-mail going to the list gets sent to a machine translation before it gets sent to me. I can optionaly say to the mailing list software that I want to receive also the original message. - If I do not like the translation of an e-mail I can choose some other machine translation engine. I may decide that some other translation engine does a better job or even pay to get get better translations. Maybe the administrator forgot to specify a machine translation engine for Euskera<->Farsi and I know of one that just started operating. I would appreciate any information you may have on this topic. Maybe somebody has started implementing this in Mailman or is already implemented? Send me any comments, problems you see on the aforementioned working schema, flames, ... Thanks a lot for your time! Rafa -- Link of the week: Der flexible Mensch. Robert Kurtz. [es] http://www.rebelion.org/economia/rkurz011002.htm [de] http://www.krisis.org/r-kurz_flexible-mensch_folha.html [en] If you find it, tell me! From loewis@informatik.hu-berlin.de Wed Nov 6 14:15:17 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 06 Nov 2002 15:15:17 +0100 Subject: [Mailman-i18n] Re: new error on the 8859-9 charset In-Reply-To: <000a01c2859d$ad5a9670$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > return mm_cfg.LC_DESCRIPTIONS[lang][1] > KeyError: tr I see. Can you please report the exact changes that you made to Defaults.py, and to mm_cfg.py? Regards, Martin From cerdil@ttnet.net.tr Wed Nov 6 14:06:16 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Wed, 6 Nov 2002 16:06:16 +0200 Subject: [Mailman-i18n] new error on the 8859-9 charset References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco> Message-ID: <000a01c2859d$ad5a9670$6501a8c0@coco> Martin, ERROR LOG OUTPUT i get this error, wheh the list is in "tr" 8859-9 the mail doesn't get sent at all, if i switch to eng no problem all is fine. ----------------------------------------------------- bythe way ---thanks, the charset problem is history on the messages. i 'll install your patch for the archives. Nov 06 15:24:43 2002 (791) Uncaught runner exception: tr Nov 06 15:24:43 2002 (791) Traceback (most recent call last): File "/usr/local/digitiygroups/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/digitiygroups/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/digitiygroups/Mailman/Queue/IncomingRunner.py", line 129, in _dispose status = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/digitiygroups/Mailman/Queue/IncomingRunner.py", line 152, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/digitiygroups/Mailman/Handlers/CookHeaders.py", line 57, in process prefix_subject(mlist, msg, msgdata) File "/usr/local/digitiygroups/Mailman/Handlers/CookHeaders.py", line 215, in prefix_subject charset = Utils.GetCharSet(mlist.preferred_language) File "/usr/local/digitiygroups/Mailman/Utils.py", line 606, in GetCharSet return mm_cfg.LC_DESCRIPTIONS[lang][1] KeyError: tr ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: "Danny Terweij" ; Sent: Wednesday, November 06, 2002 11:57 AM Subject: Re: [Mailman-i18n] error on tr language-new problem > "shawn Erdil" writes: > > > now the default lang is Turkish, but the mail does not get sent, > > now. > > > > when i switch back into eng , the mail gets sent. > > > > any idea on what it could be ? > > Sorry, I have no idea. Can you check all relevant log files? > > Regards, > Martin From cerdil@ttnet.net.tr Wed Nov 6 15:55:50 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Wed, 6 Nov 2002 17:55:50 +0200 Subject: [Mailman-i18n] Re: new error on the 8859-9 charset References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco> Message-ID: <004701c285ac$fd129dc0$6501a8c0@coco> mm.config.py OWNERS_CAN_DELETE_THEIR_OWN_LISTS = 1 PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/posts/%(listname)s' WEB_HEADER_COLOR = '#coceee' # Major section headers WEB_SUBHEADER_COLOR = '#efefef' # Minor section headers #add_language('tr', _('Turkish'), 'iso-8859-9') DEFAULT_SERVER_LANGUAGE = 'en' IMAGE_LOGOS = 'http://www.digitiy.com/icons/' #DEFAULT_CHARSET = 'iso-8859-1' #VERBATIM_ENCODING = ['iso-8859-1'] -------------------------------------------------------- defaults.py ........ ........ add_language('pt_BR', _('Portuguese (Brazil)'), 'iso-8859-1') add_language('ru', _('Russian'), 'koi8-r') add_language('sv', _('Swedish'), 'iso-8859-1') add_language('tr', _('Turkish'), 'iso-8859-9') ------------------------------------ since adding the new language line to to mm.config.py has resulted in error, like this one, i have added the tr lang line directly on the defaults.py and it has worked fine, till sending a message . thank you . shawn ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: Sent: Wednesday, November 06, 2002 4:15 PM Subject: Re: new error on the 8859-9 charset > "shawn Erdil" writes: > > > return mm_cfg.LC_DESCRIPTIONS[lang][1] > > KeyError: tr > > I see. Can you please report the exact changes that you made to > Defaults.py, and to mm_cfg.py? > > Regards, > Martin From cerdil@ttnet.net.tr Thu Nov 7 10:41:37 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Thu, 7 Nov 2002 12:41:37 +0200 Subject: [Mailman-i18n] Re: new error on the 8859-9 charset References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco> Message-ID: <005601c2864a$40b76d60$6501a8c0@coco> Martin, were you able to pinpoint the problem on, when i change the default list lang to "tr" , the mails were not getting sent. or is there anything ,on my mm config.py that is mis-configured your efforts are appreciated! thank you. shawn erdil ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: Sent: Wednesday, November 06, 2002 4:15 PM Subject: [Mailman-i18n] Re: new error on the 8859-9 charset > "shawn Erdil" writes: > > > return mm_cfg.LC_DESCRIPTIONS[lang][1] > > KeyError: tr > > I see. Can you please report the exact changes that you made to > Defaults.py, and to mm_cfg.py? > > Regards, > Martin > > _______________________________________________ > Mailman-i18n mailing list > Mailman-i18n@python.org > http://mail.python.org/mailman/listinfo/mailman-i18n > From loewis@informatik.hu-berlin.de Thu Nov 7 10:35:51 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 07 Nov 2002 11:35:51 +0100 Subject: [Mailman-i18n] Re: new error on the 8859-9 charset In-Reply-To: <005601c2864a$40b76d60$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > when i change the default list lang to "tr" , the mails were not > getting sent. > or is there anything ,on my mm config.py that is mis-configured No. I haven't researched that further, and I won't be able to do that in the coming days. Regards, Martin From cerdil@ttnet.net.tr Fri Nov 8 09:40:40 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Fri, 8 Nov 2002 11:40:40 +0200 Subject: [Mailman-i18n] the way i added my language charset References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco> Message-ID: <001101c2870a$e6a263e0$6501a8c0@coco> Martin, FIXED 1-since i couldn't get to add a new language from the mmconfig.py , i have just replaced the dutch template, that was in the system with Turkish. add_language('nl', _('Turkish'), 'iso-8859-9') it works as turkish with the nl symbol everything is fine now- no more errors are reported. let's see how it goes. i'll start the translation. PROBLEM 2- could we fix the archive problem with your patches ? PROBLEM 3-after the patches, could i show the message headers and footers in the NON-DIGEST emails. that s all:)) thank you. shawn erdil www.e-zbanner.com ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: Sent: Thursday, November 07, 2002 12:35 PM Subject: Re: [Mailman-i18n] Re: new error on the 8859-9 charset > "shawn Erdil" writes: > > > when i change the default list lang to "tr" , the mails were not > > getting sent. > > or is there anything ,on my mm config.py that is mis-configured > > No. I haven't researched that further, and I won't be able to do that > in the coming days. > > Regards, > Martin > > > _______________________________________________ > Mailman-i18n mailing list > Mailman-i18n@python.org > http://mail.python.org/mailman/listinfo/mailman-i18n > From loewis@informatik.hu-berlin.de Fri Nov 8 11:55:25 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 08 Nov 2002 12:55:25 +0100 Subject: [Mailman-i18n] Re: the way i added my language charset In-Reply-To: <001101c2870a$e6a263e0$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > PROBLEM > 2- could we fix the archive problem with your patches ? I cannot understand this question. Who is "we"? My patches fix the problems, yes. > 3-after the patches, could i show the message headers and footers in > the NON-DIGEST emails. Now that you've added the language to mailman, is there any problem remaining here? Regards, Martin From cerdil@ttnet.net.tr Fri Nov 8 12:38:34 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Fri, 8 Nov 2002 14:38:34 +0200 Subject: [Mailman-i18n] Re: the way i added my language charset References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco><001101c2870a$e6a263e0$6501a8c0@coco> Message-ID: <005501c28723$c1501010$6501a8c0@coco> ok, thank you for me just one problem remaining, there are two examples below that can explain my problem 3- i can't get the message headers and footers in NON DIGEST sends, when they arrive in outlook. ****************************** example: THIS IS NORMAL -DIGEST MODE with message headers and footers Send Python-list mailing list submissions to python-list@python.org To subscribe or unsubscribe via the World Wide Web, visit http://mail.python.org/mailman/listinfo/python-list or, via email, send a message with subject or body 'help' to python-list-request@python.org You can reach the person managing the list at python-list-admin@python.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Python-list digest..." ---------------------------------------------------------------------------- ---- Today's Topics: 1. Virtual Filesystem (was: Adding ftputil to the Python distribution?) (Stephan Diehl) 2. Re: re.sub() bug? (holger krekel) 3. Re: string.strip (Duncan Booth) 4. Re: RecordSet (ADO) with stored procs (Syver Enstad) 5. Re: Python Browser Applets (Richie Hindle) 6. Re: A vision for Parrot (Slaven Rezic) 7. Re: string.strip (Gerhard =?iso-8859-1?Q?H=E4ring?=) 8. Re: A vision for Parrot (Benjamin Goldberg) 9. Newbie-list-problem: how to supress constraining 2 lists - a=b ? (HugOnline) 10. Re: string.strip (Duncan Booth) 11. Re: Newbie-list-problem: how to supress constraining 2 lists - a=b ? (JohnJacob) 12. RE: string.strip (Simon Brunning) 13. Point an MS Access / VB developer in the right direction... (Dan) 14. stripping HTML comments in the face of programmer errors (Skip Montanaro) ---------------------------------------------------------------------------- ---- -- http://mail.python.org/mailman/listinfo/python-list **************************************************************************** ********************** this is in NON DIGEST MODE - no headers nor footers sizcede!!İmam Hatipli birinin genel başkan olması ve o idoliji'ye sahip > >olarak meclisde yer edinmeye çalışması içler acısı bir durum.Kendisi > >yıllarca İslam partisiyiz diye söyleyipduruyordu şimdi birden bire > >Muhafezekar Demokrat parti olup çıktılar.Ben türk halkının bu kadar dinci > >bir kesime oy verebileceğini düşünmüyorum,bu AKP nin iktidarı tek başına > >almasının nedeni halkın çıldırma noktasında olması ve hadi bakalım bu > >partiyi bir başa getirelimde ne olacağını görelim davasından başka bir **************************************************************************** ********** thats all when tey will normalize afetr the patch. thank you, shawn erdil ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: Sent: Friday, November 08, 2002 1:55 PM Subject: Re: the way i added my language charset > "shawn Erdil" writes: > > > PROBLEM > > 2- could we fix the archive problem with your patches ? > > I cannot understand this question. Who is "we"? My patches fix the > problems, yes. > > > 3-after the patches, could i show the message headers and footers in > > the NON-DIGEST emails. > > Now that you've added the language to mailman, is there any problem > remaining here? > > Regards, > Martin From loewis@informatik.hu-berlin.de Fri Nov 8 12:53:54 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 08 Nov 2002 13:53:54 +0100 Subject: [Mailman-i18n] Re: the way i added my language charset In-Reply-To: <005501c28723$c1501010$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> <005501c28723$c1501010$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > i can't get the message headers and footers in NON DIGEST sends, when > they arrive in outlook. Did you get them on the Playground list? I got them just fine, there, so I don't understand why you are having problems. Did you enter headers and footers in the mailman configuration? Notice that header is NOT added to NON DIGEST send if the MESSAGE is a MIME multipart message. This is by design. So just don't send multipart messages if you want mailman to add headers and footers. Regards, Martin From cerdil@ttnet.net.tr Fri Nov 8 18:35:34 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Fri, 8 Nov 2002 20:35:34 +0200 Subject: [Mailman-i18n] Re: the way i added my language charset References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco><001101c2870a$e6a263e0$6501a8c0@coco><005501c28723$c1501010$6501a8c0@coco> Message-ID: <010601c28755$a0267500$6501a8c0@coco> Martin, thanks you for your reply, >Notice that header is NOT added to NON DIGEST send if the MESSAGE is a > MIME multipart message. This is by design. So just don't send > multipart messages if you want mailman to add headers and footers. it this is by design, than there is nothing we can do if i send it as PLAIN message -- i get the headers and footers like below how can i control not to send -mime multipart alternative message ? everybody have their presets. may be it has to be converted somewhere. from multipart to text-plain. because all the non digest messages i get from yahoo groups are all plain/text encoded ****************************************** Buraya reklam verebilirsiniz? http://adserver.e-zbanner.com/cgi-bin/admonitor.cgi?e-zbannernetwork&gid=56& sid=23&cid=45&mid=136&id=943 _______________________________________________ List1 mailing list List1@digitiy.com http://digitiy.com/digitiygroups/listinfo/list1 Sesini her duydugumda Hissettigim acisini kalp atislarimda. Çok oldu terk ettiler Iyi ki de gittiler bizi anlayip, Bir kalabaligi sevmiyorum Bir de yalnizligi zaten bilirsin. Bu aralar tek mutlulugum Yanaginda güller açan o kadin. Bak bu da ikinci duble; ************************************************ thank you for your time shawn erdil ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: Sent: Friday, November 08, 2002 2:53 PM Subject: Re: the way i added my language charset > "shawn Erdil" writes: > > > i can't get the message headers and footers in NON DIGEST sends, when > > they arrive in outlook. > > Did you get them on the Playground list? I got them just fine, there, > so I don't understand why you are having problems. Did you enter > headers and footers in the mailman configuration? > > Notice that header is NOT added to NON DIGEST send if the MESSAGE is a > MIME multipart message. This is by design. So just don't send > multipart messages if you want mailman to add headers and footers. > > Regards, > Martin From cerdil@ttnet.net.tr Sat Nov 9 10:42:34 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Sat, 9 Nov 2002 12:42:34 +0200 Subject: [Mailman-i18n] the internationalization patches References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco><001101c2870a$e6a263e0$6501a8c0@coco><005501c28723$c1501010$6501a8c0@coco> Message-ID: <004701c287dc$b7320a20$6501a8c0@coco> i applied the latest patches to i18n.py and scrubber.py but in HyperachArch.py 3 out of 24 hunks FAILED -- i get these rejections , in HyperArch.py , as the result of the HyperArch.py patch. instead of the patch, would the latest CVS version make the necessary changes? *i have replaced the latest cvs version already. ******My only problem at the moment is to strip the html,mime multipart alternative content & convert to plain text for archiving, but i am not succesfull at doing it. thank you, shawn erdil e-zbanner.com *************** *** 162,168 **** # strings. Keys are (templatefile, lang) tuples. _templatecache = {} - def quick_maketext(templatefile, dict=None, raw=0, lang=None, mlist=None): if lang is None: lang = mlist.preferred_language template = _templatecache.get((templatefile, lang)) --- 178,185 ---- # strings. Keys are (templatefile, lang) tuples. _templatecache = {} + def quick_maketext(templatefile, dict=None, raw=0, + lang=None, mlist=None, charset = None): if lang is None: lang = mlist.preferred_language template = _templatecache.get((templatefile, lang)) *************** *** 170,175 **** # Use the basic maketext, with defaults to get the raw template template = Utils.maketext(templatefile, lang=lang, raw=1) _templatecache[(templatefile, lang)] = template # Copied from Utils.maketext() text = template if dict is not None: --- 187,210 ---- # Use the basic maketext, with defaults to get the raw template template = Utils.maketext(templatefile, lang=lang, raw=1) _templatecache[(templatefile, lang)] = template + tcharset = Utils.GetCharSet(lang) + if charset and tcharset != charset and tcharset != 'us-ascii': + # Need to recode the template + try: + utemplate = unicode(template, tcharset) + except (LookupError, UnicodeError): + # template charset unknown, ignore + pass + else: + try: + template = utemplate.encode(charset) + except LookupError: + # target charset unknown, ignore + pass + except UnicodeError: + # template not encodable in target charset. + # Use character references + template = unicode_quote(utemplate) # Copied from Utils.maketext() text = template if dict is not None: *************** *** 650,660 **** d["archive_listing_start"] = quick_maketext( 'archliststart.html', raw=1, lang=mlist.preferred_language, - mlist=mlist) d["archive_listing_end"] = quick_maketext( 'archlistend.html', raw=1, lang=mlist.preferred_language, - mlist=mlist) accum = [] for a in self.archives: --- 699,709 ---- d["archive_listing_start"] = quick_maketext( 'archliststart.html', raw=1, lang=mlist.preferred_language, + mlist=mlist, charset = self.charset) d["archive_listing_end"] = quick_maketext( 'archlistend.html', raw=1, lang=mlist.preferred_language, + mlist=mlist, charset = self.charset) accum = [] for a in self.archives: From loewis@informatik.hu-berlin.de Sun Nov 10 08:47:36 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 10 Nov 2002 09:47:36 +0100 Subject: [Mailman-i18n] Re: the way i added my language charset In-Reply-To: <010601c28755$a0267500$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> <005501c28723$c1501010$6501a8c0@coco> <010601c28755$a0267500$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > >Notice that header is NOT added to NON DIGEST send if the MESSAGE is a > > MIME multipart message. This is by design. So just don't send > > multipart messages if you want mailman to add headers and footers. > > it this is by design, than there is nothing we can do This was perhaps a bit pessimistic. Here is the problem: It is not clear what the correct behaviour is when you have a multipart message, and you want to add headers and footers. Consider the case of a multipart message with three alternatives: - a text/plain alternative, - a text/html alternative, and - an audio/mpeg alternative. How should you add headers and footers here. There are several alternatives, which are all wrong: - add the header only to the text/plain alternative. Since the parts are alternative, the Email reader may chose a different alternative, so you would not see the header. The alternatives are considered to be equivalent, but modifying only one of them means they are no longer equivalent. - add the header to all three alternatives. But how can you add the header to the audio data? - Even if the audio alternative is absent (i.e. your case), adding the header and footer to the HTML part is still difficult. > if i send it as PLAIN message -- i get the headers and footers like > below how can i control not to send -mime multipart alternative > message ? > everybody have their presets. I see two options: - add the header and footer only to the text/plain alternative. Since this is philosophically wrong, the mailing list admin would need to select this explicitly. - strip all alternatives except for text/plain from the message (making the entire message text/plain), then add the header and footer to the message. I doubt anybody will implement either of these options soon. So if you want them, you need to implement them yourself. For the first option, please have a look at Mailman/Handlers/Decorate.py. For the second option, I don't know how to implement that. In any case, this has nothing to do with mailman-i18n anymore; this issue applies to mailman in general. You might want to contact the mailman-users list instead. Good luck, Martin From loewis@informatik.hu-berlin.de Sun Nov 10 08:49:37 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 10 Nov 2002 09:49:37 +0100 Subject: [Mailman-i18n] the internationalization patches In-Reply-To: <004701c287dc$b7320a20$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> <005501c28723$c1501010$6501a8c0@coco> <004701c287dc$b7320a20$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > instead of the patch, would the latest CVS version make the > necessary changes? No, those patches have not been considered, yet. I'm sorry I can't help further - you will have to investigate these issues yourself. Regards, Martin From m.ramsch@computer.org Sun Nov 10 12:08:56 2002 From: m.ramsch@computer.org (Martin Ramsch) Date: Sun, 10 Nov 2002 13:08:56 +0100 Subject: [Mailman-i18n] Add header/footer to MIME multipart (was: the way i added my language charset) References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco><001101c2870a$e6a263e0$6501a8c0@coco><005501c28723$c1501010$6501a8c0@coco><010601c28755$a0267500$6501a8c0@coco> Message-ID: <00ce01c288b1$f715b8a0$8255bad9@solo> This is a multi-part message in MIME format. ---------------------- multipart/mixed attachment Martin v. Löwis schrieb: > "shawn Erdil" writes: [...] > > if i send it as PLAIN message -- i get the headers and footers like > > below how can i control not to send -mime multipart alternative > > message ? > > everybody have their presets. > > I see two options: > - add the header and footer only to the text/plain alternative. Since > this is philosophically wrong, the mailing list admin would need > to select this explicitly. > - strip all alternatives except for text/plain from the message > (making the entire message text/plain), then add the header and > footer to the message. Another option for MIME multipart messages is to embed the message parts into a _new_ multipart/mixed structure which contains 1st the header as text/plain, then 2nd all parts of the message itself, then 3rd the footer as text/plain. For an example, see the two attached demo messages. The first one, "Test-Message.eml", has type multipart/alternative with text, HTML, and audio alternatives. The second one, "Test-Message with Header_Footer.eml", is changed into multipart/mixed and just adds seperate Header and Footer parts. (BTW, these themselves again could be multipart/alternative with both text and HTML headers/footers ... :-) HTH, Martin ---------------------- multipart/mixed attachment An embedded message was scrubbed... From: "Martin Ramsch" Subject: Test-Message with alternatives Date: Sun, 10 Nov 2002 12:49:04 +0100 Size: 3434 Url: http://mail.python.org/pipermail/mailman-i18n/attachments/20021110/d4b7eb54/Test-Message.txt ---------------------- multipart/mixed attachment An embedded message was scrubbed... From: "Martin Ramsch" Subject: Test-Message with alternatives Date: Sun, 10 Nov 2002 12:49:04 +0100 Size: 3801 Url: http://mail.python.org/pipermail/mailman-i18n/attachments/20021110/d4b7eb54/Test-MessagewithHeader_Footer.txt ---------------------- multipart/mixed attachment-- From loewis@informatik.hu-berlin.de Sun Nov 10 12:49:40 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 10 Nov 2002 13:49:40 +0100 Subject: [Mailman-i18n] Add header/footer to MIME multipart (was: the way i added my language charset) In-Reply-To: <00ce01c288b1$f715b8a0$8255bad9@solo> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> <005501c28723$c1501010$6501a8c0@coco> <010601c28755$a0267500$6501a8c0@coco> <00ce01c288b1$f715b8a0$8255bad9@solo> Message-ID: "Martin Ramsch" writes: > Another option for MIME multipart messages is to embed the > message parts into a _new_ multipart/mixed structure which > contains > 1st the header as text/plain, then > 2nd all parts of the message itself, then > 3rd the footer as text/plain. That's a good idea. It also applies to the other unsupported cases, e.g. other (non-text) content types, or charsets in the text/plain part that don't match the header/footer charset. Regards, Martin From cerdil@ttnet.net.tr Fri Nov 8 09:40:40 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Fri, 8 Nov 2002 11:40:40 +0200 Subject: [Mailman-i18n] the way i added my language charset References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco> Message-ID: <001101c2870a$e6a263e0$6501a8c0@coco> Martin, FIXED 1-since i couldn't get to add a new language from the mmconfig.py , i have just replaced the dutch template, that was in the system with Turkish. add_language('nl', _('Turkish'), 'iso-8859-9') it works as turkish with the nl symbol everything is fine now- no more errors are reported. let's see how it goes. i'll start the translation. PROBLEM 2- could we fix the archive problem with your patches ? PROBLEM 3-after the patches, could i show the message headers and footers in the NON-DIGEST emails. that s all:)) thank you. shawn erdil www.e-zbanner.com ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: Sent: Thursday, November 07, 2002 12:35 PM Subject: Re: [Mailman-i18n] Re: new error on the 8859-9 charset > "shawn Erdil" writes: > > > when i change the default list lang to "tr" , the mails were not > > getting sent. > > or is there anything ,on my mm config.py that is mis-configured > > No. I haven't researched that further, and I won't be able to do that > in the coming days. > > Regards, > Martin > > > _______________________________________________ > Mailman-i18n mailing list > Mailman-i18n@python.org > http://mail.python.org/mailman/listinfo/mailman-i18n > From loewis@informatik.hu-berlin.de Fri Nov 8 11:55:25 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 08 Nov 2002 12:55:25 +0100 Subject: [Mailman-i18n] Re: the way i added my language charset In-Reply-To: <001101c2870a$e6a263e0$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > PROBLEM > 2- could we fix the archive problem with your patches ? I cannot understand this question. Who is "we"? My patches fix the problems, yes. > 3-after the patches, could i show the message headers and footers in > the NON-DIGEST emails. Now that you've added the language to mailman, is there any problem remaining here? Regards, Martin From cerdil@ttnet.net.tr Fri Nov 8 12:38:34 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Fri, 8 Nov 2002 14:38:34 +0200 Subject: [Mailman-i18n] Re: the way i added my language charset References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco><001101c2870a$e6a263e0$6501a8c0@coco> Message-ID: <005501c28723$c1501010$6501a8c0@coco> ok, thank you for me just one problem remaining, there are two examples below that can explain my problem 3- i can't get the message headers and footers in NON DIGEST sends, when they arrive in outlook. ****************************** example: THIS IS NORMAL -DIGEST MODE with message headers and footers Send Python-list mailing list submissions to python-list@python.org To subscribe or unsubscribe via the World Wide Web, visit http://mail.python.org/mailman/listinfo/python-list or, via email, send a message with subject or body 'help' to python-list-request@python.org You can reach the person managing the list at python-list-admin@python.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Python-list digest..." ---------------------------------------------------------------------------- ---- Today's Topics: 1. Virtual Filesystem (was: Adding ftputil to the Python distribution?) (Stephan Diehl) 2. Re: re.sub() bug? (holger krekel) 3. Re: string.strip (Duncan Booth) 4. Re: RecordSet (ADO) with stored procs (Syver Enstad) 5. Re: Python Browser Applets (Richie Hindle) 6. Re: A vision for Parrot (Slaven Rezic) 7. Re: string.strip (Gerhard =?iso-8859-1?Q?H=E4ring?=) 8. Re: A vision for Parrot (Benjamin Goldberg) 9. Newbie-list-problem: how to supress constraining 2 lists - a=b ? (HugOnline) 10. Re: string.strip (Duncan Booth) 11. Re: Newbie-list-problem: how to supress constraining 2 lists - a=b ? (JohnJacob) 12. RE: string.strip (Simon Brunning) 13. Point an MS Access / VB developer in the right direction... (Dan) 14. stripping HTML comments in the face of programmer errors (Skip Montanaro) ---------------------------------------------------------------------------- ---- -- http://mail.python.org/mailman/listinfo/python-list **************************************************************************** ********************** this is in NON DIGEST MODE - no headers nor footers sizcede!!İmam Hatipli birinin genel başkan olması ve o idoliji'ye sahip > >olarak meclisde yer edinmeye çalışması içler acısı bir durum.Kendisi > >yıllarca İslam partisiyiz diye söyleyipduruyordu şimdi birden bire > >Muhafezekar Demokrat parti olup çıktılar.Ben türk halkının bu kadar dinci > >bir kesime oy verebileceğini düşünmüyorum,bu AKP nin iktidarı tek başına > >almasının nedeni halkın çıldırma noktasında olması ve hadi bakalım bu > >partiyi bir başa getirelimde ne olacağını görelim davasından başka bir **************************************************************************** ********** thats all when tey will normalize afetr the patch. thank you, shawn erdil ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: Sent: Friday, November 08, 2002 1:55 PM Subject: Re: the way i added my language charset > "shawn Erdil" writes: > > > PROBLEM > > 2- could we fix the archive problem with your patches ? > > I cannot understand this question. Who is "we"? My patches fix the > problems, yes. > > > 3-after the patches, could i show the message headers and footers in > > the NON-DIGEST emails. > > Now that you've added the language to mailman, is there any problem > remaining here? > > Regards, > Martin From loewis@informatik.hu-berlin.de Fri Nov 8 12:53:54 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 08 Nov 2002 13:53:54 +0100 Subject: [Mailman-i18n] Re: the way i added my language charset In-Reply-To: <005501c28723$c1501010$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> <005501c28723$c1501010$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > i can't get the message headers and footers in NON DIGEST sends, when > they arrive in outlook. Did you get them on the Playground list? I got them just fine, there, so I don't understand why you are having problems. Did you enter headers and footers in the mailman configuration? Notice that header is NOT added to NON DIGEST send if the MESSAGE is a MIME multipart message. This is by design. So just don't send multipart messages if you want mailman to add headers and footers. Regards, Martin From cerdil@ttnet.net.tr Fri Nov 8 18:35:34 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Fri, 8 Nov 2002 20:35:34 +0200 Subject: [Mailman-i18n] Re: the way i added my language charset References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco><001101c2870a$e6a263e0$6501a8c0@coco><005501c28723$c1501010$6501a8c0@coco> Message-ID: <010601c28755$a0267500$6501a8c0@coco> Martin, thanks you for your reply, >Notice that header is NOT added to NON DIGEST send if the MESSAGE is a > MIME multipart message. This is by design. So just don't send > multipart messages if you want mailman to add headers and footers. it this is by design, than there is nothing we can do if i send it as PLAIN message -- i get the headers and footers like below how can i control not to send -mime multipart alternative message ? everybody have their presets. may be it has to be converted somewhere. from multipart to text-plain. because all the non digest messages i get from yahoo groups are all plain/text encoded ****************************************** Buraya reklam verebilirsiniz? http://adserver.e-zbanner.com/cgi-bin/admonitor.cgi?e-zbannernetwork&gid=56& sid=23&cid=45&mid=136&id=943 _______________________________________________ List1 mailing list List1@digitiy.com http://digitiy.com/digitiygroups/listinfo/list1 Sesini her duydugumda Hissettigim acisini kalp atislarimda. Çok oldu terk ettiler Iyi ki de gittiler bizi anlayip, Bir kalabaligi sevmiyorum Bir de yalnizligi zaten bilirsin. Bu aralar tek mutlulugum Yanaginda güller açan o kadin. Bak bu da ikinci duble; ************************************************ thank you for your time shawn erdil ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: Sent: Friday, November 08, 2002 2:53 PM Subject: Re: the way i added my language charset > "shawn Erdil" writes: > > > i can't get the message headers and footers in NON DIGEST sends, when > > they arrive in outlook. > > Did you get them on the Playground list? I got them just fine, there, > so I don't understand why you are having problems. Did you enter > headers and footers in the mailman configuration? > > Notice that header is NOT added to NON DIGEST send if the MESSAGE is a > MIME multipart message. This is by design. So just don't send > multipart messages if you want mailman to add headers and footers. > > Regards, > Martin From cerdil@ttnet.net.tr Fri Nov 8 09:40:40 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Fri, 8 Nov 2002 11:40:40 +0200 Subject: [Mailman-i18n] the way i added my language charset References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco> Message-ID: <001101c2870a$e6a263e0$6501a8c0@coco> Martin, FIXED 1-since i couldn't get to add a new language from the mmconfig.py , i have just replaced the dutch template, that was in the system with Turkish. add_language('nl', _('Turkish'), 'iso-8859-9') it works as turkish with the nl symbol everything is fine now- no more errors are reported. let's see how it goes. i'll start the translation. PROBLEM 2- could we fix the archive problem with your patches ? PROBLEM 3-after the patches, could i show the message headers and footers in the NON-DIGEST emails. that s all:)) thank you. shawn erdil www.e-zbanner.com ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: Sent: Thursday, November 07, 2002 12:35 PM Subject: Re: [Mailman-i18n] Re: new error on the 8859-9 charset > "shawn Erdil" writes: > > > when i change the default list lang to "tr" , the mails were not > > getting sent. > > or is there anything ,on my mm config.py that is mis-configured > > No. I haven't researched that further, and I won't be able to do that > in the coming days. > > Regards, > Martin > > > _______________________________________________ > Mailman-i18n mailing list > Mailman-i18n@python.org > http://mail.python.org/mailman/listinfo/mailman-i18n > From loewis@informatik.hu-berlin.de Fri Nov 8 11:55:25 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 08 Nov 2002 12:55:25 +0100 Subject: [Mailman-i18n] Re: the way i added my language charset In-Reply-To: <001101c2870a$e6a263e0$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > PROBLEM > 2- could we fix the archive problem with your patches ? I cannot understand this question. Who is "we"? My patches fix the problems, yes. > 3-after the patches, could i show the message headers and footers in > the NON-DIGEST emails. Now that you've added the language to mailman, is there any problem remaining here? Regards, Martin From cerdil@ttnet.net.tr Fri Nov 8 12:38:34 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Fri, 8 Nov 2002 14:38:34 +0200 Subject: [Mailman-i18n] Re: the way i added my language charset References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco><001101c2870a$e6a263e0$6501a8c0@coco> Message-ID: <005501c28723$c1501010$6501a8c0@coco> ok, thank you for me just one problem remaining, there are two examples below that can explain my problem 3- i can't get the message headers and footers in NON DIGEST sends, when they arrive in outlook. ****************************** example: THIS IS NORMAL -DIGEST MODE with message headers and footers Send Python-list mailing list submissions to python-list@python.org To subscribe or unsubscribe via the World Wide Web, visit http://mail.python.org/mailman/listinfo/python-list or, via email, send a message with subject or body 'help' to python-list-request@python.org You can reach the person managing the list at python-list-admin@python.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Python-list digest..." ---------------------------------------------------------------------------- ---- Today's Topics: 1. Virtual Filesystem (was: Adding ftputil to the Python distribution?) (Stephan Diehl) 2. Re: re.sub() bug? (holger krekel) 3. Re: string.strip (Duncan Booth) 4. Re: RecordSet (ADO) with stored procs (Syver Enstad) 5. Re: Python Browser Applets (Richie Hindle) 6. Re: A vision for Parrot (Slaven Rezic) 7. Re: string.strip (Gerhard =?iso-8859-1?Q?H=E4ring?=) 8. Re: A vision for Parrot (Benjamin Goldberg) 9. Newbie-list-problem: how to supress constraining 2 lists - a=b ? (HugOnline) 10. Re: string.strip (Duncan Booth) 11. Re: Newbie-list-problem: how to supress constraining 2 lists - a=b ? (JohnJacob) 12. RE: string.strip (Simon Brunning) 13. Point an MS Access / VB developer in the right direction... (Dan) 14. stripping HTML comments in the face of programmer errors (Skip Montanaro) ---------------------------------------------------------------------------- ---- -- http://mail.python.org/mailman/listinfo/python-list **************************************************************************** ********************** this is in NON DIGEST MODE - no headers nor footers sizcede!!İmam Hatipli birinin genel başkan olması ve o idoliji'ye sahip > >olarak meclisde yer edinmeye çalışması içler acısı bir durum.Kendisi > >yıllarca İslam partisiyiz diye söyleyipduruyordu şimdi birden bire > >Muhafezekar Demokrat parti olup çıktılar.Ben türk halkının bu kadar dinci > >bir kesime oy verebileceğini düşünmüyorum,bu AKP nin iktidarı tek başına > >almasının nedeni halkın çıldırma noktasında olması ve hadi bakalım bu > >partiyi bir başa getirelimde ne olacağını görelim davasından başka bir **************************************************************************** ********** thats all when tey will normalize afetr the patch. thank you, shawn erdil ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: Sent: Friday, November 08, 2002 1:55 PM Subject: Re: the way i added my language charset > "shawn Erdil" writes: > > > PROBLEM > > 2- could we fix the archive problem with your patches ? > > I cannot understand this question. Who is "we"? My patches fix the > problems, yes. > > > 3-after the patches, could i show the message headers and footers in > > the NON-DIGEST emails. > > Now that you've added the language to mailman, is there any problem > remaining here? > > Regards, > Martin From loewis@informatik.hu-berlin.de Fri Nov 8 12:53:54 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 08 Nov 2002 13:53:54 +0100 Subject: [Mailman-i18n] Re: the way i added my language charset In-Reply-To: <005501c28723$c1501010$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> <005501c28723$c1501010$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > i can't get the message headers and footers in NON DIGEST sends, when > they arrive in outlook. Did you get them on the Playground list? I got them just fine, there, so I don't understand why you are having problems. Did you enter headers and footers in the mailman configuration? Notice that header is NOT added to NON DIGEST send if the MESSAGE is a MIME multipart message. This is by design. So just don't send multipart messages if you want mailman to add headers and footers. Regards, Martin From cerdil@ttnet.net.tr Fri Nov 8 18:35:34 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Fri, 8 Nov 2002 20:35:34 +0200 Subject: [Mailman-i18n] Re: the way i added my language charset References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco><001101c2870a$e6a263e0$6501a8c0@coco><005501c28723$c1501010$6501a8c0@coco> Message-ID: <010601c28755$a0267500$6501a8c0@coco> Martin, thanks you for your reply, >Notice that header is NOT added to NON DIGEST send if the MESSAGE is a > MIME multipart message. This is by design. So just don't send > multipart messages if you want mailman to add headers and footers. it this is by design, than there is nothing we can do if i send it as PLAIN message -- i get the headers and footers like below how can i control not to send -mime multipart alternative message ? everybody have their presets. may be it has to be converted somewhere. from multipart to text-plain. because all the non digest messages i get from yahoo groups are all plain/text encoded ****************************************** Buraya reklam verebilirsiniz? http://adserver.e-zbanner.com/cgi-bin/admonitor.cgi?e-zbannernetwork&gid=56& sid=23&cid=45&mid=136&id=943 _______________________________________________ List1 mailing list List1@digitiy.com http://digitiy.com/digitiygroups/listinfo/list1 Sesini her duydugumda Hissettigim acisini kalp atislarimda. Çok oldu terk ettiler Iyi ki de gittiler bizi anlayip, Bir kalabaligi sevmiyorum Bir de yalnizligi zaten bilirsin. Bu aralar tek mutlulugum Yanaginda güller açan o kadin. Bak bu da ikinci duble; ************************************************ thank you for your time shawn erdil ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: Sent: Friday, November 08, 2002 2:53 PM Subject: Re: the way i added my language charset > "shawn Erdil" writes: > > > i can't get the message headers and footers in NON DIGEST sends, when > > they arrive in outlook. > > Did you get them on the Playground list? I got them just fine, there, > so I don't understand why you are having problems. Did you enter > headers and footers in the mailman configuration? > > Notice that header is NOT added to NON DIGEST send if the MESSAGE is a > MIME multipart message. This is by design. So just don't send > multipart messages if you want mailman to add headers and footers. > > Regards, > Martin From cerdil@ttnet.net.tr Sat Nov 9 10:42:34 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Sat, 9 Nov 2002 12:42:34 +0200 Subject: [Mailman-i18n] the internationalization patches References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco><001101c2870a$e6a263e0$6501a8c0@coco><005501c28723$c1501010$6501a8c0@coco> Message-ID: <004701c287dc$b7320a20$6501a8c0@coco> i applied the latest patches to i18n.py and scrubber.py but in HyperachArch.py 3 out of 24 hunks FAILED -- i get these rejections , in HyperArch.py , as the result of the HyperArch.py patch. instead of the patch, would the latest CVS version make the necessary changes? *i have replaced the latest cvs version already. ******My only problem at the moment is to strip the html,mime multipart alternative content & convert to plain text for archiving, but i am not succesfull at doing it. thank you, shawn erdil e-zbanner.com *************** *** 162,168 **** # strings. Keys are (templatefile, lang) tuples. _templatecache = {} - def quick_maketext(templatefile, dict=None, raw=0, lang=None, mlist=None): if lang is None: lang = mlist.preferred_language template = _templatecache.get((templatefile, lang)) --- 178,185 ---- # strings. Keys are (templatefile, lang) tuples. _templatecache = {} + def quick_maketext(templatefile, dict=None, raw=0, + lang=None, mlist=None, charset = None): if lang is None: lang = mlist.preferred_language template = _templatecache.get((templatefile, lang)) *************** *** 170,175 **** # Use the basic maketext, with defaults to get the raw template template = Utils.maketext(templatefile, lang=lang, raw=1) _templatecache[(templatefile, lang)] = template # Copied from Utils.maketext() text = template if dict is not None: --- 187,210 ---- # Use the basic maketext, with defaults to get the raw template template = Utils.maketext(templatefile, lang=lang, raw=1) _templatecache[(templatefile, lang)] = template + tcharset = Utils.GetCharSet(lang) + if charset and tcharset != charset and tcharset != 'us-ascii': + # Need to recode the template + try: + utemplate = unicode(template, tcharset) + except (LookupError, UnicodeError): + # template charset unknown, ignore + pass + else: + try: + template = utemplate.encode(charset) + except LookupError: + # target charset unknown, ignore + pass + except UnicodeError: + # template not encodable in target charset. + # Use character references + template = unicode_quote(utemplate) # Copied from Utils.maketext() text = template if dict is not None: *************** *** 650,660 **** d["archive_listing_start"] = quick_maketext( 'archliststart.html', raw=1, lang=mlist.preferred_language, - mlist=mlist) d["archive_listing_end"] = quick_maketext( 'archlistend.html', raw=1, lang=mlist.preferred_language, - mlist=mlist) accum = [] for a in self.archives: --- 699,709 ---- d["archive_listing_start"] = quick_maketext( 'archliststart.html', raw=1, lang=mlist.preferred_language, + mlist=mlist, charset = self.charset) d["archive_listing_end"] = quick_maketext( 'archlistend.html', raw=1, lang=mlist.preferred_language, + mlist=mlist, charset = self.charset) accum = [] for a in self.archives: From loewis@informatik.hu-berlin.de Sun Nov 10 08:47:36 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 10 Nov 2002 09:47:36 +0100 Subject: [Mailman-i18n] Re: the way i added my language charset In-Reply-To: <010601c28755$a0267500$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> <005501c28723$c1501010$6501a8c0@coco> <010601c28755$a0267500$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > >Notice that header is NOT added to NON DIGEST send if the MESSAGE is a > > MIME multipart message. This is by design. So just don't send > > multipart messages if you want mailman to add headers and footers. > > it this is by design, than there is nothing we can do This was perhaps a bit pessimistic. Here is the problem: It is not clear what the correct behaviour is when you have a multipart message, and you want to add headers and footers. Consider the case of a multipart message with three alternatives: - a text/plain alternative, - a text/html alternative, and - an audio/mpeg alternative. How should you add headers and footers here. There are several alternatives, which are all wrong: - add the header only to the text/plain alternative. Since the parts are alternative, the Email reader may chose a different alternative, so you would not see the header. The alternatives are considered to be equivalent, but modifying only one of them means they are no longer equivalent. - add the header to all three alternatives. But how can you add the header to the audio data? - Even if the audio alternative is absent (i.e. your case), adding the header and footer to the HTML part is still difficult. > if i send it as PLAIN message -- i get the headers and footers like > below how can i control not to send -mime multipart alternative > message ? > everybody have their presets. I see two options: - add the header and footer only to the text/plain alternative. Since this is philosophically wrong, the mailing list admin would need to select this explicitly. - strip all alternatives except for text/plain from the message (making the entire message text/plain), then add the header and footer to the message. I doubt anybody will implement either of these options soon. So if you want them, you need to implement them yourself. For the first option, please have a look at Mailman/Handlers/Decorate.py. For the second option, I don't know how to implement that. In any case, this has nothing to do with mailman-i18n anymore; this issue applies to mailman in general. You might want to contact the mailman-users list instead. Good luck, Martin From loewis@informatik.hu-berlin.de Sun Nov 10 08:49:37 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 10 Nov 2002 09:49:37 +0100 Subject: [Mailman-i18n] the internationalization patches In-Reply-To: <004701c287dc$b7320a20$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> <005501c28723$c1501010$6501a8c0@coco> <004701c287dc$b7320a20$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > instead of the patch, would the latest CVS version make the > necessary changes? No, those patches have not been considered, yet. I'm sorry I can't help further - you will have to investigate these issues yourself. Regards, Martin From m.ramsch@computer.org Sun Nov 10 12:08:56 2002 From: m.ramsch@computer.org (Martin Ramsch) Date: Sun, 10 Nov 2002 13:08:56 +0100 Subject: [Mailman-i18n] Add header/footer to MIME multipart (was: the way i added my language charset) References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco><001101c2870a$e6a263e0$6501a8c0@coco><005501c28723$c1501010$6501a8c0@coco><010601c28755$a0267500$6501a8c0@coco> Message-ID: <00ce01c288b1$f715b8a0$8255bad9@solo> This is a multi-part message in MIME format. ---------------------- multipart/mixed attachment Martin v. Löwis schrieb: > "shawn Erdil" writes: [...] > > if i send it as PLAIN message -- i get the headers and footers like > > below how can i control not to send -mime multipart alternative > > message ? > > everybody have their presets. > > I see two options: > - add the header and footer only to the text/plain alternative. Since > this is philosophically wrong, the mailing list admin would need > to select this explicitly. > - strip all alternatives except for text/plain from the message > (making the entire message text/plain), then add the header and > footer to the message. Another option for MIME multipart messages is to embed the message parts into a _new_ multipart/mixed structure which contains 1st the header as text/plain, then 2nd all parts of the message itself, then 3rd the footer as text/plain. For an example, see the two attached demo messages. The first one, "Test-Message.eml", has type multipart/alternative with text, HTML, and audio alternatives. The second one, "Test-Message with Header_Footer.eml", is changed into multipart/mixed and just adds seperate Header and Footer parts. (BTW, these themselves again could be multipart/alternative with both text and HTML headers/footers ... :-) HTH, Martin ---------------------- multipart/mixed attachment An embedded message was scrubbed... From: "Martin Ramsch" Subject: Test-Message with alternatives Date: Sun, 10 Nov 2002 12:49:04 +0100 Size: 3434 Url: http://mail.python.org/pipermail/mailman-i18n/attachments/20021110/d4b7eb54/Test-Message-0001.txt ---------------------- multipart/mixed attachment An embedded message was scrubbed... From: "Martin Ramsch" Subject: Test-Message with alternatives Date: Sun, 10 Nov 2002 12:49:04 +0100 Size: 3801 Url: http://mail.python.org/pipermail/mailman-i18n/attachments/20021110/d4b7eb54/Test-MessagewithHeader_Footer-0001.txt ---------------------- multipart/mixed attachment-- From loewis@informatik.hu-berlin.de Sun Nov 10 12:49:40 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 10 Nov 2002 13:49:40 +0100 Subject: [Mailman-i18n] Add header/footer to MIME multipart (was: the way i added my language charset) In-Reply-To: <00ce01c288b1$f715b8a0$8255bad9@solo> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> <005501c28723$c1501010$6501a8c0@coco> <010601c28755$a0267500$6501a8c0@coco> <00ce01c288b1$f715b8a0$8255bad9@solo> Message-ID: "Martin Ramsch" writes: > Another option for MIME multipart messages is to embed the > message parts into a _new_ multipart/mixed structure which > contains > 1st the header as text/plain, then > 2nd all parts of the message itself, then > 3rd the footer as text/plain. That's a good idea. It also applies to the other unsupported cases, e.g. other (non-text) content types, or charsets in the text/plain part that don't match the header/footer charset. Regards, Martin From cerdil@ttnet.net.tr Fri Nov 8 09:40:40 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Fri, 8 Nov 2002 11:40:40 +0200 Subject: [Mailman-i18n] the way i added my language charset References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco> Message-ID: <001101c2870a$e6a263e0$6501a8c0@coco> Martin, FIXED 1-since i couldn't get to add a new language from the mmconfig.py , i have just replaced the dutch template, that was in the system with Turkish. add_language('nl', _('Turkish'), 'iso-8859-9') it works as turkish with the nl symbol everything is fine now- no more errors are reported. let's see how it goes. i'll start the translation. PROBLEM 2- could we fix the archive problem with your patches ? PROBLEM 3-after the patches, could i show the message headers and footers in the NON-DIGEST emails. that s all:)) thank you. shawn erdil www.e-zbanner.com ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: Sent: Thursday, November 07, 2002 12:35 PM Subject: Re: [Mailman-i18n] Re: new error on the 8859-9 charset > "shawn Erdil" writes: > > > when i change the default list lang to "tr" , the mails were not > > getting sent. > > or is there anything ,on my mm config.py that is mis-configured > > No. I haven't researched that further, and I won't be able to do that > in the coming days. > > Regards, > Martin > > > _______________________________________________ > Mailman-i18n mailing list > Mailman-i18n@python.org > http://mail.python.org/mailman/listinfo/mailman-i18n > From loewis@informatik.hu-berlin.de Fri Nov 8 11:55:25 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 08 Nov 2002 12:55:25 +0100 Subject: [Mailman-i18n] Re: the way i added my language charset In-Reply-To: <001101c2870a$e6a263e0$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > PROBLEM > 2- could we fix the archive problem with your patches ? I cannot understand this question. Who is "we"? My patches fix the problems, yes. > 3-after the patches, could i show the message headers and footers in > the NON-DIGEST emails. Now that you've added the language to mailman, is there any problem remaining here? Regards, Martin From cerdil@ttnet.net.tr Fri Nov 8 12:38:34 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Fri, 8 Nov 2002 14:38:34 +0200 Subject: [Mailman-i18n] Re: the way i added my language charset References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco><001101c2870a$e6a263e0$6501a8c0@coco> Message-ID: <005501c28723$c1501010$6501a8c0@coco> ok, thank you for me just one problem remaining, there are two examples below that can explain my problem 3- i can't get the message headers and footers in NON DIGEST sends, when they arrive in outlook. ****************************** example: THIS IS NORMAL -DIGEST MODE with message headers and footers Send Python-list mailing list submissions to python-list@python.org To subscribe or unsubscribe via the World Wide Web, visit http://mail.python.org/mailman/listinfo/python-list or, via email, send a message with subject or body 'help' to python-list-request@python.org You can reach the person managing the list at python-list-admin@python.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Python-list digest..." ---------------------------------------------------------------------------- ---- Today's Topics: 1. Virtual Filesystem (was: Adding ftputil to the Python distribution?) (Stephan Diehl) 2. Re: re.sub() bug? (holger krekel) 3. Re: string.strip (Duncan Booth) 4. Re: RecordSet (ADO) with stored procs (Syver Enstad) 5. Re: Python Browser Applets (Richie Hindle) 6. Re: A vision for Parrot (Slaven Rezic) 7. Re: string.strip (Gerhard =?iso-8859-1?Q?H=E4ring?=) 8. Re: A vision for Parrot (Benjamin Goldberg) 9. Newbie-list-problem: how to supress constraining 2 lists - a=b ? (HugOnline) 10. Re: string.strip (Duncan Booth) 11. Re: Newbie-list-problem: how to supress constraining 2 lists - a=b ? (JohnJacob) 12. RE: string.strip (Simon Brunning) 13. Point an MS Access / VB developer in the right direction... (Dan) 14. stripping HTML comments in the face of programmer errors (Skip Montanaro) ---------------------------------------------------------------------------- ---- -- http://mail.python.org/mailman/listinfo/python-list **************************************************************************** ********************** this is in NON DIGEST MODE - no headers nor footers sizcede!!İmam Hatipli birinin genel başkan olması ve o idoliji'ye sahip > >olarak meclisde yer edinmeye çalışması içler acısı bir durum.Kendisi > >yıllarca İslam partisiyiz diye söyleyipduruyordu şimdi birden bire > >Muhafezekar Demokrat parti olup çıktılar.Ben türk halkının bu kadar dinci > >bir kesime oy verebileceğini düşünmüyorum,bu AKP nin iktidarı tek başına > >almasının nedeni halkın çıldırma noktasında olması ve hadi bakalım bu > >partiyi bir başa getirelimde ne olacağını görelim davasından başka bir **************************************************************************** ********** thats all when tey will normalize afetr the patch. thank you, shawn erdil ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: Sent: Friday, November 08, 2002 1:55 PM Subject: Re: the way i added my language charset > "shawn Erdil" writes: > > > PROBLEM > > 2- could we fix the archive problem with your patches ? > > I cannot understand this question. Who is "we"? My patches fix the > problems, yes. > > > 3-after the patches, could i show the message headers and footers in > > the NON-DIGEST emails. > > Now that you've added the language to mailman, is there any problem > remaining here? > > Regards, > Martin From loewis@informatik.hu-berlin.de Fri Nov 8 12:53:54 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 08 Nov 2002 13:53:54 +0100 Subject: [Mailman-i18n] Re: the way i added my language charset In-Reply-To: <005501c28723$c1501010$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> <005501c28723$c1501010$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > i can't get the message headers and footers in NON DIGEST sends, when > they arrive in outlook. Did you get them on the Playground list? I got them just fine, there, so I don't understand why you are having problems. Did you enter headers and footers in the mailman configuration? Notice that header is NOT added to NON DIGEST send if the MESSAGE is a MIME multipart message. This is by design. So just don't send multipart messages if you want mailman to add headers and footers. Regards, Martin From cerdil@ttnet.net.tr Fri Nov 8 18:35:34 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Fri, 8 Nov 2002 20:35:34 +0200 Subject: [Mailman-i18n] Re: the way i added my language charset References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco><001101c2870a$e6a263e0$6501a8c0@coco><005501c28723$c1501010$6501a8c0@coco> Message-ID: <010601c28755$a0267500$6501a8c0@coco> Martin, thanks you for your reply, >Notice that header is NOT added to NON DIGEST send if the MESSAGE is a > MIME multipart message. This is by design. So just don't send > multipart messages if you want mailman to add headers and footers. it this is by design, than there is nothing we can do if i send it as PLAIN message -- i get the headers and footers like below how can i control not to send -mime multipart alternative message ? everybody have their presets. may be it has to be converted somewhere. from multipart to text-plain. because all the non digest messages i get from yahoo groups are all plain/text encoded ****************************************** Buraya reklam verebilirsiniz? http://adserver.e-zbanner.com/cgi-bin/admonitor.cgi?e-zbannernetwork&gid=56& sid=23&cid=45&mid=136&id=943 _______________________________________________ List1 mailing list List1@digitiy.com http://digitiy.com/digitiygroups/listinfo/list1 Sesini her duydugumda Hissettigim acisini kalp atislarimda. Çok oldu terk ettiler Iyi ki de gittiler bizi anlayip, Bir kalabaligi sevmiyorum Bir de yalnizligi zaten bilirsin. Bu aralar tek mutlulugum Yanaginda güller açan o kadin. Bak bu da ikinci duble; ************************************************ thank you for your time shawn erdil ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: Sent: Friday, November 08, 2002 2:53 PM Subject: Re: the way i added my language charset > "shawn Erdil" writes: > > > i can't get the message headers and footers in NON DIGEST sends, when > > they arrive in outlook. > > Did you get them on the Playground list? I got them just fine, there, > so I don't understand why you are having problems. Did you enter > headers and footers in the mailman configuration? > > Notice that header is NOT added to NON DIGEST send if the MESSAGE is a > MIME multipart message. This is by design. So just don't send > multipart messages if you want mailman to add headers and footers. > > Regards, > Martin From cerdil@ttnet.net.tr Sat Nov 9 10:42:34 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Sat, 9 Nov 2002 12:42:34 +0200 Subject: [Mailman-i18n] the internationalization patches References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco><001101c2870a$e6a263e0$6501a8c0@coco><005501c28723$c1501010$6501a8c0@coco> Message-ID: <004701c287dc$b7320a20$6501a8c0@coco> i applied the latest patches to i18n.py and scrubber.py but in HyperachArch.py 3 out of 24 hunks FAILED -- i get these rejections , in HyperArch.py , as the result of the HyperArch.py patch. instead of the patch, would the latest CVS version make the necessary changes? *i have replaced the latest cvs version already. ******My only problem at the moment is to strip the html,mime multipart alternative content & convert to plain text for archiving, but i am not succesfull at doing it. thank you, shawn erdil e-zbanner.com *************** *** 162,168 **** # strings. Keys are (templatefile, lang) tuples. _templatecache = {} - def quick_maketext(templatefile, dict=None, raw=0, lang=None, mlist=None): if lang is None: lang = mlist.preferred_language template = _templatecache.get((templatefile, lang)) --- 178,185 ---- # strings. Keys are (templatefile, lang) tuples. _templatecache = {} + def quick_maketext(templatefile, dict=None, raw=0, + lang=None, mlist=None, charset = None): if lang is None: lang = mlist.preferred_language template = _templatecache.get((templatefile, lang)) *************** *** 170,175 **** # Use the basic maketext, with defaults to get the raw template template = Utils.maketext(templatefile, lang=lang, raw=1) _templatecache[(templatefile, lang)] = template # Copied from Utils.maketext() text = template if dict is not None: --- 187,210 ---- # Use the basic maketext, with defaults to get the raw template template = Utils.maketext(templatefile, lang=lang, raw=1) _templatecache[(templatefile, lang)] = template + tcharset = Utils.GetCharSet(lang) + if charset and tcharset != charset and tcharset != 'us-ascii': + # Need to recode the template + try: + utemplate = unicode(template, tcharset) + except (LookupError, UnicodeError): + # template charset unknown, ignore + pass + else: + try: + template = utemplate.encode(charset) + except LookupError: + # target charset unknown, ignore + pass + except UnicodeError: + # template not encodable in target charset. + # Use character references + template = unicode_quote(utemplate) # Copied from Utils.maketext() text = template if dict is not None: *************** *** 650,660 **** d["archive_listing_start"] = quick_maketext( 'archliststart.html', raw=1, lang=mlist.preferred_language, - mlist=mlist) d["archive_listing_end"] = quick_maketext( 'archlistend.html', raw=1, lang=mlist.preferred_language, - mlist=mlist) accum = [] for a in self.archives: --- 699,709 ---- d["archive_listing_start"] = quick_maketext( 'archliststart.html', raw=1, lang=mlist.preferred_language, + mlist=mlist, charset = self.charset) d["archive_listing_end"] = quick_maketext( 'archlistend.html', raw=1, lang=mlist.preferred_language, + mlist=mlist, charset = self.charset) accum = [] for a in self.archives: From loewis@informatik.hu-berlin.de Sun Nov 10 08:47:36 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 10 Nov 2002 09:47:36 +0100 Subject: [Mailman-i18n] Re: the way i added my language charset In-Reply-To: <010601c28755$a0267500$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> <005501c28723$c1501010$6501a8c0@coco> <010601c28755$a0267500$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > >Notice that header is NOT added to NON DIGEST send if the MESSAGE is a > > MIME multipart message. This is by design. So just don't send > > multipart messages if you want mailman to add headers and footers. > > it this is by design, than there is nothing we can do This was perhaps a bit pessimistic. Here is the problem: It is not clear what the correct behaviour is when you have a multipart message, and you want to add headers and footers. Consider the case of a multipart message with three alternatives: - a text/plain alternative, - a text/html alternative, and - an audio/mpeg alternative. How should you add headers and footers here. There are several alternatives, which are all wrong: - add the header only to the text/plain alternative. Since the parts are alternative, the Email reader may chose a different alternative, so you would not see the header. The alternatives are considered to be equivalent, but modifying only one of them means they are no longer equivalent. - add the header to all three alternatives. But how can you add the header to the audio data? - Even if the audio alternative is absent (i.e. your case), adding the header and footer to the HTML part is still difficult. > if i send it as PLAIN message -- i get the headers and footers like > below how can i control not to send -mime multipart alternative > message ? > everybody have their presets. I see two options: - add the header and footer only to the text/plain alternative. Since this is philosophically wrong, the mailing list admin would need to select this explicitly. - strip all alternatives except for text/plain from the message (making the entire message text/plain), then add the header and footer to the message. I doubt anybody will implement either of these options soon. So if you want them, you need to implement them yourself. For the first option, please have a look at Mailman/Handlers/Decorate.py. For the second option, I don't know how to implement that. In any case, this has nothing to do with mailman-i18n anymore; this issue applies to mailman in general. You might want to contact the mailman-users list instead. Good luck, Martin From loewis@informatik.hu-berlin.de Sun Nov 10 08:49:37 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 10 Nov 2002 09:49:37 +0100 Subject: [Mailman-i18n] the internationalization patches In-Reply-To: <004701c287dc$b7320a20$6501a8c0@coco> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> <005501c28723$c1501010$6501a8c0@coco> <004701c287dc$b7320a20$6501a8c0@coco> Message-ID: "shawn Erdil" writes: > instead of the patch, would the latest CVS version make the > necessary changes? No, those patches have not been considered, yet. I'm sorry I can't help further - you will have to investigate these issues yourself. Regards, Martin From m.ramsch@computer.org Sun Nov 10 12:08:56 2002 From: m.ramsch@computer.org (Martin Ramsch) Date: Sun, 10 Nov 2002 13:08:56 +0100 Subject: [Mailman-i18n] Add header/footer to MIME multipart (was: the way i added my language charset) References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco><001101c2870a$e6a263e0$6501a8c0@coco><005501c28723$c1501010$6501a8c0@coco><010601c28755$a0267500$6501a8c0@coco> Message-ID: <00ce01c288b1$f715b8a0$8255bad9@solo> This is a multi-part message in MIME format. ---------------------- multipart/mixed attachment Martin v. Löwis schrieb: > "shawn Erdil" writes: [...] > > if i send it as PLAIN message -- i get the headers and footers like > > below how can i control not to send -mime multipart alternative > > message ? > > everybody have their presets. > > I see two options: > - add the header and footer only to the text/plain alternative. Since > this is philosophically wrong, the mailing list admin would need > to select this explicitly. > - strip all alternatives except for text/plain from the message > (making the entire message text/plain), then add the header and > footer to the message. Another option for MIME multipart messages is to embed the message parts into a _new_ multipart/mixed structure which contains 1st the header as text/plain, then 2nd all parts of the message itself, then 3rd the footer as text/plain. For an example, see the two attached demo messages. The first one, "Test-Message.eml", has type multipart/alternative with text, HTML, and audio alternatives. The second one, "Test-Message with Header_Footer.eml", is changed into multipart/mixed and just adds seperate Header and Footer parts. (BTW, these themselves again could be multipart/alternative with both text and HTML headers/footers ... :-) HTH, Martin ---------------------- multipart/mixed attachment An embedded message was scrubbed... From: "Martin Ramsch" Subject: Test-Message with alternatives Date: Sun, 10 Nov 2002 12:49:04 +0100 Size: 3434 Url: http://mail.python.org/pipermail/mailman-i18n/attachments/20021110/d4b7eb54/Test-Message-0002.txt ---------------------- multipart/mixed attachment An embedded message was scrubbed... From: "Martin Ramsch" Subject: Test-Message with alternatives Date: Sun, 10 Nov 2002 12:49:04 +0100 Size: 3801 Url: http://mail.python.org/pipermail/mailman-i18n/attachments/20021110/d4b7eb54/Test-MessagewithHeader_Footer-0002.txt ---------------------- multipart/mixed attachment-- From loewis@informatik.hu-berlin.de Sun Nov 10 12:49:40 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 10 Nov 2002 13:49:40 +0100 Subject: [Mailman-i18n] Add header/footer to MIME multipart (was: the way i added my language charset) In-Reply-To: <00ce01c288b1$f715b8a0$8255bad9@solo> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> <005501c28723$c1501010$6501a8c0@coco> <010601c28755$a0267500$6501a8c0@coco> <00ce01c288b1$f715b8a0$8255bad9@solo> Message-ID: "Martin Ramsch" writes: > Another option for MIME multipart messages is to embed the > message parts into a _new_ multipart/mixed structure which > contains > 1st the header as text/plain, then > 2nd all parts of the message itself, then > 3rd the footer as text/plain. That's a good idea. It also applies to the other unsupported cases, e.g. other (non-text) content types, or charsets in the text/plain part that don't match the header/footer charset. Regards, Martin From cerdil@ttnet.net.tr Fri Nov 8 09:40:40 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Fri, 8 Nov 2002 11:40:40 +0200 Subject: [Mailman-i18n] the way i added my language charset References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco> Message-ID: <001101c2870a$e6a263e0$6501a8c0@coco> Martin, FIXED 1-since i couldn't get to add a new language from the mmconfig.py , i have just replaced the dutch template, that was in the system with Turkish. add_language('nl', _('Turkish'), 'iso-8859-9') it works as turkish with the nl symbol everything is fine now- no more errors are reported. let's see how it goes. i'll start the translation. PROBLEM 2- could we fix the archive problem with your patches ? PROBLEM 3-after the patches, could i show the message headers and footers in the NON-DIGEST emails. that s all:)) thank you. shawn erdil www.e-zbanner.com ----- Original Message ----- From: "Martin v. Löwis" To: "shawn Erdil" Cc: Sent: Thursday, November 07, 2002 12:35 PM Subject: Re: [Mailman-i18n] Re: new error on the 8859-9 charset > "shawn Erdil" writes: > > > when i change the default list lang to "tr" , the mails were not > > getting sent. > > or is there anything ,on my mm config.py that is mis-configured > > No. I haven't researched that further, and I won't be able to do that > in the coming days. > > Regards, > Martin > > > _______________________________________________ > Mailman-i18n mailing list > Mailman-i18n@python.org > http://mail.python.org/mailman/listinfo/mailman-i18n > From cerdil@ttnet.net.tr Tue Nov 12 17:01:54 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Tue, 12 Nov 2002 19:01:54 +0200 Subject: [Mailman-i18n] solutions are fine, but require coding in python Message-ID: <025e01c28a6d$34630c50$6501a8c0@coco> This is a multi-part message in MIME format. ---------------------- multipart/alternative attachment Thank you, for your solutions, concerning the charset = originated problems, in the archiving and the non- existance of = message footers and headers, in non digest emails. But , to tell you the truth, unless it is a patch or ready code = change, we cannot code in python, to make other necessary = changes.thank you. shawn Erdil. www.e-zbanner.com ---------------------- multipart/alternative attachment An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-i18n/attachments/20021112/d34e09a5/attachment.html ---------------------- multipart/alternative attachment-- From barry@python.org Tue Nov 12 21:33:52 2002 From: barry@python.org (Barry A. Warsaw) Date: Tue, 12 Nov 2002 16:33:52 -0500 Subject: [Mailman-i18n] Add header/footer to MIME multipart (was: the way i added my language charset) References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> <005501c28723$c1501010$6501a8c0@coco> <010601c28755$a0267500$6501a8c0@coco> <00ce01c288b1$f715b8a0$8255bad9@solo> Message-ID: <15825.29632.754829.971333@gargle.gargle.HOWL> | Another option for MIME multipart messages is to embed the | message parts into a _new_ multipart/mixed structure which | contains | 1st the header as text/plain, then | 2nd all parts of the message itself, then | 3rd the footer as text/plain. I thought about this when the new MIME-aware Decorate.py code was written, and it's definitely a possibility. If you look at the code, you'll notice some placeholders where this could be added. My main reservation about doing this is about the best way to craft this new outer multipart/mixed message. In all the other cases, we're basically keeping the outer chrome intact, e.g. the headers from the originally sent message are basically passed through. But in the above approach, we'd have to wrap the original message in one of Mailman's own creation, so what do we use for things like the To, From, and Subject headers? Do we pass through Received headers, References header, etc? Those were all issues that I couldn't decide on, so I decided to punt for now. -Barry From m.ramsch@computer.org Wed Nov 13 01:24:18 2002 From: m.ramsch@computer.org (Martin Ramsch) Date: Wed, 13 Nov 2002 02:24:18 +0100 Subject: [Mailman-i18n] Re: Add header/footer to MIME multipart References: <007f01c284e9$8e3ddae0$6501a8c0@coco><018d01c28500$22eb10c0$6501a8c0@coco><000701c2850c$b5f5c5c0$6501a8c0@coco><004801c2850d$30323120$1e00a8c0@onsnet.org><005201c28514$88254820$6501a8c0@coco><000a01c2859d$ad5a9670$6501a8c0@coco><005601c2864a$40b76d60$6501a8c0@coco><001101c2870a$e6a263e0$6501a8c0@coco><005501c28723$c1501010$6501a8c0@coco><010601c28755$a0267500$6501a8c0@coco><00ce01c288b1$f715b8a0$8255bad9@solo> <15825.29632.754829.971333@gargle.gargle.HOWL> Message-ID: <002901c28ab3$66dddbb0$9d55bad9@solo> Barry A. Warsaw wrote: > | Another option for MIME multipart messages is to embed the > | message parts into a _new_ multipart/mixed structure which > | contains > | 1st the header as text/plain, then > | 2nd all parts of the message itself, then > | 3rd the footer as text/plain. [...] > My main reservation about doing this is about the best way to craft > this new outer multipart/mixed message. In all the other cases, we're > basically keeping the outer chrome intact, e.g. the headers from the > originally sent message are basically passed through. The same is possible here! You keep _all_ of the original header lines, just changing the MIME header lines, basically Content-Type and Content-Length Example, imagine you'd have this mail: Recieved: blablabla 1 Recieved: blablabla 2 ...many more headers... MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Some text about the Euro =A4 To add header and footer text as seperate MIME parts, you _just_ change the Content-Type header here (and delete or update Content-Length header, if present): Recieved: blablabla 1 Recieved: blablabla 2 ...many more headers... MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="choosesomethingunique" Put some explanatory text here for non-MIME-conformant mail clients. --choosesomethingunique Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Here goes the header text, with some schöne Umlauts, if you like --choosesomethingunique Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Some text about the Euro =A4 --choosesomethingunique Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Here goes the footer text --choosesomethingunique-- So it's pretty simple: just move the MIME header lines down into its new seperate part, leave all other header lines alone! Not too difficult :-) Regards, Martin PS: I just had a beer (or was it two, or four?) so fergive me any writing mitakes :) From loewis@informatik.hu-berlin.de Wed Nov 13 11:26:46 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 13 Nov 2002 12:26:46 +0100 Subject: [Mailman-i18n] Re: Add header/footer to MIME multipart In-Reply-To: <002901c28ab3$66dddbb0$9d55bad9@solo> References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> <005501c28723$c1501010$6501a8c0@coco> <010601c28755$a0267500$6501a8c0@coco> <00ce01c288b1$f715b8a0$8255bad9@solo> <15825.29632.754829.971333@gargle.gargle.HOWL> <002901c28ab3$66dddbb0$9d55bad9@solo> Message-ID: "Martin Ramsch" writes: > > My main reservation about doing this is about the best way to craft > > this new outer multipart/mixed message. In all the other cases, we're > > basically keeping the outer chrome intact, e.g. the headers from the > > originally sent message are basically passed through. [...] > So it's pretty simple: just move the MIME header lines down into > its new seperate part, leave all other header lines alone! > > Not too difficult :-) While it may be simple on paper or in a text editor, I believe Barry was talking about the changes needed in Mailman, given the class-and-instance structure of Mailman. Barry wants to create a new email.Message.Message around the existing message, which then would become the multipart/mixed message. However, I don't think this is needed: You could create a new Message, and copy the ._payload, and the content type to the new message; you would change the _payload of the existing message to be a list of the three parts (header, submessage, footer), and also change content type. That would leave the outer chrome intact, no? Regards, Martin From barry@python.org Wed Nov 13 19:32:51 2002 From: barry@python.org (Barry A. Warsaw) Date: Wed, 13 Nov 2002 14:32:51 -0500 Subject: [Mailman-i18n] Adding non-ASCII headers References: Message-ID: <15826.43235.596460.734686@gargle.gargle.HOWL> >>>>> "MvL" =3D=3D Martin v L=F6wis wr= ites: MvL> I just tried to configure the playground list to use MvL> non-ASCII headers, and failed. MvL> First, I tried to add Turkish letters, without having Turkish MvL> templates. This failed, and not surprisingly so: The MvL> admin/playground/nondigest form was encoded in us-ascii, so MvL> it was not capable of properly transmitting the header MvL> contents (it was surprising that Mailman sent out a garbage MvL> message, though). MvL> Then, I changed the list to Russian, and got a Koi8-r form, MvL> in which I successfully entered a Cyrillic text (this text is MvL> still configured at the moment). MvL> However, when sending a message in non-digest mode, neither a MvL> header nor a footer was added by mailman. Can somebody MvL> explain this behaviour? Mailman won't add by concatenation headers or footers to text/plain parts of the message that don't have a charset that matches the list's preferred charset (which is by fiat the charset assumed for the header and footer text). I suppose we could do a similar kind of multipart re-wrapping as is being proposed for adding headers and footers to multipart/.= -Barry From barry@python.org Wed Nov 13 19:39:55 2002 From: barry@python.org (Barry A. Warsaw) Date: Wed, 13 Nov 2002 14:39:55 -0500 Subject: [Mailman-i18n] Pipermail and non-English lists References: Message-ID: <15826.43659.281251.84968@gargle.gargle.HOWL> >>>>> "MvL" =3D=3D Martin v L=F6wis wr= ites: MvL> It appears that pipermail does not work will with the message MvL> catalogs. Please have a look at MvL> http://mail.python.org/pipermail/playground/ MvL> This HTML page is formatted as KOI-8R, but that encoding is MvL> nowhere declared. Really? When I use Moz1.1's "get page info" it tells me that the encoding is KOI8-R. Where would it get this information from? =20 MvL> More disturbingly, MvL> http://mail.python.org/pipermail/playground/2002-November/0000= 18.html MvL> has the body of the message encoded as UTF-8. However, the MvL> rest of the page is still encoded as KOI8-R. Yikes. MvL> It appears that we need either to recode the message in the MvL> encoding of the HTML header/footer, or recode the HTML MvL> header/footer to the encoding of body of the message (using MvL> character references where necessary). MvL> Which one would you prefer? I'm not sure it much matters, because those pages are statically created, so even changing the list's preferred language won't change the already generated archive pages. -Barry From wilane@omnet.sn Sat Nov 9 20:31:09 2002 From: wilane@omnet.sn (Ousmane Wilane) Date: Sat, 9 Nov 2002 20:31:09 +0000 Subject: [Mailman-i18n] Another fr champion In-Reply-To: <15814.58185.655937.793787@gargle.gargle.HOWL> References: <15814.58185.655937.793787@gargle.gargle.HOWL> Message-ID: <1036873869.3dcd708d49115@www.omnet.sn> Surlignage "Barry A. Warsaw" : > I wish you all the best in your new life adventures, and I can only > say that being a father is one of the most amazing and rewarding > experiences I've ever had. Thanks a lot. The little guy is now 4 days old, it's realy amazing :) > I hope you'll come back soon -- you've done a wonderful job on the > French translations. Thanks. I'll be back as soon as I can. > OW> I posted on traduc@traduc.org (fr language team) and > OW> mailman-fr@rezo.net to find a taker, I'll let you know as soon > OW> as I find another champion. > > Maybe we should sign up for Translation Project support? > -Barry I think that it's something to consider, the TP is very effective for finding volunteers. Cheers -- Ousmane Wilane --------------------------------------------------------------------- OMNET NetWork, the Net that sucks less. You deserve a FREE Network with vanishing to zero downtime, just ask! From barry@python.org Sat Nov 16 05:51:42 2002 From: barry@python.org (Barry A. Warsaw) Date: Sat, 16 Nov 2002 00:51:42 -0500 Subject: [Mailman-i18n] Another fr champion References: <15814.58185.655937.793787@gargle.gargle.HOWL> <1036873869.3dcd708d49115@www.omnet.sn> Message-ID: <15829.56558.682856.536040@gargle.gargle.HOWL> >>>>> "OW" == Ousmane Wilane writes: OW> Thanks a lot. The little guy is now 4 days old, it's realy OW> amazing :) I'm sure you know by now all the changes a little guy can go through in their first few days. I swear I never thought I'd talk about someone else poop so much. (I'll thankfully refrain from more graphic jokes.) OW> I think that it's something to consider, the TP is very OW> effective for finding volunteers. I think this is something we should seriously look into after the MM2.1 final release. -Barry From loewis@informatik.hu-berlin.de Sat Nov 16 18:49:46 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 16 Nov 2002 19:49:46 +0100 Subject: [Mailman-i18n] Pipermail and non-English lists In-Reply-To: <15826.43659.281251.84968@gargle.gargle.HOWL> References: <15826.43659.281251.84968@gargle.gargle.HOWL> Message-ID: barry@python.org (Barry A. Warsaw) writes: > MvL> http://mail.python.org/pipermail/playground/ > > MvL> This HTML page is formatted as KOI-8R, but that encoding is > MvL> nowhere declared. > > Really? When I use Moz1.1's "get page info" it tells me that the > encoding is KOI8-R. Where would it get this information from? I have no idea. Connected to mail.python.org. Escape character is '^]'. GET /pipermail/playground/ HTTP/1.0 HTTP/1.1 200 OK Date: Sat, 16 Nov 2002 18:47:31 GMT Server: Apache/1.3.27 (Unix) Last-Modified: Wed, 13 Nov 2002 22:54:55 GMT ETag: "1a00a9-100d-3dd2d83f" Accept-Ranges: bytes Content-Length: 4109 Connection: close Content-Type: text/html The Playground Archives As you can see, there is no indication of a charset. Perhaps Mozilla 1.1 does smart guessing? Mozilla 1.0 displays Mojibake. > MvL> It appears that we need either to recode the message in the > MvL> encoding of the HTML header/footer, or recode the HTML > MvL> header/footer to the encoding of body of the message (using > MvL> character references where necessary). > > MvL> Which one would you prefer? > > I'm not sure it much matters, because those pages are statically > created, so even changing the list's preferred language won't change > the already generated archive pages. It might matter for some Web browsers, which might be able to render one of these versions better than the other. For a conforming browser, it should not matter. Regards, Martin From barry@python.org Sun Nov 17 18:28:57 2002 From: barry@python.org (Barry A. Warsaw) Date: Sun, 17 Nov 2002 13:28:57 -0500 Subject: [Mailman-i18n] Re: Add header/footer to MIME multipart References: <007f01c284e9$8e3ddae0$6501a8c0@coco> <018d01c28500$22eb10c0$6501a8c0@coco> <000701c2850c$b5f5c5c0$6501a8c0@coco> <004801c2850d$30323120$1e00a8c0@onsnet.org> <005201c28514$88254820$6501a8c0@coco> <000a01c2859d$ad5a9670$6501a8c0@coco> <005601c2864a$40b76d60$6501a8c0@coco> <001101c2870a$e6a263e0$6501a8c0@coco> <005501c28723$c1501010$6501a8c0@coco> <010601c28755$a0267500$6501a8c0@coco> <00ce01c288b1$f715b8a0$8255bad9@solo> <15825.29632.754829.971333@gargle.gargle.HOWL> <002901c28ab3$66dddbb0$9d55bad9@solo> Message-ID: <15831.57321.172907.679708@gargle.gargle.HOWL> >>>>> "MvL" =3D=3D Martin v L=F6wis wr= ites: MvL> However, I don't think this is needed: You could create a new MvL> Message, and copy the ._payload, and the content type to the MvL> new message; you would change the _payload of the existing MvL> message to be a list of the three parts (header, submessage, MvL> footer), and also change content type. MvL> That would leave the outer chrome intact, no? 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 ones? I'm going to play around with a few things to see what makes sense, but this general idea should make it into b5. -Barry From loewis@informatik.hu-berlin.de Mon Nov 18 16:41:34 2002 From: loewis@informatik.hu-berlin.de (Martin v. Löwis) Date: Mon, 18 Nov 2002 17:41:34 +0100 Subject: [Mailman-i18n] Re: Add header/footer to MIME multipart Message-ID: Am Sonntag, 17 November 2002 schrieb barry@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 >ones? 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. Martin =================================================================== EASY and FREE access to your email anywhere: http://Mailreader.com/ =================================================================== From barry@python.org Mon Nov 18 16:46:14 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 18 Nov 2002 11:46:14 -0500 Subject: [Mailman-i18n] Re: Add header/footer to MIME multipart References: Message-ID: <15833.6486.95867.217071@gargle.gargle.HOWL> >>>>> "MvL" =3D=3D Martin v L=F6wis wr= ites: >> 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 ones? MvL> It think finding the minimum subset would be best: all MIME MvL> headers must be present (Content-Type, MvL> Content-transfer-encoding, perhaps Content-disposition, but MvL> not MIME-Version). All other headers belong to the outer MvL> chrome, AFAICT. Yep, that's actually what's implemented in cvs now. I copy any header starting with "Content-". Seems to work okay in my limited testing. Thanks, -Barry From barry@python.org Mon Nov 18 16:58:58 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 18 Nov 2002 11:58:58 -0500 Subject: [Mailman-i18n] Pipermail and non-English lists References: <15826.43659.281251.84968@gargle.gargle.HOWL> Message-ID: <15833.7250.743784.428770@gargle.gargle.HOWL> >>>>> "MvL" =3D=3D Martin v L=F6wis wr= ites: >> MvL> This HTML page is formatted as KOI-8R, but that encoding >> is MvL> nowhere declared. Really? When I use Moz1.1's "get >> page info" it tells me that the encoding is KOI8-R. Where >> would it get this information from? MvL> I have no idea. | Connected to mail.python.org. | Escape character is '^]'. | GET /pipermail/playground/ HTTP/1.0 | HTTP/1.1 200 OK | Date: Sat, 16 Nov 2002 18:47:31 GMT | Server: Apache/1.3.27 (Unix) | Last-Modified: Wed, 13 Nov 2002 22:54:55 GMT | ETag: "1a00a9-100d-3dd2d83f" | Accept-Ranges: bytes | Content-Length: 4109 | Connection: close | Content-Type: text/html | | | | The Playground Archives | | MvL> As you can see, there is no indication of a charset. Perhaps MvL> Mozilla 1.1 does smart guessing? Mozilla 1.0 displays MvL> Mojibake. Ah, I think it's a TOC problem, because individual articles have an http-equiv header indicating the proper encoding: -------------------- snip snip -------------------- % telnet mail.python.org 80 Trying 12.155.117.29... Connected to mail.python.org. Escape character is '^]'. GET /pipermail/playground/2002-November/000018.html HTTP/1.0 HTTP/1.1 200 OK Date: Mon, 18 Nov 2002 16:53:25 GMT Server: Apache/1.3.27 (Unix) Last-Modified: Mon, 18 Nov 2002 16:48:07 GMT ETag: "188314-8b0-3dd919c7" Accept-Ranges: bytes Content-Length: 2224 Connection: close Content-Type: text/html [Playground] Testing KOI8-R once more -------------------- snip snip -------------------- But it looks like the thread indices and the list archive overview pages either don't have http-equiv's or they're incorrect. I'll try to fix those. -Barry From barry@python.org Mon Nov 18 17:59:40 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 18 Nov 2002 12:59:40 -0500 Subject: [Mailman-i18n] Pipermail and non-English lists References: <15826.43659.281251.84968@gargle.gargle.HOWL> <15833.7250.743784.428770@gargle.gargle.HOWL> Message-ID: <15833.10892.8350.91462@gargle.gargle.HOWL> >>>>> "BAW" == Barry A Warsaw writes: BAW> But it looks like the thread indices and the list archive BAW> overview pages either don't have http-equiv's or they're BAW> incorrect. BAW> I'll try to fix those. Ok, that was fun. :/ I fixed things so that the index.html page adds an http-equiv header with the proper charset information, but that wasn't working as expected. Dumping the page source indeed showed the proper http-equiv meta tag, but the page was still being displayed incorrectly. Turns out, my Apache config had this line in it: AddDefaultCharset ISO-8859-1 And because these pages are vended right from the file system, Apache dutifully adds "charset=iso-8859-1" to the Content-Type header. This is documented to override the meta tag setting, so that part works correctly . A weird browser incompatibility exists between Moz1.1 and NS4.7x (all I've tried so far). Moz will always believe the http header, trying to display the page in iso-8859-1, which isn't what we want. NS will do the same thing -- until you hit the back button! Then it picks up the koi8-r charset in the meta tag (I surmise) and displays it in the Russian charset. The solution was to comment out this line (not withstanding the security scare hinted at in the config file, but not in the documentation), or set it to AddDefaultCharset off which is the default. Now it seems to work just fine. I guess I have to add this to the docs. Hmm, maybe this is another reason to want a cgi in front of even public archives? I'll check in a bunch of changes as soon as SF's cvs comes back on-line :( -Barry From m.ramsch@computer.org Mon Nov 18 21:21:44 2002 From: m.ramsch@computer.org (Martin Ramsch) Date: Mon, 18 Nov 2002 22:21:44 +0100 Subject: [Mailman-i18n] Re: Add header/footer to MIME multipart References: <15833.6486.95867.217071@gargle.gargle.HOWL> Message-ID: <007e01c28f48$83836980$2e55bad9@solo> QmFycnkgQS4gV2Fyc2F3IDxiYXJyeUBweXRob24ub3JnPiB3cm90ZToNCg0KPiAgICAgTXZMPiBJ dCB0aGluayBmaW5kaW5nIHRoZSBtaW5pbXVtIHN1YnNldCB3b3VsZCBiZSBiZXN0OiBhbGwgTUlN RQ0KPiAgICAgTXZMPiBoZWFkZXJzIG11c3QgYmUgcHJlc2VudCAoQ29udGVudC1UeXBlLA0KPiAg ICAgTXZMPiBDb250ZW50LXRyYW5zZmVyLWVuY29kaW5nLCBwZXJoYXBzIENvbnRlbnQtZGlzcG9z aXRpb24sIGJ1dA0KPiAgICAgTXZMPiBub3QgTUlNRS1WZXJzaW9uKS4gQWxsIG90aGVyIGhlYWRl cnMgYmVsb25nIHRvIHRoZSBvdXRlcg0KPiAgICAgTXZMPiBjaHJvbWUsIEFGQUlDVC4NCj4gDQo+ IFllcCwgdGhhdCdzIGFjdHVhbGx5IHdoYXQncyBpbXBsZW1lbnRlZCBpbiBjdnMgbm93LiAgSSBj b3B5IGFueSBoZWFkZXINCj4gc3RhcnRpbmcgd2l0aCAiQ29udGVudC0iLiAgU2VlbXMgdG8gd29y ayBva2F5IGluIG15IGxpbWl0ZWQgdGVzdGluZy4NCg0KUkZDIDIwNDUgaHR0cDovL3d3dy5pZXRm Lm9yZy9yZmMvcmZjMjA0NS50eHQgYWxzbyBzdGF0ZXM6DQoNCnwgMi40LiAgRW50aXR5DQpbLi4u XQ0KfCBbLi4uXSBvbmx5IHRob3NlIGZpZWxkcyB3aG9zZSBuYW1lcyBiZWdpbiB3aXRoICJjb250 ZW50LSIgYWN0dWFsbHkNCnwgaGF2ZSBhbnkgTUlNRS1yZWxhdGVkIG1lYW5pbmcuDQoNClNvIHlv dXIgZGVjaXNpb24gaXMgcGVyZmVjdGx5IHJpZ2h0ISA6KQ0KDQpDaGVlcnMsDQogIE1hcnRpbg0K From barry@python.org Mon Nov 18 23:07:02 2002 From: barry@python.org (Barry A. Warsaw) Date: Mon, 18 Nov 2002 18:07:02 -0500 Subject: [Mailman-i18n] Recode pipermail templates References: <200211060832.gA68WgRE008907@paros.informatik.hu-berlin.de> Message-ID: <15833.29334.567234.739929@gargle.gargle.HOWL> >>>>> "MvL" == Martin von Loewis writes: MvL> I made a patch MvL> http://sourceforge.net/tracker/index.php?func=detail&aid=634303&group_id=103&atid=300103 MvL> which recodes the pipermail HTML templates and gettext MvL> messages if the charset of the page-under-creation is MvL> different from the charset of the templates. It uses HTML MvL> character references if the template characters are not MvL> supported in the target character set, so it should work fine MvL> if the template charset and the target charset are both known MvL> to Python. If the template charset and the target charset MvL> match, no conversion happens. If the message has no decared MvL> charset, but the templates use a non-ASCII charset, a META MvL> tag is now inserted into the page. I posted a follow up to this patch about a simplification that I think works just as well. I've now committed all the changes to the archiver than I think is necessary to get it to properly behave when the charsets of the content is different than the charsets of the template. But this stuff always makes my brain hurt and I'm not 100% sure I've gotten everything right, or everything that's needed. Could someone: - Please double check all the changes that are in the archiver in current cvs. I think what's there will become beta5 unless something comes up in the next few hours. - Are there any other changes to the archiver needed to resolve the i18n issues? If so, please let me know. - Is patch #634303 still necessary? I think not, and I'd like to close it. Thanks, -Barry From james@daa.com.au Tue Nov 19 00:49:23 2002 From: james@daa.com.au (James Henstridge) Date: Tue, 19 Nov 2002 08:49:23 +0800 Subject: [Mailman-i18n] Pipermail and non-English lists References: <15826.43659.281251.84968@gargle.gargle.HOWL> <15833.7250.743784.428770@gargle.gargle.HOWL> <15833.10892.8350.91462@gargle.gargle.HOWL> Message-ID: <3DD98A93.30700@daa.com.au> Barry A. Warsaw wrote: >>>>>>"BAW" == Barry A Warsaw writes: >>>>>> >>>>>> > > BAW> But it looks like the thread indices and the list archive > BAW> overview pages either don't have http-equiv's or they're > BAW> incorrect. > > BAW> I'll try to fix those. > >Ok, that was fun. :/ > >I fixed things so that the index.html page adds an http-equiv header >with the proper charset information, but that wasn't working as >expected. Dumping the page source indeed showed the proper http-equiv >meta tag, but the page was still being displayed incorrectly. > >Turns out, my Apache config had this line in it: > > AddDefaultCharset ISO-8859-1 > >And because these pages are vended right from the file system, Apache >dutifully adds "charset=iso-8859-1" to the Content-Type header. This >is documented to override the meta tag setting, so that part works >correctly . > >A weird browser incompatibility exists between Moz1.1 and NS4.7x (all >I've tried so far). Moz will always believe the http header, trying >to display the page in iso-8859-1, which isn't what we want. NS will >do the same thing -- until you hit the back button! Then it picks up >the koi8-r charset in the meta tag (I surmise) and displays it in the >Russian charset. > >The solution was to comment out this line (not withstanding the >security scare hinted at in the config file, but not in the >documentation), or set it to > > AddDefaultCharset off > >which is the default. Now it seems to work just fine. I guess I have >to add this to the docs. > >Hmm, maybe this is another reason to want a cgi in front of even >public archives? > >I'll check in a bunch of changes as soon as SF's cvs comes back >on-line :( > > I ran into this same issue for the GNOME reference documentation. We had our stylesheets set up to output UTF-8 docs, which caused problems when placed on a web server configured like this. It looks like the default Apache 2.0 config includes this directive (and so do a number of distributors' apache-1.3 packages), so we decided to switch back to outputting ISO-8859-1, and encoding other codepoints as character references. The comments in the config file say that they add the charset to the content-type to work around security bugs in some web browsers. Having it set is a bit annoying, but we ended up deciding to work around this common configuration. James. -- Email: james@daa.com.au | Linux.conf.au http://linux.conf.au/ WWW: http://www.daa.com.au/~james/ | Jan 22-25 Perth, Western Australia. From barry@python.org Tue Nov 19 06:23:48 2002 From: barry@python.org (Barry A. Warsaw) Date: Tue, 19 Nov 2002 01:23:48 -0500 Subject: [Mailman-i18n] Re: Add header/footer to MIME multipart References: <15833.6486.95867.217071@gargle.gargle.HOWL> <007e01c28f48$83836980$2e55bad9@solo> Message-ID: <15833.55540.498667.866270@gargle.gargle.HOWL> >>>>> "MR" == Martin Ramsch writes: MR> So your decision is perfectly right! :) Cool! :) -Barry From domains@keying.net Wed Nov 20 08:42:54 2002 From: domains@keying.net (Domain Monitor) Date: Wed, 20 Nov 2002 00:42:54 -0800 (PST) Subject: [Mailman-i18n] i18n.org is available. Message-ID: <9392051.1037781774714.JavaMail.hongwei@localhost> Hi, The i18n.org is just released. If you are interested in, please register it with http://www.keying.net as soon as possible. Thank you. From a.zeini@farsikde.org Wed Nov 20 18:39:55 2002 From: a.zeini@farsikde.org (Arash Zeini) Date: Wed, 20 Nov 2002 22:09:55 +0330 Subject: [Mailman-i18n] Another fr champion In-Reply-To: <1036873869.3dcd708d49115@www.omnet.sn> References: <15814.58185.655937.793787@gargle.gargle.HOWL> <1036873869.3dcd708d49115@www.omnet.sn> Message-ID: <200211202209.55747.a.zeini@farsikde.org> On Sunday 10 November 2002 00:01, Ousmane Wilane wrote: > Surlignage "Barry A. Warsaw" : > > > > > I wish you all the best in your new life adventures, and I can only > > say that being a father is one of the most amazing and rewarding > > experiences I've ever had. > > Thanks a lot. The little guy is now 4 days old, it's realy amazing :) How wonderful! Congratulations and all the Best to you and your girlfrien= d. A=20 wonderful adventure has began for you.=20 Enjoy it! Arash --=20 The FarsiKDE Project www.farsikde.org From cerdil@ttnet.net.tr Thu Nov 21 09:29:27 2002 From: cerdil@ttnet.net.tr (shawn Erdil) Date: Thu, 21 Nov 2002 11:29:27 +0200 Subject: [Mailman-i18n] charset impovements Message-ID: <001b01c29140$7d6bdab0$6401a8c0@coco> İ 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 ? thank you shawn erdil -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-i18n/attachments/20021121/d145fb22/attachment.html From loewis@informatik.hu-berlin.de Thu Nov 21 11:05:16 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 21 Nov 2002 12:05:16 +0100 Subject: [Mailman-i18n] Pipermail and non-English lists In-Reply-To: <15833.10892.8350.91462@gargle.gargle.HOWL> References: <15826.43659.281251.84968@gargle.gargle.HOWL> <15833.7250.743784.428770@gargle.gargle.HOWL> <15833.10892.8350.91462@gargle.gargle.HOWL> Message-ID: barry@python.org (Barry A. Warsaw) writes: > Hmm, maybe this is another reason to want a cgi in front of even > public archives? No, I don't think so. Instead, I think the security warning is just misguided. It may be possible to cause security violations by playing tricks with the charset, but in all cases, this is somebody else's bug if these tricks work, not the bug of the web server. I would add this issue to the installation instructions. People who use non-Latin-1 regularly will notice quickly that they get mojibake. Regards, Martin From loewis@informatik.hu-berlin.de Thu Nov 21 11:06:24 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 21 Nov 2002 12:06:24 +0100 Subject: [Mailman-i18n] charset impovements In-Reply-To: <001b01c29140$7d6bdab0$6401a8c0@coco> References: <001b01c29140$7d6bdab0$6401a8c0@coco> Message-ID: "shawn Erdil" writes: > can we expect, considerable improvement in the beta 5 > version,regarding charset in archiving and message header,footer > output in non digest sends ? I believe so, yes. Regards, Martin From tkikuchi@is.kochi-u.ac.jp Thu Nov 21 12:40:03 2002 From: tkikuchi@is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu, 21 Nov 2002 21:40:03 +0900 Subject: [Mailman-i18n] Pipermail and non-English lists References: <15826.43659.281251.84968@gargle.gargle.HOWL> <15833.7250.743784.428770@gargle.gargle.HOWL> <15833.10892.8350.91462@gargle.gargle.HOWL> Message-ID: <3DDCD423.7060604@is.kochi-u.ac.jp> Hi, > I would add this issue to the installation instructions. People who > use non-Latin-1 regularly will notice quickly that they get mojibake. Where did you learn japanese? Or, is this (mojibake) already an internaltional word? BTW, I propose each language define 'alternative charsets' which are safely convertible to the 'standard charset' for the language. On entry to the global pipeline, incoming message is examined and converted to the stdcharset if possible. Name the module Entry.py and rough algorithm may be like this; if mlist.preferred_language has altcharsets \ and msg.charset in altcharsets: msg = unicode(msg, msg.charset).encode(stdcharset) 'replace' may be needed for safety. Japanese need this because there are three charsets widely used. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From loewis@informatik.hu-berlin.de Thu Nov 21 12:47:58 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 21 Nov 2002 13:47:58 +0100 Subject: [Mailman-i18n] Pipermail and non-English lists In-Reply-To: <3DDCD423.7060604@is.kochi-u.ac.jp> References: <15826.43659.281251.84968@gargle.gargle.HOWL> <15833.7250.743784.428770@gargle.gargle.HOWL> <15833.10892.8350.91462@gargle.gargle.HOWL> <3DDCD423.7060604@is.kochi-u.ac.jp> Message-ID: Tokio Kikuchi writes: > Where did you learn japanese? Or, is this (mojibake) already an > internaltional word? I'm using it as an international word. I don't think there is an English word for that phenomenon ("garbage" is not really equivalent, in my understanding) - for that matter, there isn't a German word for it, either. It happened that the Japanese apparently are confronted with garbage characters so often that they created a new word, and I happily accept it as a terminus technicus :-) Regards, Martin From barry@python.org Thu Nov 21 13:41:27 2002 From: barry@python.org (Barry A. Warsaw) Date: Thu, 21 Nov 2002 08:41:27 -0500 Subject: [Mailman-i18n] Pipermail and non-English lists References: <15826.43659.281251.84968@gargle.gargle.HOWL> <15833.7250.743784.428770@gargle.gargle.HOWL> <15833.10892.8350.91462@gargle.gargle.HOWL> <3DD98A93.30700@daa.com.au> Message-ID: <15836.57991.374606.980739@gargle.gargle.HOWL> >>>>> "JH" == James Henstridge writes: JH> It looks like the default Apache 2.0 config includes this JH> directive (and so do a number of distributors' apache-1.3 JH> packages), so we decided to switch back to outputting JH> ISO-8859-1, and encoding other codepoints as character JH> references. Ouch. :( JH> The comments in the config file say that they add the charset JH> to the content-type to work around security bugs in some web JH> browsers. Yeah, but the online docs make no mention of this. What specifically are the security vulnerabilities? -Barry From barry@python.org Thu Nov 21 13:43:45 2002 From: barry@python.org (Barry A. Warsaw) Date: Thu, 21 Nov 2002 08:43:45 -0500 Subject: [Mailman-i18n] Pipermail and non-English lists References: <15826.43659.281251.84968@gargle.gargle.HOWL> <15833.7250.743784.428770@gargle.gargle.HOWL> <15833.10892.8350.91462@gargle.gargle.HOWL> Message-ID: <15836.58129.285092.290286@gargle.gargle.HOWL> >>>>> "MvL" =3D=3D Martin v L=F6wis wr= ites: >> Hmm, maybe this is another reason to want a cgi in front of >> even public archives? MvL> No, I don't think so. Instead, I think the security warning MvL> is just misguided. It may be possible to cause security MvL> violations by playing tricks with the charset, but in all MvL> cases, this is somebody else's bug if these tricks work, not MvL> the bug of the web server. Can you describe exactly what kind of security violations might occur? MvL> I would add this issue to the installation MvL> instructions. People who use non-Latin-1 regularly will MvL> notice quickly that they get mojibake. Done. I don't know what mojibake is, but it sounds like I dn't want it! Maybe "shmutz" is a good enough working translation? :) -Barry From barry@python.org Thu Nov 21 13:44:17 2002 From: barry@python.org (Barry A. Warsaw) Date: Thu, 21 Nov 2002 08:44:17 -0500 Subject: [Mailman-i18n] charset impovements References: <001b01c29140$7d6bdab0$6401a8c0@coco> Message-ID: <15836.58161.626500.800646@gargle.gargle.HOWL> >>>>> "MvL" =3D=3D Martin v L=F6wis wr= ites: >> can we expect, considerable improvement in the beta 5 >> version,regarding charset in archiving and message >> header,footer output in non digest sends ? MvL> I believe so, yes. Phew! So the b5 changes look good? -Barry From barry@python.org Thu Nov 21 13:47:46 2002 From: barry@python.org (Barry A. Warsaw) Date: Thu, 21 Nov 2002 08:47:46 -0500 Subject: [Mailman-i18n] Pipermail and non-English lists References: <15826.43659.281251.84968@gargle.gargle.HOWL> <15833.7250.743784.428770@gargle.gargle.HOWL> <15833.10892.8350.91462@gargle.gargle.HOWL> <3DDCD423.7060604@is.kochi-u.ac.jp> Message-ID: <15836.58370.719926.318834@gargle.gargle.HOWL> >>>>> "TK" == Tokio Kikuchi writes: >> I would add this issue to the installation instructions. People >> who use non-Latin-1 regularly will notice quickly that they get >> mojibake. TK> BTW, I propose each language define 'alternative charsets' TK> which are safely convertible to the 'standard charset' for the TK> language. On entry to the global pipeline, incoming message is TK> examined and converted to the stdcharset if possible. Name the TK> module Entry.py and rough algorithm may be like this; | if mlist.preferred_language has altcharsets \ | and msg.charset in altcharsets: | msg = unicode(msg, msg.charset).encode(stdcharset) TK> 'replace' may be needed for safety. TK> Japanese need this because there are three charsets widely TK> used. Ouch. This sounds like something we probably need to do if Japanese archives are going to come out right, but it also sounds like a fair bit of work. Why does it need to be part of the global pipeline? I'd imagine its only necessary where email messages might get displayed in http, so that'd mean Pipermail and the admindb. Most languages aren't going to need alternative charsets, right? I'm guessing Japanese and perhaps other Asian languages (but I don't know for sure). What would be the value of altcharsets for Japanese? -Barry From alessio@albourne.com Thu Nov 21 14:31:25 2002 From: alessio@albourne.com (Alessio Bragadini) Date: 21 Nov 2002 16:31:25 +0200 Subject: [Mailman-i18n] Pipermail and non-English lists In-Reply-To: <15836.58370.719926.318834@gargle.gargle.HOWL> References: <15826.43659.281251.84968@gargle.gargle.HOWL> <15833.7250.743784.428770@gargle.gargle.HOWL> <15833.10892.8350.91462@gargle.gargle.HOWL> <3DDCD423.7060604@is.kochi-u.ac.jp> <15836.58370.719926.318834@gargle.gargle.HOWL> Message-ID: <1037889085.29708.781.camel@iris> On Thu, 2002-11-21 at 15:47, Barry A. Warsaw wrote: > Most languages aren't going to need alternative charsets, right? Actually depends on your idea of alternative charsets, because now the 12 Euro-zone European countries should use ISO-8859-15 instead of ISO-8859-1: 15 is 1 changed with the euro symbol, but not a lot of users use the "new one" yet. Does this qualify as "two alternative charsets" for Italian and others. Sorry if I'm completely offtopic... :-) -- 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 james@daa.com.au Thu Nov 21 15:36:12 2002 From: james@daa.com.au (James Henstridge) Date: Thu, 21 Nov 2002 23:36:12 +0800 Subject: [Mailman-i18n] Pipermail and non-English lists References: <15826.43659.281251.84968@gargle.gargle.HOWL> <15833.7250.743784.428770@gargle.gargle.HOWL> <15833.10892.8350.91462@gargle.gargle.HOWL> <3DD98A93.30700@daa.com.au> <15836.57991.374606.980739@gargle.gargle.HOWL> Message-ID: <3DDCFD6C.8080007@daa.com.au> Barry A. Warsaw wrote: >>>>>>"JH" == James Henstridge writes: >>>>>> >>>>>> > > JH> It looks like the default Apache 2.0 config includes this > JH> directive (and so do a number of distributors' apache-1.3 > JH> packages), so we decided to switch back to outputting > JH> ISO-8859-1, and encoding other codepoints as character > JH> references. > >Ouch. :( > Well, our API docs are mainly 7-bit ascii with the occasional code point out of that range, so it wasn't that bad. It would be much worse for mailing list archives for a Japanese list for instance, so it might not be the solution you want ... > > JH> The comments in the config file say that they add the charset > JH> to the content-type to work around security bugs in some web > JH> browsers. > >Yeah, but the online docs make no mention of this. What specifically >are the security vulnerabilities? > > There is a fairly lengthy comment above the directive in the default config file: # Specify a default charset for all pages sent out. This is # always a good idea and opens the door for future internationalisation # of your web site, should you ever want it. Specifying it as # a default does little harm; as the standard dictates that a page # is in iso-8859-1 (latin1) unless specified otherwise i.e. you # are merely stating the obvious. There are also some security # reasons in browsers, related to javascript and URL parsing # which encourage you to always set a default char set. Of course, the comment about it being harmless is obviously wrong if you were expecting the charset to be detected from the document content. There is some discussion of the problem as it relates to Apache here: http://httpd.apache.org/info/css-security/apache_specific.html The idea is to prevent external data from setting the charset to something weird in order to sneak malicious code past content checks (it gives the example of UTF-7 encoded data, which might pass through many filters). I don't think that it is an issue here, as the untrusted information (message body) can't affect the charset on the archive pages. Since the AddDefaultCharset directive can be used in a section of the apache config file. We could include it in the sample httpd.conf fragment for setting up the archives. Something like this: Alias /pipermail/ /home/mailman/archives/public/ Options Indexes FollowSymLinks AllowOverride None Order allow,deny Allow from all AddDefaultCharset Off Doing that and making a note of it in the upgrade notes should be enough. James. -- Email: james@daa.com.au | Linux.conf.au http://linux.conf.au/ WWW: http://www.daa.com.au/~james/ | Jan 22-25 Perth, Western Australia. From loewis@informatik.hu-berlin.de Thu Nov 21 17:18:47 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 21 Nov 2002 18:18:47 +0100 Subject: [Mailman-i18n] Pipermail and non-English lists In-Reply-To: <15836.57991.374606.980739@gargle.gargle.HOWL> References: <15826.43659.281251.84968@gargle.gargle.HOWL> <15833.7250.743784.428770@gargle.gargle.HOWL> <15833.10892.8350.91462@gargle.gargle.HOWL> <3DD98A93.30700@daa.com.au> <15836.57991.374606.980739@gargle.gargle.HOWL> Message-ID: barry@python.org (Barry A. Warsaw) writes: > Yeah, but the online docs make no mention of this. What specifically > are the security vulnerabilities? You can arrange for "cross-site scripting". If you manage to put UTF-7 into some page, utf-7 decoding this could result in, say, The server-side filter may fail to detect the markup in the input, as it isn't prepared to see encoding which aren't ASCII-compatible. You have to bend your mind quite a bit, to make a number of unreasonable assumptions, for this to result in a successful attack. See http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/news/csoverv.asp for Microsofts explanation of this issue. Regards, Martin From loewis@informatik.hu-berlin.de Thu Nov 21 17:24:44 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 21 Nov 2002 18:24:44 +0100 Subject: [Mailman-i18n] Pipermail and non-English lists In-Reply-To: <15836.58129.285092.290286@gargle.gargle.HOWL> References: <15826.43659.281251.84968@gargle.gargle.HOWL> <15833.7250.743784.428770@gargle.gargle.HOWL> <15833.10892.8350.91462@gargle.gargle.HOWL> <15836.58129.285092.290286@gargle.gargle.HOWL> Message-ID: barry@python.org (Barry A. Warsaw) writes: > Done. I don't know what mojibake is, but it sounds like I dn't want > it! Maybe "shmutz" is a good enough working translation? :) Yes, in typesetting, "Schmutz" might be indeed a translation for "moji-bake". See http://www.tuxedo.org/~esr/jargon/html/entry/mojibake.htm for the jargon file entry. Regards, Martin From loewis@informatik.hu-berlin.de Thu Nov 21 17:58:48 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 21 Nov 2002 18:58:48 +0100 Subject: [Mailman-i18n] Pipermail and non-English lists In-Reply-To: <15836.58370.719926.318834@gargle.gargle.HOWL> References: <15826.43659.281251.84968@gargle.gargle.HOWL> <15833.7250.743784.428770@gargle.gargle.HOWL> <15833.10892.8350.91462@gargle.gargle.HOWL> <3DDCD423.7060604@is.kochi-u.ac.jp> <15836.58370.719926.318834@gargle.gargle.HOWL> Message-ID: barry@python.org (Barry A. Warsaw) writes: > TK> Japanese need this because there are three charsets widely > TK> used. > > Ouch. This sounds like something we probably need to do if Japanese > archives are going to come out right, but it also sounds like a fair > bit of work. I'm not so sure this is necessary. For forwarding the messages, header and footer would just become different parts right now. Correct? That may not be perfect, but I think it will work. > Why does it need to be part of the global pipeline? I'd imagine its > only necessary where email messages might get displayed in http, so > that'd mean Pipermail and the admindb. Even for the archives, I'm not so sure it is needed. If the message is in a different encoding than the list's preferred encoding, you now recode the message to the list's encoding. For the Japanese encodings, this should work mostly without problems. > Most languages aren't going to need alternative charsets, right? Increasingly wrong. We Germans had been using latin-1 exclusively for some time, but now we also find cp1252, iso-8859-15 (latin-9), and utf-8 being used. > I'm guessing Japanese and perhaps other Asian languages (but I don't > know for sure). What would be the value of altcharsets for > Japanese? iso-2022-jp, eucJP, shift_jis, cp932, with various aliases (essentially, the encodings supported by JapaneseCodecs). Regards, Martin From loewis@informatik.hu-berlin.de Thu Nov 21 18:35:40 2002 From: loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) Date: 21 Nov 2002 19:35:40 +0100 Subject: [Mailman-i18n] charset impovements In-Reply-To: <15836.58161.626500.800646@gargle.gargle.HOWL> References: <001b01c29140$7d6bdab0$6401a8c0@coco> <15836.58161.626500.800646@gargle.gargle.HOWL> Message-ID: barry@python.org (Barry A. Warsaw) writes: > So the b5 changes look good? I haven't actually looked at the changes yet.=20 I just tested them, and there are still problems. In particular, the generation of multipart messages seems to corrupt data. In my recent Test1 message, http://mail.python.org/pipermail/playground/2002-November/000028.html the additional header was transmitted as --------------------------------------------- Content-Type: text/plain; charset=3D"us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Cyrillic header text: =C6=D5=CE=CB=D4=C9=CF=CE -------------------------------------------- I think the MIME-Version does not belong there (not sure though), and the charset is wrong (should have been koi8-r). Test message 2 was worse: http://mail.python.org/pipermail/playground/2002-November/000029.html should read 'This message should be encoded in koi8-r.\r\n\xc1\xc2\xd7\xc7\xc4\xc5\xd6\= r\n\r\n' instead. As you can see in the .mbox file, the original message still had the encoding as base64 and koi8-r. The archiving incorrectly displays the base64 data; the message sent out misses the charset on the primary part (even though the transfer encoding was included). Test message 3 was processed correctly, MIME-wise, except that header and footer have the encoding incorrect. Test 4 is both archived incorrectly and sent out incorrectly. So I do think there are considerable improvements, just new bugs as well. Regards, Martin From tkikuchi@is.kochi-u.ac.jp Fri Nov 22 00:19:17 2002 From: tkikuchi@is.kochi-u.ac.jp (Tokio Kikuchi) Date: Fri, 22 Nov 2002 09:19:17 +0900 Subject: [Mailman-i18n] Pipermail and non-English lists References: <15826.43659.281251.84968@gargle.gargle.HOWL> <15833.7250.743784.428770@gargle.gargle.HOWL> <15833.10892.8350.91462@gargle.gargle.HOWL> <3DDCD423.7060604@is.kochi-u.ac.jp> <15836.58370.719926.318834@gargle.gargle.HOWL> Message-ID: <3DDD7805.90503@is.kochi-u.ac.jp> Hi, > Why does it need to be part of the global pipeline? I'd imagine its > only necessary where email messages might get displayed in http, so > that'd mean Pipermail and the admindb. Because there may arise many occasions to display or decorate in the http/mail services, I want to convert the charset only once. I also use namazu for indexing the archive and it is convenient if charset is unique and not containing unicode. > Most languages aren't going to need alternative charsets, right? I'm > guessing Japanese and perhaps other Asian languages (but I don't know > for sure). What would be the value of altcharsets for Japanese? Since we set 'euc-jp' as the standard charset for japanese, remainings are 'iso-2022-jp', 'shift_jis' and 'cp932'. Here is my version of Entry.py which is going to be part of a japanese patch I am going to release. I need to write Exit.py (or something) because 'iso-2022-jp' is the de-facto standard for japanese mail. =========================================== from Mailman import Message, mm_cfg from email.Header import decode_header import re _ = i18n._ def get_header_decoded(h): # decode mime header AND convert it to standard charset if # alternate charset exists. h = decode_header(h) hs = '' spc = '' for (s, c) in h: if c and c in altcharsets: s = unicode(s, c, 'replace').encode(stdcharset) hs = hs + spc + s if c == None or c == 'us-ascii': spc = ' ' else: spc = '' return hs global stdcharset, altcharsets lang = mlist.preferred_language stdcharset = mm_cfg.LC_DESCRIPTIONS[lang][1] try: altcharsets = mm_cfg.LC_DESCRIPTIONS[lang][2] except: altcharsets = None # hs = get_header_decoded(msg.get('subject', _('no subject'))) msgdata['subject'] = hs del msg['subject'] msg['Subject'] = hs # hs = get_header_decoded(msg['from']) msgdata['from'] = hs msg['X-MMOriginal-From'] = msg['from'] del msg['from'] msg['From'] = hs # if altcharsets: for part in msg.walk(): ctype = part.get_type() m = re.search(r'charset=["\']?([\w_-]+)', msg['content-type'], re.I) if m: charset = m.group(1).lower() else: charset = 'us-ascii' # charset = part.get_charset() if charset in altcharsets: u = unicode(part.get_payload(decode=1), charset, 'replace') part.set_payload(u.encode(stdcharset)) # set_charset cannot be used here for it may automatically # convert to mail-standard charset. del part['content-type'] part['Content-Type'] = 'text/plain; charset=%s' % stdcharset ================================================= With this Entry.py, you only have to check 'no subject' once. I am going to upload this on SF when the exit part was done. It may be japanese specific but I will try it to be i18n as much as possible. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From jgon7@yahoo.com Fri Nov 22 18:37:43 2002 From: jgon7@yahoo.com (Jaime Gonzalez) Date: Fri, 22 Nov 2002 10:37:43 -0800 (PST) Subject: [Mailman-i18n] Translation.... Message-ID: <20021122183743.92041.qmail@web14611.mail.yahoo.com> Hi 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.... Greetings $ecrets 2 $uccess Inc. Check out the information that will unlock your doors to success and money. IT'S FREE!! http://www.secrets2success.com/special217640/index.html --------------------------------- Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now-------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-i18n/attachments/20021122/2e333c6a/attachment.html From danny@terweij.nl Mon Nov 25 01:54:38 2002 From: danny@terweij.nl (Danny Terweij) Date: Mon, 25 Nov 2002 02:54:38 +0100 Subject: [Mailman-i18n] Re: [Mailman-Users] Using CSS for all pages References: <15841.1951.614223.277845@gargle.gargle.HOWL> <15841.32927.210512.727172@gargle.gargle.HOWL> Message-ID: <004701c29425$9cbdf230$1e00a8c0@onsnet.org> From: "Barry A. Warsaw" > 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 :) Danny Terweij Dutch Translator 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 dev list) From barry@python.org Wed Nov 27 16:42:22 2002 From: barry@python.org (Barry A. Warsaw) Date: Wed, 27 Nov 2002 11:42:22 -0500 Subject: [Mailman-i18n] The plan for 2.1 Message-ID: <15844.62958.645219.294861@gargle.gargle.HOWL> 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: beta6: 02-Dec-2002 rc1: 09-Dec-2002 rc2: 16-Dec-2002 (if necessary) final: 23-Dec-2002 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, -Barry From danny@terweij.nl Wed Nov 27 17:46:56 2002 From: danny@terweij.nl (Danny Terweij) Date: Wed, 27 Nov 2002 18:46:56 +0100 Subject: [Mailman-i18n] The plan for 2.1 References: <15844.62958.645219.294861@gargle.gargle.HOWL> Message-ID: <108001c2963c$fac0d1e0$1e00a8c0@onsnet.org> From: "Barry A. Warsaw" > 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. Nice schedule. The next weeks i am going to translate more than i did :) Danny Terweij. From bojan@trust-b.com Thu Nov 28 13:50:02 2002 From: bojan@trust-b.com (Bojan Suzic) Date: Thu, 28 Nov 2002 14:50:02 +0100 Subject: [Mailman-i18n] new language for 2.1(b) Message-ID: <006c01c296e5$0f779e90$3a42fcc3@ooppq> Hello. I have made Serbian translation of Mailman 2.1b templates (utf-8). Where I should send them? Regards, Bojan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-i18n/attachments/20021128/75685326/attachment.html