Skip to content

Issues decoding leading escaped spaces when using Text.XML.Stream.Parse #74

@alexkalderimis

Description

@alexkalderimis

content and maybeContent both skip over leading escaped whitespace.

A minimal example is:

<term name="foo">&#160;&#39;&#160;</term>

where the content parses as: "'\160", rather than "\160'\160".

Note that trailing characters are treated correctly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions