You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The table in this appendix jumbles up a bunch of different things.
Do you want it to show how RLM/LRM can be prepended to a string in JSON to indicate the intended base direction? (If so, the examples should use javascript escapes, rather than HTML escapes.) (This is the kind of thing that rows 3 and 4 appear to be aiming at.)
Or do you want it to show how a consumer would wrap the string in markup/characters, to show how to apply the base direction in the target location when used? (which seems to be implied by the location of the link at the moment)
The second row of the table also shows how one can use characters to embed a different base direction within a string. Do you really need this? We don't mention string-internal bidi controls in the rest of the spec - only how to set the overall directional context for the string as a whole.
If you want to achieve more than one of the above, i think you will need to break up the table and add a bunch of introductory and explanatory text.
The text was updated successfully, but these errors were encountered:
D. Examples for bidirectional texts
https://w3c.github.io/wpub/#app-bidi-examples
The table in this appendix jumbles up a bunch of different things.
Do you want it to show how RLM/LRM can be prepended to a string in JSON to indicate the intended base direction? (If so, the examples should use javascript escapes, rather than HTML escapes.) (This is the kind of thing that rows 3 and 4 appear to be aiming at.)
Or do you want it to show how a consumer would wrap the string in markup/characters, to show how to apply the base direction in the target location when used? (which seems to be implied by the location of the link at the moment)
The second row of the table also shows how one can use characters to embed a different base direction within a string. Do you really need this? We don't mention string-internal bidi controls in the rest of the spec - only how to set the overall directional context for the string as a whole.
If you want to achieve more than one of the above, i think you will need to break up the table and add a bunch of introductory and explanatory text.
The text was updated successfully, but these errors were encountered: