Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Dean Roddey]

I'm not sure you want to do anything about this or not. But one our customers was trying to load his exported XML file, and it wasn't working. He sent it to me and it's because an invalid character being generated:

The production for XMLChars is:

Char    ::=    #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]

So only 3 chars below space are allowed. There were trailing \x04 characters on some of his lines. The stuff it was on was actually source code. I'm not sure why source code is in the database but it looked like it was all legitimately there, not just junk.

Anyway, though you guys are correctly escaping characters, you aren't filtering for illegal ones, and it might save a lot of sanity down the line if you would warn about this during the export process.

[Dean Roddey]

Just making sure that someone has seen and acknowledged this problem? There doesn't seem to be any other official way to report errors, so I just want to know that this problem has been noted.

[JimH]

We'll see if we can duplicate the problem.

[Dean Roddey]

From what he said, I guess when you do an automatic scan for files, that it will pick up development projects or source files? They were clearly supposed to be there, since they were marked as such in the exported XML, so I assume they were legitimately imported.

So that means that you can effectively import random data, and unless you are explicitly checking that text files you import really are just text, then this problem will happen, since you'll then export it back out and generate invalid XML.

[JimH]

It's entirely possible.  This is, for the most part, an area that's little explored in MC.  But we'll try to make it right.  Thanks for reporting it.