XML parsing error

[bpducman]

When I try and import a sup, on 1 particular sequence I am getting a message

XML parsing error. 'not well-formed (invalid token)' at line 64555.

When I look at that line with Notepad++ it reads like
<timing centiseconds="16880">

Similar to the other lines just a different Number.

For the computer illiterate.

What's Up

Brad

[Gilrock]

Is the sequence from a paid for version of LOR and not a demo version?

[bpducman]

Yes Paid version

Licensed for the Advanced Edition with SuperStar 60_CCR

[bpducman]

I just sent Brian a note and asked him if this was a good copy that I purchased .

I will let you know what he says

B

[bpducman]

and his reply

I looked at my copy of SilentNight_16CCRs_archive.sup and the last line is line number 32786.

Not sure why their code would think there are 64,555 lines. Check with the xlights guys and I would be curious to know their answer.

 -Brian Bruderer

[Gilrock]

So the error isn't being returned by xLights code its coming from the wxWidgets XML parser library we use to read XML files.  SuperStar has been creating a lot of badly formed XML where some of the start tags don't have proper end tags so the wxWidgets XML parsers chokes on it.  What we have done is detected those situations and corrected the SuperStar XML file before we send it to the parser.  We already have a lot of code in place that does that.  We only do it for the tags that we have found to have issues.  When Brian adds new XML tags that don't have proper closing tags we have to figure out what new tag name has an issue and add the new tag name to the list of tags that we fix.  Its hard for me to fix without seeing the file.  I usually don't need any of the effect contents I just need all the major sections to see the tag names and see if they have the proper end tag.

A tag like <tagname> must have a closing </tagname> to be valid XML.

[bpducman]

the sup is 1782 KB

rather send you the complete file if that is ok

B

[Gilrock]

Ok click the email icon under my avatar.