Chris von Rosenvinge wrote: > 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. > > Does anyone know how to avoid these problems? It would appear that that your tidy installation is using latin-1 as its output encoding. Try adding: output-encoding: ascii or output-encoding: utf8 to your configuration file. Under no circumstances should you use "output-encoding: raw". > Thanks! HTHReceived on Wednesday, 10 August 2005 22:21:19 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 April 2012 06:13:55 GMT