[Bug 28650] named character reference needed for curved apostrophe in natural-language English content

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28650

Michael[tm] Smith <mike@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mike@w3.org

--- Comment #2 from Michael[tm] Smith <mike@w3.org> ---
Current best practice it to not use named character references at all. At this
point they're basically just a legacy feature of the platform. No implementors
are interested in adding new ones.

Best practice is to type characters directly, without using either named
character references or numeric character references.

(In reply to Nick Levinson from comment #0)

> While we can use
> &amp;rsquo; or &amp;#0146; for English text, they are not either memorable
> in context or named semantically for the usage.

You can also just type a literal ’ character. That way the problem of what’s
memorable or “named semantically” (whatever you mean by that) isn't relevant.

> I'd like HTML5 to provide a
> curved apostrophe with a named character reference that would be
> semantically relevant. I propose adding &amp;aposc;.

“aposc” doesn’t seem to be an improvement over “rsquo” in any way. “rsquo“ is a
mnemonic for “right single quote” that’s become well-known. “aposc” means
nothing to nobody nowhere, and it’s not at all obvious that it’s intended to
mean “curved apostrophe”.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 18 May 2015 08:03:57 UTC