On Mon, 05 Oct 2009, Szak�ts Viktor wrote: Hi,
> Just tested it, and visual glitches are now all gone in > GTWVT UNICODE mode. Thank you very much. Fine. I would like to ask about keeping some builds in UNICODE mode so thay can be tested in the future. AFAIR UNICODE mode was fully functional about two years ago and we lost it by some modifications which were not well tested. I hope that now all basic GTWVT functionality > What remains is the char encoding problem. It seems as > if in UNICODE mode the HB_GTI_CODEPAGE setting is ignored. Yes it is and it's intentional. HB_GTI_CODEPAGE is MS-Windows only extension used in non UNICODE mode. Use hb_setTermpCP()/hb_setKeyCP()/hb_setDispCP() just like in all other GTs. See tests/gtchars.prg > I'm getting line-drawing chars in place of 852 accented chars. see above. > [ Something similar happens in UNICODE GTWIN, but there I'm > seeing '?' chars. ] GTWIN was never updated to work internally in UNICODE mode so I guess it has problem with non ASCII characters. It should be quite easy to add support for UNICODE mode for someone who can verify the results on the screen. best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
