If I get a mail from phpgedview the special chars in the body which are coded with utf-8 are not displayed properly when I try to read them with outlook express.
If I send out a mail from mozilla with setting UTF-8 coding mozilla writes:
phpgedview only writes the subject message from the chosen lang file.
For example (where für means fr in UTF-coding):
[PhpGedView Message] Neue Anmeldung für http://localhost
Mozilla does this:
Subject: [PhpGedView Message] Neue Anmeldung =?UTF-8?B?ZsO8ciBodHRwOi8vbG8=?=
=?UTF-8?B?Y2FsaG9zdA==?=
----------------------------------
Mozilla uses the following way:
Subject: test =?UTF-8?B?w7wgxJ8=?=
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
------------------------------------
This is a mail which I can also read with OE and the unicode-chars are displayed correctly.
Does anybody see where the problem could be???
bye, Kurt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Don't know if it is but do you also include the utf-coded subject into "" ??? So seem to do so with the fullname of "TO:" and the fullname of "FROM:" but not with subject.
bye, Kurt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I tested this I switched the language to German and changed my name to a German word and sent a message to myself.
I got two emails that Outlook was able to read without any problem. The headers looked like this:
Date: Mon, 01 Dec 2003 14:54:03 -0700
From: =?UTF-8?Q?=65=72=6d=c3=b6=67=6c=69=63=68=74?= <yalnifj at users.sourceforge.net>
Subject:
=?UTF-8?Q?=5b=50=68=70=47=65=64=56=69=65=77=20=4d=65=73=73=61=67=65=5d=20=c3=9c=62=65=72=77=61=63=68=65=6e=20=62=65=76=6f=72=73=74=65=68=65=6e=64=65=72=20?=
To: =?UTF-8?Q?=65=72=6d=c3=b6=67=6c=69=63=68=74?= <yalnifj at users.sourceforge.net>
Message-id: <01L3OOUSJE5C95U395@EMAIL1.BYU.EDU>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8; format=flowed
Content-transfer-encoding: 8BIT
I then forwarded these emails to other addresses that I have and still did not have any problems reading them.
--John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That is one of the things that I was afraid of. My only other idea is to use the utf8_decode function on the to, from, and subject fields. This will work fine for most of the languages, but for some languages, like chinese, I don't think this will work.
--John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Not sending the names would work, but we still have the same problem with the subject.
I've tried using the utf8_decode function but it isn't working either.
I think that the best compromise will only be to convert to the UTF-8 encoding if the characters can only be encoded that way otherwise just send the plain text with encoding it.
Even if they get an email in their webclient that they cannot read, they could still login to their MyGedView page and read it correctly.
--John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If I get a mail from phpgedview the special chars in the body which are coded with utf-8 are not displayed properly when I try to read them with outlook express.
If I send out a mail from mozilla with setting UTF-8 coding mozilla writes:
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
PHPGedView writes:
Content-type: text/plain; charset=UTF-8
----------------------
Also a problem seems to be the subject line:
phpgedview only writes the subject message from the chosen lang file.
For example (where für means fr in UTF-coding):
[PhpGedView Message] Neue Anmeldung für http://localhost
Mozilla does this:
Subject: [PhpGedView Message] Neue Anmeldung =?UTF-8?B?ZsO8ciBodHRwOi8vbG8=?=
=?UTF-8?B?Y2FsaG9zdA==?=
----------------------------------
Mozilla uses the following way:
Subject: test =?UTF-8?B?w7wgxJ8=?=
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
------------------------------------
This is a mail which I can also read with OE and the unicode-chars are displayed correctly.
Does anybody see where the problem could be???
bye, Kurt
Hi Kurt,
This has also been discussed in this bug:
http://sourceforge.net/tracker/index.php?func=detail&aid=844130&group_id=55456&atid=477079
I could decode it back to ISO-8859 for the emails but this would cause problems with some languages like chinese.
I'm not sure how to go from:
[PhpGedView Message] Neue Anmeldung
to
=?UTF-8?B?ZsO8ciBodHRwOi8vbG8=?==?UTF-8?B?Y2FsaG9zdA==?=
--John
Kurt,
I figured out how to do the encoding and committed the changes to CVS.
Could you update and get the latest CVS file and try out the mail to make sure it is working for you?
Thanks,
--John
Hi John...
I tried it out but it seems that the problem is not solved yet.
I updated from cvs. Put it on the server and now the mails are totally destroyed.
Now I have parts of the header inside the mail and this part also includes the UTF-8 info :-(
For example:
Content-type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Message-Id: <E1AQuuZ-00041Q-00@mrvnet.kundenserver.de>
X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:d41d8caaloofdsaf4e9800998ecf8427e
X-NAS-Classification: 0
X-NAS-MessageID: 1104
X-NAS-Validation: {XXXX113B-D439-4B24-A0ED-F9487012BDF7}
Don't know if it is but do you also include the utf-coded subject into "" ??? So seem to do so with the fullname of "TO:" and the fullname of "FROM:" but not with subject.
bye, Kurt
The included header text in the last message is NOT part of the header anymore.
It is handled as part of the mail.
Sorry, but I will shut down now. I will be online on Thursday again.
Maybe you can ask Botak to help. He also uses another language than english :-)
bye, Kurt
When I tested this I switched the language to German and changed my name to a German word and sent a message to myself.
I got two emails that Outlook was able to read without any problem. The headers looked like this:
Date: Mon, 01 Dec 2003 14:54:03 -0700
From: =?UTF-8?Q?=65=72=6d=c3=b6=67=6c=69=63=68=74?= <yalnifj at users.sourceforge.net>
Subject:
=?UTF-8?Q?=5b=50=68=70=47=65=64=56=69=65=77=20=4d=65=73=73=61=67=65=5d=20=c3=9c=62=65=72=77=61=63=68=65=6e=20=62=65=76=6f=72=73=74=65=68=65=6e=64=65=72=20?=
To: =?UTF-8?Q?=65=72=6d=c3=b6=67=6c=69=63=68=74?= <yalnifj at users.sourceforge.net>
Message-id: <01L3OOUSJE5C95U395@EMAIL1.BYU.EDU>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8; format=flowed
Content-transfer-encoding: 8BIT
I then forwarded these emails to other addresses that I have and still did not have any problems reading them.
--John
But how do we humans read
=?UTF-8?Q?=5b=50=68=70=47=65=64=56=69=65=77=20=4d=65=73=73=61=67=65=5d=20=c3=9c=62=65=72=77=61=63=68=65=6e=20=62=65=76=6f=72=73=74=65=68=65=6e=64=65=72=20?=
Trying to read emails via the WebMail interface from my ISP doesn't decode UTF-8 into English (or any other readable language)
Mark
Hi Mark,
That is one of the things that I was afraid of. My only other idea is to use the utf8_decode function on the to, from, and subject fields. This will work fine for most of the languages, but for some languages, like chinese, I don't think this will work.
--John
Hi John,
if you don't send the Realname of the users and only the emailadress you do not need to convert the from and to of an email.
You could put these infos inside the local mail and don't add it to the mail which is sent over the net.
Would this be a kompromise?
bye, Kurt
Hi Kurt,
Not sending the names would work, but we still have the same problem with the subject.
I've tried using the utf8_decode function but it isn't working either.
I think that the best compromise will only be to convert to the UTF-8 encoding if the characters can only be encoded that way otherwise just send the plain text with encoding it.
Even if they get an email in their webclient that they cannot read, they could still login to their MyGedView page and read it correctly.
--John