Hello,
Le 20/07/2018 à 00:48, Antonio Scuri a écrit :
> Following this line of reasoning, why are both UTF-8 and ISO-8859-1
needed in IUP source? Shouldn't the project choose one for source, and
convert to the other at runtime only for APIs (Microsoft?) which need it?
UTF-8 support in IUP has just a couple of years. So we need a way to
test everything without compromising well established projects. And we
did not want to penalty one or another with a conversion that could be
done previously.
Also text editors took sometime to be UTF-8 friendly, so we decided
to use ISO-8859-1 for our text encoding. And to explicitly show where
UTF-8 dual bytes were used. So we can quickly identify encoding problems.
IEC 8859-1[5] and Windows-1252 are not equivalent :
https://en.wikipedia.org/wiki/ISO/IEC_8859-1#Windows-1252
In the long run UTF8 is a better alternative because all systems
converge on this solution, even Windows :
https://stackoverflow.com/questions/166503/utf-8-in-windows#50217129
Regards,
--
Stéphane Aulery
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Iup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/iup-users