On Thu, 01 Apr 2010, vatzct wrote: > 01.04.2010 12:03, vatzct написав(ла): > This is result of cpinfo from $Id: ChangeLog 14262 2010-03-30 > 19:55:52Z druzus $ > The cpinfo.txt: > 04/01/10 12:30:03 Windows XP 5.1.2600 Service Pack 1 Harbour > 2.1.0dev (Rev. 14111) > Character encoding: UA866 > ================================================== > upper: > "ABCDEFGHАБВГДЕЁЄЖЗИIЇЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯJKLMNOPQRSTUVWXYZ" > lower: > "abcdefghабвгдеёєжзиiїйклмнопрстуфхцчшщъыьэюяjklmnopqrstuvwxyz" > ================================================== > in console: > 04/01/10 12:32:27 Windows XP 5.1.2600 Service Pack 1 Harbour > 2.1.0dev (Rev. 1411 > 1) > Character encoding: UA866 > ================================================== > upper: > "ABCDEFGHCueaaa??aceI?eeiiiAAE??ooouuyOU?????JKLMNOPQRSTUVWXYZ" > lower: > "abcdefghaiounN+????i??┐???<>??????ч?????????jklmnopqrstuvwxyz" > ==================================================
For some GTs you should also use: HB_SETTERMCP( "UA866" ) to inform them about character encoding in string buffer. This requirement will be removed in UNICODE builds in the future when we switch internal screen buffer to operate on UNICODE values. best regards, Przemek _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
