On 4/22/14, 1:55 AM, "Martin J. Dürst" wrote:
Hello Peter/Pete/others,
On 2014/04/22 02:44, Peter Saint-Andre wrote:
Looking back at the text, I think Pete might have a point. I suggest the
following change.
###
OLD
The directionality rule of a profile specifies which strings are to
be considered left-to-right (LTR) and right-to-left (RTL), and the
allowable sequences of characters in LTR and RTL strings (see Unicode
Standard Annex #9 [UAX9]); note that mixed-direction strings are not
supported, since there is currently no widely accepted and
implemented solution for the processing and display of mixed-
direction strings. Possible rules include, but are not limited to,
(a) considering any string that contains a right-to-left code point
to be a right-to-left string, or (b) applying the "Bidi Rule" from
[RFC5893].
NEW
The directionality rule of a profile specifies which strings are to
be considered left-to-right (LTR) and right-to-left (RTL), and the
allowable sequences of characters in LTR and RTL strings (see Unicode
Standard Annex #9 [UAX9]). Possible rules include, but are not
limited to, (a) considering any string that contains a right-to-left
code point to be a right-to-left string, or (b) applying the "Bidi
Rule" from [RFC5893].
Mixed-direction strings are not directly supported by the PRECIS
framework itself, since there is currently no widely accepted and
implemented solution for the processing and safe display of mixed-
Please remove "processing". Processing mixed-direction strings isn't a
problem at all. Display is the problem.
Correct.
direction strings. An application protocol that uses the PRECIS
framework (or an extension to the framework) could define methods for
handling mixed-direction strings; however, such methods are outside
the scope of the framework.
I'm not sure "handling" and "methods" are the right word, unless these
words are used in other parts of the text. They sound a bit too
procedural for simple restrictions. In theory, it's possible to define
new ways of displaying things, but good luck for getting these deployed
:-(.
I'd prefer if the text here ended with some clear caution. Maybe
something like changing the last part of the last sentence to
"however, such methods are outside the scope of the framework and should
only be introduced after carefully studying bidirectional display
problems."
I originally had something like "such methods are fraught with
difficulty so don't try to solve the problem unless you really know what
you're doing". Adding the text you propose is fine with me.
Peter
_______________________________________________
precis mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/precis
