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

Clarify character styling and other styling requirements #76

Merged
merged 4 commits into from
Dec 1, 2022

Conversation

nigelmegitt
Copy link
Contributor

@nigelmegitt nigelmegitt commented Nov 25, 2022

Closes #29 and #60.

  • Drive-by fix of a few linting/HTML syntax errors including removing two duplicate id attribute values.
  • Define Character Style
  • Specify that Character Styles are style elements with ttm:agent attributes matching the xml:id of the ttm:agent element for the Character
  • Character Styles can be applied to Script Events and Text objects using the style attribute
  • Presentation processors must not associate them with character styles via any other mechanism, e.g. matching the ttm:agent attributes only. Note and example also included.
  • Permit other non-Character Style styling including inline
  • Tweak text that permits

    elements to contain mixed content

  • Tweak note about the order of

    elements mattering, for grammar.


Preview | Diff

@nigelmegitt nigelmegitt linked an issue Nov 29, 2022 that may be closed by this pull request
@nigelmegitt nigelmegitt changed the title Resolve #29 Clarify character styling and other styling requirements Nov 29, 2022
index.html Outdated Show resolved Hide resolved
index.html Show resolved Hide resolved
* Drive-by fix of a few linting/HTML syntax errors including removing two duplicate id attribute values.
* Define Character Style
* Specify that Character Styles are style elements with ttm:agent attributes matching the xml:id of the ttm:agent element for the Character
* Character Styles can be applied to Script Events and Text objects using the style attribute
* Presentation processors must not associate them with character styles via any other mechanism, e.g. matching the ttm:agent attributes only. Note and example also included.
* Permit other non-Character Style styling including inline
* Tweak text that permits <p> elements to contain mixed content
* Tweak note about the order of <p> elements mattering, for grammar.
* "one or more optional" is better written "zero or more".
* The representation of Character Styles is not dependent on whether or not a Character has a Character Style.
* Clarify that style elements without a ttm:agent attribute are allowed, and are simply not Character Styles.
@nigelmegitt nigelmegitt force-pushed the issue-0029-character-styles branch from 459a2af to b375a95 Compare November 30, 2022 17:02
Remove duplicate "be".
@nigelmegitt nigelmegitt merged commit 9548e18 into main Dec 1, 2022
@nigelmegitt nigelmegitt deleted the issue-0029-character-styles branch December 1, 2022 10:50
@nigelmegitt nigelmegitt mentioned this pull request Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Do we want to allow inline styles? Do character styles override event-level styles or the opposite?
2 participants