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

Draft prose about end-of-line handling #242

Merged
merged 3 commits into from
Apr 2, 2024
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
10 changes: 10 additions & 0 deletions src/ixml-specification.html
Original file line number Diff line number Diff line change
Expand Up @@ -557,6 +557,16 @@ <h2 id="parsing">Parsing</h2>
href="#cyk">CYK</a>], [<a href="#glr">GLR</a>], and [<a href="#gll">GLL</a>];
see also [<a href="#grune">Grune</a>].</p>

<p>Invisible XML processors normalize line endings when they read grammar and
input files. They apply the same rules as [<a href="#xml">XML</a>]: every
occurrence of the two character sequence <code>#d #a</code>, and any
<code>#d</code> not immediately followed by a <code>#a</code>, are translated
into a single <code>#a</code> in the input. This assures that the single
character <code>#a</code> can always be used to match an end of line,
irrespective of the conventions of the system where the files were created. It
follows that the iXML exclusion <code>~[#a]*</code> will always match all of the
characters to the end of a line.</p>

<p>If an input encoded in UTF-8 begins with a BOM, the BOM
<span class="conform">should</span> be ignored.</p>

Expand Down
Loading