[Mailman-i18n] how to encode in iso-8859-9 charset
shawn Erdil
cerdil@ttnet.net.tr
Tue Nov 5 08:49:13 2002
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" <loewis@informatik.hu-berlin.de>
To: "shawn Erdil" <cerdil@ttnet.net.tr>
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
>
More information about the Mailman-i18n
mailing list