Hi,
I searched the support forums but didn't find a solution for the following problem:
Because my site is in German language I have very much accented characters (umlauts) in the descriptions of the links. When sending out a newsletter I often get complaints that the umlaut characters are unreadable because they are changed to '=E4' (for 'ä') and so on. What makes this even worse is that I provide a link to 'search.cgi?query=&ID=123' and the equal sign gets converted, too, so the link becomes something like that: 'search.cgi?query=3D&ID=3D2=123' which obviously doesn't work.
Apparently this is not the case for all recipients - the mail I and many others receive, is displayed absolutely correct.
I guess this must have something to do with the setting for 'Content-Transfer-Encoding' which is set to 'quoted printable' (I am using smtp, not sendmail).
So I changed the corresponding line in Bulkmail.pm from
print $out "Content-Transfer-Encoding: quoted-printable";
to
print $out "Content-Transfer-Encoding: 8bit";
which - as I understand - should do no encoding at all.
But with that setting the test mails I sent to myself via 'Mass Mail' -> 'Selected Users' get converted exactly the way some of my users are complaining about.
So I have to chose from
Content-Transfer-Encoding: quoted-printable -> some users get scrambled umlauts
or
Content-Transfer-Encoding: 8bit -> I get scrambled umlauts myself (not knowing if the complaining users would get correct ones)
Unfortunately I have no idea how to tell the smtp server or the script to do an encoding that makes sure that everybody will get correct umlauts.
Does anyone else use umlauts in the Links newsletter?
What is their experience with that?
I even thought of converting every umlaut (ä -> ae, ö -> oe etc.), but that wouldn't solve the problem with the link to search.cgi....
Any help would be very appreciated.
Thank you.
Andreas
http://www.archaeologie-online.de
I searched the support forums but didn't find a solution for the following problem:
Because my site is in German language I have very much accented characters (umlauts) in the descriptions of the links. When sending out a newsletter I often get complaints that the umlaut characters are unreadable because they are changed to '=E4' (for 'ä') and so on. What makes this even worse is that I provide a link to 'search.cgi?query=&ID=123' and the equal sign gets converted, too, so the link becomes something like that: 'search.cgi?query=3D&ID=3D2=123' which obviously doesn't work.
Apparently this is not the case for all recipients - the mail I and many others receive, is displayed absolutely correct.
I guess this must have something to do with the setting for 'Content-Transfer-Encoding' which is set to 'quoted printable' (I am using smtp, not sendmail).
So I changed the corresponding line in Bulkmail.pm from
print $out "Content-Transfer-Encoding: quoted-printable";
to
print $out "Content-Transfer-Encoding: 8bit";
which - as I understand - should do no encoding at all.
But with that setting the test mails I sent to myself via 'Mass Mail' -> 'Selected Users' get converted exactly the way some of my users are complaining about.
So I have to chose from
Content-Transfer-Encoding: quoted-printable -> some users get scrambled umlauts
or
Content-Transfer-Encoding: 8bit -> I get scrambled umlauts myself (not knowing if the complaining users would get correct ones)
Unfortunately I have no idea how to tell the smtp server or the script to do an encoding that makes sure that everybody will get correct umlauts.
Does anyone else use umlauts in the Links newsletter?
What is their experience with that?
I even thought of converting every umlaut (ä -> ae, ö -> oe etc.), but that wouldn't solve the problem with the link to search.cgi....
Any help would be very appreciated.
Thank you.
Andreas
http://www.archaeologie-online.de