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 escape in literal convention (#987). #1173

Merged
merged 2 commits into from
Nov 9, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion spec/ttml2.xml
Original file line number Diff line number Diff line change
Expand Up @@ -2187,6 +2187,7 @@ which corresponds to production [3] <code>S</code> as defined by <bibref ref="xm
<ulist>
<item><p>a literal term (specified within quotation marks), when present, must appear exactly as specified
(excluding the quotation marks themselves);</p></item>
nigelmegitt marked this conversation as resolved.
Show resolved Hide resolved
<item><p>the literal <code>&apos;\\&apos;</code> is interpreted as a single backslash, i.e., REVERSE SOLIDUS (U+005C);</p></item>
<item><p>concatenated (juxtaposed) terms mean that all terms must appear in the stated order, e.g., <code>a b</code> means that the terms
<code>a</code> and <code>b</code> are present and the former precedes the latter;</p></item>
<item><p>a vertical bar (<code>|</code>) separates two or more alternatives, of which exactly one must appear;</p></item>
Expand Down Expand Up @@ -15293,7 +15294,7 @@ non-ascii-or-c1
: [^\0-\237]

escape
: "\\" <emph><code>char</code></emph>
: &apos;\\&apos; <emph><code>char</code></emph>
</eg>
</td>
</tr>
Expand Down