Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Constrain certain descendant content in ruby container. #372

Closed
skynavga opened this issue Jun 5, 2017 · 2 comments
Closed

Constrain certain descendant content in ruby container. #372

skynavga opened this issue Jun 5, 2017 · 2 comments

Comments

@skynavga
Copy link
Collaborator

skynavga commented Jun 5, 2017

Proscribe the following from appearing in a ruby container:

  • use of span children of container that do not specify a ruby style, i.e., that do not play a role in ruby structure; if present, then such span is ignored for presentation purposes;
  • use of #PCDATA children of container, baseContainer, and textContainer; i.e., permit #PCDATAA only in base, text, and delimiter; if used, then ignore for presentaion purposes;
  • use of br element in ruby or its descendants, and, if used, treat as normal (collapsible) whitespace;
  • use of U+2028 (LINE SEPARATOR) and U+2029 (PARAGRAPH SEPARATOR) in ruby or its descendants, and, if used, they are interpreted as normal (collapsible) whitespace.

Editorial notes from 2015-02-18.

@tmichel07 tmichel07 added WR-open and removed WR-open labels Oct 2, 2017
@skynavga skynavga self-assigned this Jan 19, 2018
@cconcolato
Copy link
Contributor

IMO, the text would be much more readable if it was expressed as it is currently in the note, i.e.:

container
: base text
| base delimiter text delimiter
| baseContainer textContainer textContainer?

rather than with a lengty bullet point list.

@skynavga
Copy link
Collaborator Author

We can't express the bulleted constraints using this grammar. I am working on this issue now, so a PR will appear shortly.

@skynavga skynavga added this to the Editor's CR Work List milestone Jan 31, 2018
skynavga added a commit that referenced this issue Feb 14, 2018
@skynavga skynavga removed their assignment Feb 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants