>> 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.
So, I'm afraid I'm confused. For sure I don't want to unblock it just for the sake of having it unlocked. But now I can't see why it cannot work as main CP, but can work as DB CP. I assume if it can be used in DB, sorting must be working, so I wonder what are those 'national settings'? Sorry to force the matter, but I'd like to see if it's possible to start in this direction already. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
