Tidy warnings and IDs and names
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
http://people.debian.org/~alfie/tidy/ shows warnings about not being
able to copy name attribute to id.
I want to know, what to do with these warnings.
This can be caused mainly be two reasons:
1. There is already an Id with the same name in that page
2. The name attribute contains characters not allowed in name or id [1]
The current errors are completely or mainly of kind 2.
HTML Spec [2] allows the following characters in name and id attributes:
- - the attribute mus begin wit a letter ([A-Za-z])
- - the following characters ma be letters, digits, hyphens,
underscores, colons and periods
The attributes ma not contain spaces, commas, or characters from non
ascii range and others.
Some examples of wrong usage:
- - http://www.debian.org/devel/people contains name attributes with
spaces. The spaces should be deleted or replaced by unterscores. As
people.names is genereated outside, there may be a replace directive
in the wml file?
- - http://www.debian.org/CD/releases/ has names like "3.1 rev0a" which
contain spaces and a digist as first character. This can be replaced
by "debian3.1rev0a" or "debian3.1_rev0a"
For the second page I have already had a look, if something inside
the tree is pointing to the anchors, but seems nothing does.
References from other places will always reach the page though, if we
replace those names.
Another point to keep in mind here is using names or ids. In nost of
the cases, I'd just change the names to Ids, becaus we get in trouble
with the css fpr links. IN other cases, where the a-tag does not
contain a href, the atag just can be opened and shut again
immediately behind the name.
[1] The w3 validator should create an error on that but does not to.
[2] See HTML 4.01 Specicication at http://www.w3.org/TR/html401 p. 50
- --
http://www.witch.westfalen.de
http://witch.muensterland.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iEYEARECAAYFAkOIV1YACgkQOgZ5N97kHkfU3QCfSXQfx9mtFJAaVINgXJ9g1qjf
q5YAn3073JpYF3/Nji6035SKOMFVdDkF
=lRsM
-----END PGP SIGNATURE-----
Reply to: