[M3devel] how to represent a 16bit char?

[Jay]

Sorry sent too soon. Windows is basically WCHAR everywhere except at boundaries that must accept multiple encodings...

 - Jay

On Dec 1, 2013, at 12:33 PM, Jay <jay.krell at cornell.edu> wrote:

> A lot of code within Windows uses WCHAR all the time. The kernel interfaces all accept only WCHAR (and a 16 bit length of bytes). FAT32, NTFS, registry all store 16bit WCHAR, at least when 7bits don't suffice.
> 
> 
> Trestle surely will remain with Xlib & Win32. New code...Qt?
> 
> 
>  - Jay
> 
> On Nov 30, 2013, at 2:52 AM, Dragiša Durić <dragisha at m3w.org> wrote:
> 
>> And yes, Cairo uses UTF-8 natively, even on Windows.
>> 
>> On 30 Nov 2013, at 11:41, Dragiša Durić <dragisha at m3w.org> wrote:
>> 
>>> Are we really sure about this Xlib interfacing?
>>> 
>>> There are several very-low-level and very-portable libraries right now. Why don’t we use Cairo?
>>> --
>>> Dragiša Durić
>>> dragisha at m3w.org
>>> 
>>> 
>>> 
>>> On 30 Nov 2013, at 10:06, Jay K <jay.krell at cornell.edu> wrote:
>>> 
>>>> 1) Ok for purposes of interfacing with Win32 and Xlib, what should I use where WIDECHAR used to be correct?
>>>> 2) Are we really certain that redefining WIDECHAR is the way to go?
>>>> Not, say, introduce a new time, CHAR32 or UCHAR32?
>>>> And maybe add an explicit alias CHAR16 or UCHAR16 to provide a type that nobody will ever consider changing?
>>>>  
>>>> Or do people now advocate: 
>>>>  get rid of WIDECHAR 
>>>>  leave 8 bit CHAR 
>>>>  with a new understanding that it is UTF-8 encoded, and force lots conversion back and forth? 
>>>> ?? 
>>>>  
>>>> Thank you,
>>>>  - Jay
>> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20131201/a5419881/attachment-0002.html>