RE: [AD] Proposal to kill non-UTF-8 support |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Eric Botcazou writes:
> In my mind, that's clearly a Bad Thing:
> - the burden is on the client,
But, has anyone (other than developers) actually understood and
sensibly used the current range of different encoding options?
I can't help thinking that a lot of people are going to find
it simpler if the lib just says "I speak UTF8, please talk to
me in that format", rather than "here's a huge collection of
different functions and conversion routines and possible sources
of buffer overflows and suchlike things that you need to think
about and understand and then decide what mode you want to
use (but you do risk addon packages being buggy if you set
anything too unusual that they haven't been tested with :-)
(I'm playing Devil's advocate here: not quite sure what I think
about the issue, but the current all-formats system does seem
a bit more complex than the problem really warrants)
--
Shawn