Re: Using libunistring for string comparisons et al

[Ludovic Courtès]

Hi Mark,

Mark H Weaver <address@hidden> writes:

> I have a compromise proposal, which could be implemented for 2.0.x:
>
> We keep wide (UTF-32) stringbufs as-is, but we change narrow stringbufs
> to UTF-8, along with a flag that indicates whether it is known to be
> ASCII-only.

The whole point of the narrow/wide distinction was to avoid
variable-width encodings.  In addition, we’d end up with 3 cases (ASCII,
UTF-8, or UTF-32) instead of 2, which seems quite complex to me.

What do you think of moving to narrow = ASCII, as I suggested earlier?

Thanks,
Ludo’.