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.

Sign up for GitHub

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

Expand explanation of "repair techniques" #2566

Closed
wants to merge 3 commits into from
Closed

Expand explanation of "repair techniques" #2566

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
689cef8
Expand explanation of "repair techniques"
patrickhlauke Aug 4, 2022
d92d197
Merge branch 'main' into patrickhlauke-issue2563
patrickhlauke Oct 25, 2024
ac9049f
Merge branch 'main' into patrickhlauke-issue2563
patrickhlauke Oct 29, 2024
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
5 changes: 3 additions & 2 deletions understanding/20/parsing.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,8 @@ <h2>Intent of Parsing</h2>
The intent of this Success Criterion is to ensure that user agents, including assistive technologies, can accurately interpret and parse content. If the content cannot be parsed into a data structure, then different user agents may present it differently or be completely unable to parse it. Some user agents use "repair techniques" to render poorly coded content.
</p>

<p>Since repair techniques vary among user agents, authors cannot assume that content
<p>Since these repair techniques - the way user agents will attempt to parse and error-correct
malformed or invalid markup - may vary among user agents, authors cannot assume that content
will be accurately parsed into a data structure or that it will be rendered correctly
by specialized user agents, including assistive technologies, unless the content is
created according to the rules defined in the formal grammar for that technology.
Expand All @@ -63,7 +64,7 @@ <h2>Intent of Parsing</h2>

<p>The concept of "well formed" is close to what is required here. However, exact parsing
requirements vary amongst markup languages, and most non XML-based languages do not
explicitly define requirements for well formedness. Therefore, it was necessary to
explicitly define requirements for well-formedness. Therefore, it was necessary to
be more explicit in the Success Criterion in order to be generally applicable to markup
languages. Because the term "well formed" is only defined in XML, and (because end
tags are sometimes optional) valid HTML does not require well formed code, the term
Expand Down