XML world file format - problems loading

Posted by Storm Dragon on Sat 18 May 2002 02:57 PM — 6 posts, 21,108 views.

Denmark #0
Æ Ø Å
æ ø å

I use the three above characters in aliases because the
mud I use does not have any use for them, and also
because they are located near the middle of the keyboard
and I use them frequently
however now the world says: warning, unprintable character
and I then get: unexpected file format in a small window
I went into the world file and removed my aliases with the special characters and it loaded up, however, my triggers does not work!
Well some of the coloring ones..
Amended on Sat 18 May 2002 02:58 PM by Storm Dragon
Denmark #1
Another thing, all the triggers where I match on

white on black

it changed to black on black :P
USA #2
Hmm. I have to agree that non-standard characters being rejected is a major problem. Not only are 'most' of them above character 31 actually printable, but some of us so use them for things. In my case I use one that appears in the terminal font, but due to the complete rearrangement that was done in most so called 'modern' fonts appears as a blank to add hidden exits to rooms in my house. I use aliases that include those characters to navigate these hidden shortcuts and am now glad I haven't upgraded to the XML version of MUSHclient yet, since this bug would have been a nasty surprise. Even the truly unprintable ones are in some cases 'displayable' and have been used on rare cases for some games (though perhaps not muds).
Australia Forum Administrator #3
Hmmmm - on 8th May I said ...

Quote:

It might also help if you two, and anyone else with a large world file, emails me a copy of a representative sample.

You can de-identify it by removing character names, world names, IP addresses, passwords etc.

Then I can run that through the XML generator, and then re-parse it in XML, to find:

  • If it works; and
  • How much larger the file gets



Magnum sent me his file, and I did the following to it:

  • Saved it as XML (ie. File A -> File B)
  • Reloaded the XML version (ie. Loaded File B)
  • Re-saved as the "old" format (ie. File B -> File C)
  • Compared File A to File C. Once some minor bugs were fixed, File A and File C were identical - to the last bit!


After this process, I was reasonably happy with the XML conversion, however obviously he didn't use some "features" (like non-printable characters) that you are using.

My offer remains open (for now) - send me your file and I'll make sure it loads and saves, without being changed in any way (one file each please, I am not planning to test 1000 files). The more complex the file the better. :)

Storm Dragon - please be specific about what is not working about the triggers. All of Magnum's converted OK, so try to narrow down which parts are not. I'll investigate the "match colour" part.
Australia Forum Administrator #4
Quote:

Æ Ø Å
æ ø å

I use the three above characters in aliases because the mud I use does not have any use for them


Sorry, that was an unintended restriction. It was caused by a sign mismatch. The test was to reject characters < ' ', however because the character being tested was in a signed field, any character over 128 was rejected.

Fixed in 3.22.
Amended on Sat 18 May 2002 11:21 PM by Nick Gammon
Australia Forum Administrator #5
Quote:

Another thing, all the triggers where I match on

white on black

it changed to black on black :P


Hmmm - another subtle one slipped through. Fixed in 3.22.