> We can not support all character sets, not even other variants of > ISO-8859-<whatever>, unless we know the encoding _before_ we start > processing the input. Even *if* we would know, we would need all > kinds of character mapping tables for all possible character sets.
I agree that it probably isn't possible to perform a totally automatic and correct conversion on different character sets without some means of being able to select the desired character set. What I had envisaged, but don't know exactly how to implement, is a system where known converters can register themselves. There would be an option on the file chooser to allow the user to select from the list of known converters. The "default" one could be set via LOCALE or a preference. If the "wrong" converter is used, it would just give unexpected / undefined characters on the display, so the user would be able to change the converter selection and try again. Something like that anyway. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
