FW: GME Meta bug

[GME]

----------
From: 	Sandeep Neema
Sent: 	Monday, November 18, 2002 10:37:49 AM
To: 	GME Group
Subject: 	RE: GME Meta bug
Auto forwarded by a Rule

Thanks!! I had tried escaping in my prompt specification, but I was missing the semicolon in the escaping “<”
 
-----Original Message-----
From: GME Group 
Sent: Monday, November 18, 2002 10:33 AM
To: GME List
Subject: FW: GME Meta bug
 
 

----------
From:   Andras Lang 
Sent:        Monday, November 18, 2002 10:33:23 AM 
To:        GME Group 
Subject:       RE: GME Meta bug 
Auto forwarded by a Rule
 
The problem with CDATA is: 
    Everything inside a CDATA section is ignored by the parser!
 
I think the best solution is to use the xml own escape characters:
 
<
<
less than
&gt;
>
greater than
&amp;
&
ampersand 
&apos;
'
apostrophe
&quot;
"
quotation mark
 
 
Andras
 
 
  -----Original Message-----
From: GME Group 
Sent: Monday, November 18, 2002 10:13 AM
To: GME List
Subject: FW: GME Meta bug
 

----------
From:   Tamas Paka 
Sent:         Monday, November 18, 2002 10:12:48 AM 
To:        GME Group 
Subject:       RE: GME Meta bug 
Auto forwarded by a Rule
 
I think, the best solution would be that we use <![CDATA[ ... ]]> for those values where XML-reserved characters may occur (i.e. almost anywhere , except of name, kindName and so on). 
The format of the latter values are forced by constraints.
 
Tamas
I am using ">" symbol in one of my attribute prompts. Here is a snippet from the generated .xmp file:
 
      <attrdef name="AbsoluteLowerBound" metaref = "1149" valuetype = "string" defvalue = "">
         <dispname>> (mandatory) :</dispname>
      </attrdef>
 
GME barfs when trying to register this xmp file, which is quite obvious. My question is: Shouldn't the meta-interpreter be automatically generating escape sequences for xml-reserved characters? Peter, is there a separate buglist for reporting Meta-environment bugs?
 
Sandeep