Loading...
 
Features / Usability

Features / Usability


Problem with characters in webmail

posts: 6 Sweden

Hi!
Is ti only me who has encoding problem with webmail?
I can't get the swedish characters åäö to work with webmail.
If I mess someone and let this user get a mail sent that a message has arrived it works just fine.
With webmail the character shows up like åäö.
If I look at the header it says:
Subject: =?ISO-8859-1?Q?=C3=A5=C3=A4=C3=B6?=
...but with a mail that shows the characters right (sent with outlook) the Subject row says:
Subject: =?iso-8859-1?B?5eT2?=

Is ther a known problem with tiki's webmail or am I just stupid?
I've read everything to find about the character problems that have occured in tiki but I can't find any solution for webmail.

Please help me on this...

Regards
/Pitch

posts: 1092

Q and B are the different Mime encoding. As far as you mail reader can read the 2 encoding, it will not create problem

On my site, sending email with a header with accent is ok... Receiving - I have a system error I am trying to solve.

I had problem with header encoding with htmlMimeMail library. For the newsletter there is a modify encoding header. Can you send a newsletter and test if it is the same behavior?

posts: 6 Sweden

> Q and B are the different Mime encoding. As far as you mail reader can read the 2 encoding, it will not create problem
>
> On my site, sending email with a header with accent is ok... Receiving - I have a system error I am trying to solve.
>
> I had problem with header encoding with htmlMimeMail library. For the newsletter there is a modify encoding header. Can you send a newsletter and test if it is the same behavior?

Sorry, but I don't get this.
Shouldn't it be possible to use M$-Outlook to read the mail?
How is it possible to get two different encodings of the same text depending on which "mail-client" you are using when it's using the same codeset (iso-8859-1)?
Isn't iso8859-1 a standard that shouldn't have more than one way to interpret?

/Pitch


posts: 6 Sweden

Sorry, but I don't get this.
Shouldn't it be possible to use M$-Outlook to read the mail?
How is it possible to get two different encodings of the same text depending on which "mail-client" you are using when it's using the same codeset (iso-8859-1)?
Isn't iso8859-1 a standard that shouldn't have more than one way to interpret?

/Pitch

posts: 3

First tiki1.8 doesn't encode the mail properly.
1.9 is supposed to do a better job. The difference you gave is not important as it is 2 different standards mail reader are suppose to accept. But the problem is has usual. Mail reader don't accept the same syntax. A lot are not standard. and is the encoding way tiki has now the best to fit the majority of mail reader?
Perhaps there is a potentiel problem in webmail and not in newsletter (as the library has been fixed in newsletter). It is why it will be nice to try to send a newsletter to the same address and to see if the problem exist?

posts: 6 Sweden

> First tiki1.8 doesn't encode the mail properly.
> 1.9 is supposed to do a better job. The difference you gave is not important as it is 2 different standards mail reader are suppose to accept. But the problem is has usual. Mail reader don't accept the same syntax. A lot are not standard. and is the encoding way tiki has now the best to fit the majority of mail reader?
> Perhaps there is a potentiel problem in webmail and not in newsletter (as the library has been fixed in newsletter). It is why it will be nice to try to send a newsletter to the same address and to see if the problem exist?

I've now tried the newsletter-module and it works great, both subject and body is getting throug nice :-).
Is it easy to put the newsletter lib-code into the webmail lib-code?
Thank You!
/pitch