> On Saturday 07 April 2007 22:02:29 Mariwan wrote:
> > Hi all,
> > It seems that even in fltk 2 the label is stile const char* declared.
> > Widget(int,int,int,int,const char* =3D0);
> >=20
> > Should not be ....const wchar_t*=3D0 , Is it wrong or what?
> > thanks for your reply
> > Mariwan
>
> As much as I know about FLTK 2.x, it only supports UTF-8 Unicode *encoding*.
> Size of "wchar_t" type is system specific, and may be 4 bytes (int) long,=20
> which is probably UTF-32 encoding and contains exact Unicode code-point (li=
> ke=20
> in Linux) or 2 bytes (short int) long, which is UTF-16 encoding (used in=20
> Windows and Java platform for example).
>
> UTF-8 is only Unicode *encoding*, it is not to be confused with compression=
> =20
> and there are several Unicode encodings (among which two are already=20
> mentioned above: UTF-32 and UTF-16) and every has it's pros and cons.
> UTF-8 uses *sequence* of bytes or characters (1 byte =3D=3D 8-bit, therefor=
> e=20
> UTF-8) to represent certain Unicode character and not only single "char"=20
> (byte). Don't mix this. So for example in Serbian, Cyrillic UTF-8 encoded=20
> letter '=D0=8B' is represented as two byte sequence "\xd0\x8b", that is two=
> =20
> *char's*.
>
> If you are new with all this, I suggest you first visit these two
Hi,
In fact I am not new with utf8 or the unicode. My question was about using
const char pointers to holde text which is not ansi. All comparision and class
name ...etc done in fltk will be based on ansi and not utf8. Look at the code.
when you have a lable with utf8 coding how can you compare it with another
string that could be also utf8*?
Mariwan
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
