On Mon, 07 Dec 2009, Szak�ts Viktor wrote: Hi,
> Ok I see. Although this also means that I can't use > it as native CP in an application. > You seem to have suggested that any app may use UTF-8 > even now. But maybe I misunderstood something. I understand > this needs UTF-8 sorting support (for ASORT(), <, > operators, > maybe else, plus these things in RDD, if DBCODEPAGE is > left to default also), which we don't have. > Although maybe we should protection to now allow to use > UTF-8 in _SET_DBCODEPAGE and RDD CP parameters extensions. You can use UTF-8 in _SET_DBCODEPAGE and _SET_OSCODEPAGE. I only blocked setting such code page in _SET_CODEPAGE because it does not support any national settings. If you unblock it then it will work just like "EN" CP. best regards, Przemek _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
