[bp-i18n-specdev] Some "problems with control characters" are not exclusive to CC, but also apply to markup

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[bp-i18n-specdev] Some "problems with control characters" are not exclusive to CC, but also apply to markup

r12a via GitHub
lkemmel has just created a new issue for
https://github.com/w3c/bp-i18n-specdev:

== Some "problems with control characters" are not exclusive to CC,
but also apply to markup ==
"5.2.4 Problems with control characters" says:

"2. It is sometimes necessary to choose which [CC] to use based on
context or the type of the data, and this means that a content author
typically needs to select the control codes – specifying control codes
 in this way for all paragraphs is time-consuming and error-prone."

- and

"Don't expect users to add control codes at the start and end of every
 paragraph. That's far too much work"

Same holds true for markup, at least in the following cases:
   - there is a need to denote an embedding direction (and hence it's
necessary to choose which direction value to specify within markup for
 each inline segment),
  -  first-strong algorithm doesn't represent the content adequately
(and hence it's necessary to choose explicit "prevailing" direction
within the markup for each paragraph),
  - the prevailing base direction is not uniform and thus can't be
denoted for units containing multiple paragraphs (but for each
paragraph individually).




See https://github.com/w3c/bp-i18n-specdev/issues/17
Please do NOT reply to this email. If you'd like to contribute to the
discussion, please do so at the above link. You will need to subscribe
 yourself to the issue (using the button provided by that page) to
receive notifications of further comments.