This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16983 - i18n-ISSUE-124: Wording on avoidance of Unicode control characters
Summary: i18n-ISSUE-124: Wording on avoidance of Unicode control characters
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Edward O'Connor
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 17866
  Show dependency treegraph
 
Reported: 2012-05-07 18:19 UTC by Addison Phillips
Modified: 2012-10-12 22:56 UTC (History)
6 users (show)

See Also:


Attachments

Description Addison Phillips 2012-05-07 18:19:46 UTC
3.2.6 Requirements relating to bidirectional-algorithm formatting characters
http://www.w3.org/TR/html5/content-models.html#requirements-relating-to-bidirectional-algorithm-formatting-characters

This note:

--
For convenience, where possible authors will likely prefer to use the dir attribute, the bdo element, and the bdi element, rather than maintaining the bidirectional-algorithm formatting characters manually.
--

We would prefer if it were rephrased slightly to read:

--
For convenience, where possible authors should use the dir attribute, the bdo element, and the bdi element, rather than maintaining the bidirectional-algorithm formatting characters manually.
--

We would also like it to be removed from a note and made normative (hence the use of "should").
Comment 1 Ian 'Hixie' Hickson 2012-05-08 00:31:26 UTC
"should" means that it's a requirement. If it's a requirement, it's not for convenience. Why would we make it a requirement?
Comment 2 Addison Phillips 2012-05-08 00:43:53 UTC
(In reply to comment #1)
> "should" means that it's a requirement. If it's a requirement, it's not for
> convenience. Why would we make it a requirement?

Indeed it is normative (and we noted that in our comment). Since this directed at authors as a requirement upon them. The weasel wording surrounding the normative SHOULD will not be ignored ;-)
Comment 3 Ian 'Hixie' Hickson 2012-05-10 17:53:54 UTC
Yes but why?
Comment 4 contributor 2012-07-18 07:08:46 UTC
This bug was cloned to create bug 17866 as part of operation convergence.
Comment 5 Edward O'Connor 2012-10-12 22:56:56 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:

   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Additional Information Needed
Change Description: No spec change.
Rationale: Awaiting a reply to Ian's question in comment #3.