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
It seems that if to_xml() is called to produce a XML file, certain conditions can cause a XML with invalid syntax to be produced.
This happens whenever there are custom attributes in a waypoint. Even though the regular attributes seem to escape properly (e.g. & to &), this validation doesn't seem to be done for the custom attributes. Here is an example of a failure case:
This is invalid XML cause there is a disallowed ampersand at line 7 (drinks & coffee).
This can easily be reproduced by using a GPX file with custom attributes (e.g. from OSMAnd in this case) that contain any of the special characters that are invalid in XML such as &.
The text was updated successfully, but these errors were encountered:
It seems that if
to_xml()
is called to produce a XML file, certain conditions can cause a XML with invalid syntax to be produced.This happens whenever there are custom attributes in a waypoint. Even though the regular attributes seem to escape properly (e.g.
&
to&
), this validation doesn't seem to be done for the custom attributes. Here is an example of a failure case:This is invalid XML cause there is a disallowed ampersand at line 7 (
drinks & coffee
).This can easily be reproduced by using a GPX file with custom attributes (e.g. from OSMAnd in this case) that contain any of the special characters that are invalid in XML such as
&
.The text was updated successfully, but these errors were encountered: