MacArthur, Ian (SELEX GALILEO, UK) wrote:
> Well, the Windows way was to use the MS API to convert your strings into > the local MBCS (multi-byte characters) and use that to display your > strings. The idea was that the winXX OS would know what the current > "code page" (and so forth) were and perform the correct encoding to > display your string. > It pretty much works, but can be tricky to use... I can just write own conversion, but then, on Win98, I should send data to FLTK in utf-16 or extended ascii code page (windows-1250)? But... if I send just encoded bytes, instead of UTF-8, will that not full FLTK? Like, FLTK seems to count number of characters etc assuming data is UTF-8, so if it something that looks like utf-8 but is cp-1250 then fltk will incorrectly count number of glyphs and have trouble displaing...? Also, how to detect if Im on win98? _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
