You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Builder-Options allow to specify a custom encoding.
However this has no effect, except changing the xml declaration.
According to the XML spec:
... it is a fatal error for an entity including an encoding declaration
to be presented to the XML processor
in an encoding other than that named in the declaration, ...
Browsers and NodeJS support multiple encodings. It would be great if xmlbuilder-js would support this too.
To be clear, changing the encoding can have an impact on the XML representation.
Unsupported character need to be escaped with numeric character references.
The Builder-Options allow to specify a custom encoding.
However this has no effect, except changing the xml declaration.
According to the XML spec:
Browsers and NodeJS support multiple encodings. It would be great if xmlbuilder-js would support this too.
To be clear, changing the encoding can have an impact on the XML representation.
Unsupported character need to be escaped with numeric character references.
Example in UTF-8:
Same example in ISO-8859-1:
The text was updated successfully, but these errors were encountered: