|
|
Posted by Joγo Morais on 09/28/14 12:01
> If you have any chance of avoiding such meta tags, do so. Send the
> header it "replaces".
Ok, but the header should specify utf8 too?
> What would you think of
>
> <meta http-equiv="Content-Type" content="text/html; charset=UTF-32"> ?
>
> Sending a meta tag describing the encoding within the encoded page is
> like locking the key to a safe inside it.
> What's even worse, your server may send a "latin-1" header while your
> code could have an "utf-8" meta tag. Which of the two would be the right
> one?
I see the problem.
And this:
>Right, so if I want to support this kind of characters my:
>
>* mysql charset
>* mysql connection collation
>* table collation's
Is it correct?
Navigation:
[Reply to this message]
|