Przemek,
It breaks Turkish CPs so we cannot use it in such form.
Ops... This could be solved easily with more patches but... :)
I'll add soon alternative method to register CPs.
Ok you do, thanks.
IMHO, NTXSPA is a very bad collation for Spanish, to me is a bug.
ES850 is better but can not share indices with Clipper.
While is the new method the issue is solved for local repositories.
Of course, not share with Turkish CPs. :(
Regards,
--
Xavi
Przemyslaw Czerpak escribió:
On Wed, 14 Oct 2009, Szak�ts Viktor wrote:
Hi,
Thank you. I'd like to ask Przemek to review these modifications,
as they are also altering the CP engine.
It breaks Turkish CPs so we cannot use it in such form.
I'll add soon alternative method to register CPs.
It will use 4 tables with 256 bytes each of them. One for
upper translation, second for lower translation, third for
sorting and forth with bits describing character attributes
(alpha, digit, upper, lower) for IS*() functions.
It will allow to automatically generate CP modules for Harbour
from Clipper applications what should definitely resolve the
problem for all programs which have to share data with Clipper.
Anyone will be able to create CP module for Harbour himself.
But for such definitions I have to change existing code used for
translations and update some code which now directly access
CharsUpper and CharsLower HB_CODEPAGE members (mostly GT code).
best regards,
Przemek
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
