<HTML><HEAD>
<STYLE><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></STYLE>
</HEAD>
<BODY class=hmmessage dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>Yes, I think UTF-8 CHAR is the way to go. Nearly all recent Un*x
libraries</DIV>
<DIV>use it by now. Only Microsoft sticks to CHAR16 nowadays. I have
a<BR>UTF-8 TEXT implementation in the making and don’t have the time,</DIV>
<DIV>these days, to complete it. It has a constant time cursor to
sequentially</DIV>
<DIV>access this encoding, support for character properties, dynamic </DIV>
<DIV>text building and formatting, and NLS (National Language support),</DIV>
<DIV>and will have an XML reader. Finished: TEXT implementation, and char</DIV>
<DIV>props. Partially finished: Dynamic buffer and NLS. Unfinished so
far:<BR>Formatting and XML. The software is called libunicode.</DIV>
<DIV>As for Win32, most software use dynamic translation to CHAR16,</DIV>
<DIV>when required, eg Component Pascal for .Net, GTK, golang etc.</DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV style="FONT: 10pt tahoma">
<DIV><FONT size=3 face=Calibri>leaving it the craggy island it is.</FONT></DIV>
<DIV><FONT size=3 face=Calibri></FONT> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=jay.krell@cornell.edu
href="mailto:jay.krell@cornell.edu">Jay K</A> </DIV>
<DIV><B>Sent:</B> Saturday, November 30, 2013 10:06 AM</DIV>
<DIV><B>To:</B> <A title=m3devel@elegosoft.com
href="mailto:m3devel@elegosoft.com">m3devel</A> </DIV>
<DIV><B>Subject:</B> [M3devel] how to represent a 16bit char?</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV dir=ltr>1) Ok for purposes of interfacing with Win32 and Xlib, what should
I use where WIDECHAR used to be correct?<BR>2) Are we really certain that
redefining WIDECHAR is the way to go?<BR>Not, say, introduce a new time, CHAR32
or UCHAR32?<BR>And maybe add an explicit alias CHAR16 or UCHAR16 to provide a
type that nobody will ever consider changing?<BR> <BR>Or do people now
advocate: <BR>get rid of WIDECHAR <BR>leave 8 bit CHAR <BR>with a new
understanding that it is UTF-8 encoded, and force lots conversion back and
forth? <BR>?? <BR> <BR>Thank you,<BR>-
Jay<BR><BR><BR><BR> <BR></DIV></DIV></DIV></DIV></BODY></HTML>