I've written a mod tool for a community of flight sim addicts, but they are having problems running it.

Loading an aircraft only works on English language versions of windows. The aircraft are in a very complicated format. There are multiple mesh files per aircraft, some are in a text file format and some in a binary format. Naturally I use a TextReader and a BInaryReader as required.

It's coded in C# as a winforms application with XNA embedded as a renderer.

The exception seems to be the "Invalid number sequence" exception you get when you read a multi-byte character by accident when you want to read a byte.

I know this can happen on a call to PeekChar, so I deliberately avoided using that.

Does anyone know any other functions that can produce the same error?

The results are looking good for me but the whole project is a failure if I cannot get it working for everyone else.

On a float ? Wow never thought of that. Guess I've got a lot of find and replaces to do.

Thanks Hodgman

Changing all my Float.Parse worked. (Thank you very much for that hint)

What I don't understand is why 1.0 cannot be processed regardless of language.

If one language uses 1,0 that's fine, but it shouldn't be a replacement for a 1.0, rather a new case to consider..

Supporting both is sensible, throwing an exception is just silly. Would you expect to write float x = 1,0; in a c++ file?

Without talking to you guys I would have never even considered Float.Parse as an issue.

Guess I have one more thing to worry about

In Swedish, numbers are supposed to be written with a space between all thousand groups and a comma as decimal separator. I have a comma button on my numpad, not a dot one. Other countries use an apostrophe or similar for their thousands while English uses comma for thousands and dots for their decimals. I think it's great that the default is to use locale specific formatting, but it would have been much better if these format differences didn't exist. I wish they had standardised them instead.

I actually had a laugh about this today, now that the app is working of course, wasn't laughing before.

When Microsoft started pushing XML, I was totally against it. I could not accept the massive increase in file size that storing a text version of a number instead of the binary version created.

As usual, I was ignored and we all use XML all the time now.

Now I find out that storing a number in a text format can produce massive internationalisation problems

Maybe it's just me, but I find that highly amusing.