Package: tidy
Version: 20091223cvs-1
Severity: minor

For XHTML output, it is an error to generate entity references (except
the standard XML ones) as they are not guaranteed to work. Indeed
http://www.w3.org/TR/html5/the-xhtml-syntax.html#writing-xhtml-documents
says:

  Note: According to the XML specification, XML processors are not
  guaranteed to process the external DTD subset referenced in the
  DOCTYPE. This means, for example, that using entity references for
  characters in XHTML documents is unsafe if they are defined in an
  external file (except for <, >, &, " and ').

Numeric character references should be generated instead, i.e. when
XHTML output is generated, numeric-entities should be ignored (or at
least, it should default to "yes").

An example of the problem:

  echo "é" | tidy -asxhtml

outputs:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml";>
<head>
<meta name="generator" content=
"HTML Tidy for Linux (vers 25 March 2009), see www.w3.org" />
<title></title>
</head>
<body>
&eacute;
</body>
</html>

Note: web browsers should have no problems with entity references,
but remember that one of the purposes of XHTML (over HTML) is to
manipulate the files with XML tools.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages tidy depends on:
ii  libc6                      2.11.2-7      Embedded GNU C Library: Shared lib
ii  libtidy-0.99-0             20091223cvs-1 HTML syntax checker and reformatte

tidy recommends no packages.

Versions of packages tidy suggests:
ii  tidy-doc                   20091223cvs-1 HTML syntax checker and reformatte

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to