Re: [AD] Proposal to kill non-UTF-8 support

[Peter Wang <tjaden@xxxxxxxxxx>]

On 2002-01-04, Vincent Penquerc'h <Vincent.Penquerch@xxxxxxxxxx> wrote:
> But given the way it's done at the moment (via pointers to
> functions), I'd say that supporting UTF-8 is no more hard
> than supporting any possible Unicode format if the framework
> (which will have to be there for UTF-8 support anyway) is
> clean and robust.

It's not the framework that's the problem, but rather the fact that
any encoding format could be in use.  Taking the simplest example, you
can't even do:

	textout(..., "an ASCII string", ...);

but rather you have to do:

	char buf[SOMESIZE];
	textout(..., uconvert_ascii("an ASCII string", buf), ...);

User programs can choose to only care about one particular encoding,
but authors of addons don't have that luxury.


Therefore proposal #2: Get rid of set_uformat().

Then all strings are expected to be UTF-8, but other encodings and
convertors still exist for interacting with the Real World.  I don't
think it creates any new problems and it'll help us lazy people who
hate uconvert_ascii().