W3C home > Mailing lists > Public > html-tidy@w3.org > April to June 2010

char-encoding, input-encoding, output-encoding

From: Dennis Kowallek <kowallek@iglou.com>
Date: Thu, 06 May 2010 11:00:55 -0400
To: html-tidy@w3.org
Message-ID: <psl5u5d9v47d92u2too1aomm5frq64u34p@4ax.com>
Why are there 3 options? Why not just input-encoding and
output-encoding? If specified, do input-encoding and output-encoding
override char-encoding?

Also, in the quickref
(http://tidy.sourceforge.net/docs/quickref.html#char-encoding) it

"For mac and win1252, Tidy will accept vendor specific character values,
but will use entities for all characters whose value > 127."

I assume this is referring to the output side. Does this mean that chars
like  will be converted to entities like \&\#\n\n\n\; (remove
backslashes) on output?


Received on Thursday, 6 May 2010 15:01:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:38:57 UTC