Opened 15 years ago
Closed 14 years ago
#1232 closed defect (fixed)
Maestro: does not properly escape GT symbol in map metadata
Reported by: | jbirch | Owned by: | jng |
---|---|---|---|
Priority: | medium | Milestone: | Maestro-3.0 |
Component: | Maestro | Version: | |
Severity: | major | Keywords: | |
Cc: | External ID: |
Description (last modified by )
When creating a MapDefinition, greater-than symbols within the map's MetaData are not converted to >
Maestro r4480
See package attached.
Attachments (1)
Change History (9)
by , 15 years ago
Attachment: | mypackage.mgp added |
---|
comment:1 by , 15 years ago
Description: | modified (diff) |
---|---|
Priority: | low → medium |
Severity: | trivial → major |
Summary: | Maestro: package creation does not properly escape GT symbol in map metadata → Maestro: does not properly escape GT symbol in map metadata |
Originally thought this was a problem with export because it showed as escaped in the editor, but MapAgent shows the unescaped value too.
comment:2 by , 15 years ago
Description: | modified (diff) |
---|
comment:3 by , 15 years ago
I'm guessing this is because of different serialization code than Studio? I've also noticed other things like utf-8 being in lowercase, quotes not being escaped to ", etc.
comment:4 by , 15 years ago
Milestone: | → Maestro-2.0 |
---|---|
Status: | new → assigned |
Should be easy to fix, but sounds very weird as the code does no manual handling of special chars.
comment:5 by , 15 years ago
Milestone: | Maestro-2.0 → Maestro-2.1 |
---|
Ok, I have done some testing, and you are correct; it does not escape those characters.
But for some reason the Xml with the unescaped characters is accepted by any program that I can test with, eg.: MapGuide itself, Firefox and IE.
This suggests that the escape is done correctly, even if it is different than I would expect.
http://www.w3.org/TR/REC-xml/#syntax
Describes that < MUST be escaped, where > MUST be escaped only in CDATA fragements.
I don't think I can fix Maestro so the output has those correctly escaped without writing a custom serializer.
comment:6 by , 15 years ago
Milestone: | Maestro-2.1 → Maestro-2.5 |
---|---|
Owner: | changed from | to
Status: | assigned → new |
comment:8 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Due to my inability to reproduce the problem in the 3.0 editor, I am assuming the issues was fixed with the rewrite.
Package containing (among other things) unescaped strings