Follow-up Comment #7, sr #109857 (project administration):

It's complaining it's not well-formed XML.  In particular, line 352 has an
ampersand as part of a URL and it pinpoints the 1 of 1.215 as an 'invalid
token'.  This is inside a "<content type='xhtml'" that starts on line 342.  I
suspect the ampersands there need to be escaped.

<p>For more detailed information you can look at <a
ChangeLog since 1.2</a>.


Reply to this item at:


  Message sent via Savannah

Reply via email to