[M3devel] AND (…, 16_ff)… Not serious - or so I hope!

[Dragiša Durić]

Also… If we add length info to TEXT fragments, we might as well add encoding info :).

So, most of TEXT fragments in memory will use same (system default) encoding but there will also be a way to mix them, convert to system default or anything some API (like Win32) requires.

On Jun 26, 2012, at 9:38 PM, Dirk Muysers wrote:

> So let them hate it. Memory is not a problem anymore.
> 
> --------------------------------------------------
> From: "Hendrik Boom" <hendrik at topoi.pooq.com>
> Sent: Tuesday, June 26, 2012 8:19 PM
> To: <m3devel at elegosoft.com>
> Subject: Re: [M3devel]AND (…, 16_ff)… Not serious - or so I hope!
> 
>> On Tue, Jun 26, 2012 at 12:18:41PM +0200, Dragiša Durić wrote:
>>> This piece of code, from TextClass.m3, disturbs me… a lot.
>>> 
>>> If we are to use WIDECHAR, I think we must be a lot more serious than this.
>>> 
>>> Probably, text pieces are limited to 128 bytes by design, somewhere. But - whose idea was to "narrow" by ignoring everything except 8 LSB's? By mapping set of 2^20 elements to set of 2^8 elements.
>>> 
>>> Probably by someone whose mother tongue is fully writeable with ASCII :).
>> 
>> I'm told the Japanese hate UTF-8, because it expands  their characters
>> from two bytes to three.
>> 
>> -- hendrik