Re: Invalid HTML-Tags
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 06.10.2005 um 14:31 schrieb Frédéric Bothamy:
I agree that <em> and <strong> should be preferred, but I did not see
anywhere in the HTML specifications
(http://www.w3.org/TR/html401/index/elements.html) that they should
not
be used, even using "HTML Strict".
Please read the notes about accessibilty and what css and HTML tags
are for. Rendering (presentation) should go to css with HTML strict.
HTML tags are for pointing out what the content is (paragraph, link,
quotation heading and so on).
And <b> and <i> is font rendering.
Maybe you missed the mails about www.debian.org going HTML strict
instead of outdated Transitional? Strict is available for years now.
Using <q> was only a quick solution as some content really has been
quotes. It si up to the translators to replace the tag by <q lang=en-
us> where content is an english book title (which should not be
translated if not available in you origin language) or lang=fr-fr if
the content is french.
I am not sure, if the borwser will render it better then. Maybe, I
find a css solution.
For all: it is really not possible to ask in every translation group
for all the changes necesary. That would takes years of discussion
and lots of mail in my mailbox, I cannot read at all (not the masses
and not most languages).
Beside that, It cannot really be a problem having some wrong quotes
on old pages for some weeks until a soulution is found (may be the
solution is filing bugs against browsers representing quotes wrong).
greetings
Jutta
- --
http://www.witch.westfalen.de
http://witch.muensterland.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iEYEARECAAYFAkNFcFgACgkQOgZ5N97kHkeixQCaAoB3K8SqcDgDQ0pesip70Xq1
4BIAoKKcBbr5MmVb0rSbfr14k78vpeMu
=Fo+J
-----END PGP SIGNATURE-----
Reply to: