[Bug 10838] Make <u> conforming.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10838

KangHao Lu <kennyluck@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |

--- Comment #2 from KangHao Lu <kennyluck@w3.org> 2010-09-30 06:52:31 UTC ---
The following is two other use cases of <u> from the wiki entry "Underline"[1].
I am not familiar with these use cases, but I think <em>, <mark> and <b> are
not suitable here.

- Underlines are sometimes used as a diacritic, to indicate that a letter has a
different pronunciation to its non-underlined form.
- single underline used on manuscripts to indicate the italic typeface to be
used

The use of <i> for the second use case is arguably incorrect because the
typical typographic presentation in that context is not italicized.

While these are probably corner cases, it might be worth giving just a tag to
these cases where underline is the typical typographic presentation.

For the record, I do agree that we shouldn't add extra semantics to <u>, but
based on the current spec I don't agree that <u> is more presentational than
<b> and <i>. They are all "a span of text offset from the normal
prose/presentational mode, whose typical typographic presentation is xxx" to
me, and explanation based on examples is confusing and somehow inconsistent.
<i> for ship names won't be pronounced in an alternative voice (and ship names
won't be italicized in Chinese, just as proper nouns won't be underlined in
English), and I personally think these should all be made obsolete but
conforming for consistency. They are all last resorts anyway.

Any pointer to your long thought about underline will be appreciated.

[1] http://en.wikipedia.org/wiki/Underline

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Thursday, 30 September 2010 06:52:36 UTC