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

non valid XML Content documentation #72

Merged
merged 2 commits into from
Dec 7, 2021
Merged

non valid XML Content documentation #72

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
737aa68
non valid XML Content documentation
111andre111 May 22, 2020
be37382
Update docs/index.asciidoc
111andre111 Dec 3, 2021
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
9 changes: 9 additions & 0 deletions docs/index.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,6 +99,15 @@ By default the parser is not strict and thus accepts some invalid content.
Currently supported options are:

- `strict` - forces the parser to fail early instead of accumulating errors when content is not valid xml.

Control characters such as ASCII 0x0 are not allowed and _always_ result in non-valid XML.

XML 1.0 Spec: https://www.w3.org/TR/2008/REC-xml-20081126/#charsets

XML 1.1 Spec: https://www.w3.org/TR/xml11/#charsets

In case whenever XML Content is not valid, it will be tagged with a tag `_xmlparsefailure`.


[id="plugins-{type}s-{plugin}-remove_namespaces"]
===== `remove_namespaces`
Expand Down