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

[Bug 10660] use < and > and not &#8592; and &#8594; to indicate previous and next

From: <bugzilla@jessica.w3.org>
Date: Fri, 12 Nov 2010 01:30:52 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PGiTc-0002OH-RG@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10660

--- Comment #3 from Gregory J. Rosmaita <oedipus@hicom.net> 2010-11-12 01:30:51 UTC ---
(In reply to comment #2)

> Status: Rejected
> Change Description: no spec change
> Rationale: Angle brackets aren't the appropriate Unicode characters here, so
> I'm WONTFIXing this. If there are ATs that don't handle Unicode correctly, they
> should be fixed.

ian, i think you misunderstand the issue -- the problem isn't in the exposition
of the unicode characters, but in their replication by a user who is trying to
use a list of links or an auto-complete feature to get to/activate the link
that leads to the previous and next sections -- i have a 101 key keyboard, and
i don't know how to generate the character you are currently using as part of
the hyperlink text in the navigational portion of the multi-page view; i can't
even imagine how i would invoke it on a device with only a telephone keypad to
input text or a braille keyboard (as one can do with the icon or braille plus
from APH (american printing house for the blind -
http://tech.aph.org/pda_doc.htm)

-- 
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, 12 November 2010 01:30:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 12 November 2010 01:31:01 GMT