W3C home > Mailing lists > Public > html-tidy@w3.org > July to September 2005

Re: Chinese characters in BBEdit (again)

From: Fred Bone <Fred.Bone@dial.pipex.com>
Date: Wed, 10 Aug 2005 19:07:49 +0100
To: html-tidy@w3.org
Message-ID: <42FA5085.18241.6493D1B@Fred.Bone.dial.pipex.com>

On 10 Aug 2005 at 13:52, Chris von Rosenvinge said:

[...]

> 2. In the config file that I can choose with the BBTidy plug-in, I use
> 
> ascii-chars: no
> numeric-entities: yes
> 
> This leaves alone such items as #160 
> (non-breaking space) and #8226 (bullet) as well 
> as #8211 (en dash) and #8220 (curly open quote). 
> It even knows to convert ndash to #8211. However, 
> it turns eacute and #233 into an e with an acute 
> accent, which reads OK as a local file opened in 
> a browser, but displays incorrectly from a web 
> server. Similarly with other accented characters, 
> such as U umlaut.

Sounds like your problem is with the web server.

What hex value is being stored/transmitted for that eacute?
What charset does the server say the page is in?
What transfer-encoding does it say is being used?
What charset is the page actually in?
Is there a charset meta tag in the page?
What do you mean by "displays incorrectly"?
Received on Wednesday, 10 August 2005 18:09:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 April 2012 06:13:55 GMT