UTF-8 More info

[kgroneman]

While the individual languages for forum use are now UTF-8 providing
readability between all language forums, the server used (vBulletin)
remains ISO-8859-1 (Latin). There are two reasons for this, first
because vBulletin does not support changing to UTF-8, second, like
changing the database, we don't have the time/resources now to do it.
Also non-ascii characters are not officially supported in URLs so
switching them over is not an option.

What this means is that when you get an email from the system or read
via NNTP, the server code will be Latin. The body of NNTP messages
will be UTF-8, however so if you set your reader for UTF-8 you'll have
no problem reading them.

Baby steps...baby steps.....

--
Kim - 5/10/2011 1:32:51 PM

[robin_listas]

On 2011-05-10 21:39, kgroneman wrote:

> What this means is that when you get an email from the system or read
> via NNTP, the server code will be Latin. The body of NNTP messages
> will be UTF-8, however so if you set your reader for UTF-8 you'll have
> no problem reading them.

You can not set Thunderbird to UTF-8, except for the current message and
valid only till you view another post.

The "Content-Type" header of the posts has to be changed to match the
content. You can not send UTF and say it is Latin.

--
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 "Emerald" at Telcontar)

[vindevienne]

While the individual languages for forum use are now UTF-8 providing
readability between all language forums, the server used (vBulletin)
remains ISO-8859-1 (Latin). There are two reasons for this, first
because vBulletin does not support changing to UTF-8, second, like
changing the database, we don't have the time/resources now to do it.
Also non-ascii characters are not officially supported in URLs so
switching them over is not an option.

What this means is that when you get an email from the system or read
via NNTP, the server code will be Latin. The body of NNTP messages
will be UTF-8, however so if you set your reader for UTF-8 you'll have
no problem reading them.

Baby steps...baby steps.....

--
Kim - 5/10/2011 1:32:51 PM

I am no expert in URLs and domain naming but I was under the impression that UTF8 domain names and URLs were now acceptable. I thought that this was changed by ICANN in 2009.