compiling app with unsigned char breaks wx/mimetype.h in 2.8.0rc1

[Alicia da Conceicao]

>> But the developers who specified the ISO-8859 standards and write non-
>> English applications often used unsigned-char.  That is why the unsigned-
>> char is an option is every modern "C" compiler.
> Interesting point of view. I always thought that this option exists only
> because the C standard doesn't specify if char is signed or not and so a
> portable C program has to work with both signed and unsigned char by
> default. This is also why it's a bad idea to rely on char being unsigned as
> you do, or at least why using unsigned char explicitly is a much better
> one.

Hi VZ:

That is where you and I agreed. It is a bad idea to rely on char being signed
or unsigned.  Which is why ALL LIBRARIES should allow for both!  If one
library requires signed-chars and another other library unsigned-chars, then
the user application can't use both, even if end user application is character
sign neutral.  I do hope that future wxWidgets releases will continue to be
sign neutral.

Still, I have never ever seen any international text encoding standard that
specifies negative character values, so I am still baffled as to why anyone
would want a signed character.  The "ç" cedilla/cedilha in my last name is
specified as 199 not -57.

Anyways, sorry for venting.  As a Portuguese born immigrant who has
lived in Europe, North America, and Asia, I am very sensitive to multi-
lingual support and international (especially ISO) standards.

Alicia.