Unicode handling comparison

Walter Bright newshound2 at digitalmars.com
Thu Nov 28 18:34:45 PST 2013


On 11/28/2013 11:32 AM, Dmitry Olshansky wrote:
> I had a (a bit cloudy) vision of settling encoded ranges problem once and for
> good. That includes defining notion of an encoded range that is 2 in one: some
> stronger (as in capabilities) range of code elements and the default decoded
> view imposed on top of it (that can be weaker).

I suspect the correct approach would be to have the range over string to produce 
bytes. If you want decoded values, then run it through an adapter algorithm.



More information about the Digitalmars-d mailing list