Re: utf8 output from database
- From: Sander Tekelenburg <user@xxxxxxxxxxxxxx>
- Date: Tue, 15 Nov 2005 18:38:29 +0100
In article <L8idne-6U7PDiOfeRVn-rQ@xxxxxxxxxxx>,
Jerry Stuckle <jstucklex@xxxxxxxxxxxxx> wrote:
[...]
> I have seen other problems like this; it's generally the charset isn't
> set up to display that particular character. And I'm not sure UTF-8
> will do it.
The charset parameter doesn't 'do' anything. It simply claims which
character repertoire applies. If the content is utf-8, the charset
should say so. If the content is for example mac-roman, claiming
"charset=utf-8" doesn't *make* it utf-8. You'll need to transliterate to
utf-8 first.
Thus, you need to always, in this order,
- know what character repertoire your original content is in
- optionally transliterate to another character repertoire
- ensure all tools you use handle that character repertoire properly
- provide the correct charset value to let user-agents know how to
handle the data
--
Sander Tekelenburg, <http://www.euronet.nl/~tekelenb/>
Mac user: "Macs only have 40 viruses, tops!"
PC user: "SEE! Not even the virus writers support Macs!"
.
- References:
- utf8 output from database
- From: elyob
- Re: utf8 output from database
- From: Jerry Stuckle
- utf8 output from database
- Prev by Date: Re: multiple stacks, multiple versions bother anybody, or is it just me?
- Next by Date: noob...content via fread keeps reverting
- Previous by thread: Re: utf8 output from database
- Next by thread: Re: utf8 output from database
- Index(es):
Relevant Pages
|