Character encodings (UTF16)

[Andras Mantia]

On Wednesday 09 February 2005 17:52, Thiago Macieira wrote:
> Andras Mantia wrote:
> >PS: It's funny how it's shown in KMail. The file was attached, no
> > sign of HTML mails here.
>
> Well, the attachment is totally wrong:
>
> Content-Type: text/html;
>   charset="us-ascii";
>
> It'll never display correctly in KMail. I'd venture to say that even
> if you click on the attachment and have it open externally, it should
> NOT display correctly, because of that encoding. The emailer -- KMail
> -- should have added the proper encoding.

Well, this is what KMail did...

> However, if you save the file to disk, then open it, the programs
> should detect the UTF-16 encoding. It would be easier if the file
> started with the Byte Order Mark (BOM), which is a good way of
> telling it is UTF-16.

So you say the files are correct and just the byte order marks is not 
present and this causes the KDE applications to fail loading it? In 
this case the problem is really on the KDE side.

Andras

-- 
Quanta Plus developer - http://quanta.sourceforge.net
K Desktop Environment - http://www.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050209/5e2a53f6/attachment.sig>