Re: byteoffset() in lutf8lib.c from 5.3, work2

[Coda Highland <chighland@...>]

On Tue, May 13, 2014 at 4:52 PM, Tim Hill <drtimhill@gmail.com> wrote:
>
> On May 13, 2014, at 4:45 PM, Sean Conner <sean@conman.org> wrote:
>
>> It was thus said that the Great Coroutines once stated:
>>> On Tue, May 13, 2014 at 3:41 PM, Sean Conner <sean@conman.org> wrote:
>>>
>>>>  If you are curious, check out the source code to joe (Joe's Editor),
>>>> specifically, the files i18n.c and utf8.c, to see just the amount of code
>>>> required to maybe, hopefully, handle UTF-8.  I have no idea how well it
>>>> deals with right-to-left languages.
>>>
>>> https://github.com/paul-schwendenman/joe-editor/blob/master/joe/i18n.c
>>>
>>> I am not a fan of the proliferation of wide characters :(
>>
>>  Well, if you want to handle checking for control characters, spaces, upper
>> case, lower case, numbers, combining characters or punctuation ...
>>
>>  -spc (i18n.c and utf8.c compile to about 31k on a 32-bit system ... )
>>
>>
>
> Just editorializing for a moment, when it first appeared Unicode was supposed to clean up the mess with codepages, all the various odd multi-byte character hacks (shift-JIS anyone?) and make multi-lingual applications far easier to code. Fast forward and I’m not sure that the “cure” is any better than the original problem. Any standard that has a “normalized” form that is in fact FOUR different forms is in trouble imho.
>
> —Tim

I mildly disagree. While I agree that Unicode isn't perfect, I think
it HAS successfully addressed the goals it set out to accomplish. In
my opinion and experience, Unicode is better than any extant
alternative.

/s/ Adam