W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2010

[Bug 11124] consider reducing verbosity when talking about code points

From: <bugzilla@jessica.w3.org>
Date: Fri, 22 Oct 2010 18:25:46 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P9MJG-0003VC-8o@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11124

Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Simetrical+w3cbug@gmail.com

--- Comment #4 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2010-10-22 18:25:45 UTC ---
I think the UPPERCASE NAME is excessive.  Just give the character itself and
the code point, like

"""
a valid non-negative integer, followed by ";" (U+003B), followed by one or more
space characters, followed by a substring that is an ASCII case-insensitive
match for the string "URL", followed by "=" (U+003D), followed by a valid URL.
"""

or maybe

"""
a valid non-negative integer, followed by U+003B (;), followed by one or more
space characters, followed by a substring that is an ASCII case-insensitive
match for the string "URL", followed by U+003D (=), followed by a valid URL.
"""

or whatever.  It's more concise and easier to read, but no less precise.  You
should only need to give a name when the character is whitespace or a combining
diacritic or something, and in that case you should just use a simple
description like "space", "tab", "CR", "LF", not the full Unicode name.

(In reply to comment #3)
> I disapprove of the RFC style of giving ad hoc names to Unicode characters. I
> object to using that style in HTML5.

It's already used in some places, e.g., "space characters".

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 22 October 2010 18:25:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:32 UTC