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

Jump to bottom

Encoding of & in XML Extract #926

Closed
svareg opened this issue Oct 24, 2019 · 2 comments
Closed

Encoding of & in XML Extract #926

svareg opened this issue Oct 24, 2019 · 2 comments
Assignees
@vvmruder
Labels
usergroup work This lable is used to mark issues which will be done by usergroup members

Comments

@svareg
Copy link
Collaborator

svareg commented Oct 24, 2019

The presence of the character & in the columns type_code or type_code_list on table LegendEntry and PublicLawRestriction prevents the creation of a valid XML-Extract.

This character should be encoded as & in the whole XML-Extract.

Thanks.
@kdeininger kdeininger assigned kdeininger and vvmruder and unassigned kdeininger Oct 28, 2019
@kdeininger kdeininger added the usergroup work This lable is used to mark issues which will be done by usergroup members label Oct 28, 2019
@CoNussberger
Copy link
Collaborator

Just as supplementary information: We have the same problem with & used in the "name" attribute of the "office" table.

@vvmruder vvmruder mentioned this issue Nov 11, 2019
Merged
@vvmruder
Copy link
Collaborator

I pushed changes to #939. Could you check in a test environment if it solves your issues?

vvmruder added a commit that referenced this issue Jan 9, 2020
@vvmruder
Merge pull request #939 from openoereb/improve_xml_encoding
58e0c26 
fix xml encoding, fixes #926
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vvmruder vvmruder

Labels
usergroup work This lable is used to mark issues which will be done by usergroup members
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@vvmruder @kdeininger @CoNussberger @svareg