Opened 14 years ago

Closed 13 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 jbirch)

When creating a MapDefinition, greater-than symbols within the map's MetaData are not converted to >

Maestro r4480

See package attached.

Attachments (1)

mypackage.mgp (7.2 KB ) - added by jbirch 14 years ago.
Package containing (among other things) unescaped strings

Download all attachments as: .zip

Change History (9)

by jbirch, 14 years ago

Attachment: mypackage.mgp added

Package containing (among other things) unescaped strings

comment:1 by jbirch, 14 years ago

Description: modified (diff)
Priority: lowmedium
Severity: trivialmajor
Summary: Maestro: package creation does not properly escape GT symbol in map metadataMaestro: 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 jbirch, 14 years ago

Description: modified (diff)

comment:3 by jbirch, 14 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 ksgeograf, 14 years ago

Milestone: Maestro-2.0
Status: newassigned

Should be easy to fix, but sounds very weird as the code does no manual handling of special chars.

comment:5 by ksgeograf, 14 years ago

Milestone: Maestro-2.0Maestro-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 jng, 14 years ago

Milestone: Maestro-2.1Maestro-2.5
Owner: changed from ksgeograf to jng
Status: assignednew

comment:7 by jng, 14 years ago

Can't seem to reproduce this in 3.0

Is this still the case?

comment:8 by jng, 13 years ago

Resolution: fixed
Status: newclosed

Due to my inability to reproduce the problem in the 3.0 editor, I am assuming the issues was fixed with the rewrite.

Note: See TracTickets for help on using tickets.