Hi Viktor,
For backwards compatibility (especially with
legacy systems) I think you need to also support Windows-1252 encoding.
Regards,
Randy.
At 09:03 AM 11/3/2008, you wrote:
Hi Przemek and all,
Here are the results. (official C5.2e and C5.3b ones,
plus three unofficial HU ones).
To fully replicate these, we'd need to add the whole
tables (from 0-255) to our compatible collations.
I can do this if it seems useful.
Brgds,
Viktor
On 2008.11.03., at 13:36, Szakáts Viktor wrote:
Hi Przemek,
I've been following the instructions in these files, which
say, the first string should be the exact same string as
the second, but in upper case. Now, in French these accented
chars are present in IBM850, so they should IMO be included.
Accented chars in French are also considered with the same
weight as unaccented versions (accented ones are not part
of the official alphabet per se).
Because there wasn't any indication of the strange previous
behavior in the file, I cannot tell the reason behind it.
Maybe it was Clipper compatibility.
I've found original Clipper ntxfre.obj and mdxfre.obj, and
for one thing (and on first binary spot) they seem to be
different from each other. And they are both different from
both the old Harbour version and also probably from the
current one. I'll do some tests ASAP.
You're right though that such Clipper compatibility
comments are useful, I've added such for all HU collations
long ago. Maybe we should keep simply name those collations
XXYYYC to indicate the fact. Regarding the future and
because collations have more implications than just
indexing, I'd vote to try to be as close to the official
(or practical) language standards as possible (while
keeping the Clipper compatible ones in parallel).
Brgds,
Viktor
On 2008.11.03., at 13:17, Przemyslaw Czerpak wrote:
On Mon, 03 Nov 2008, Szak�ts Viktor wrote:
Hi Viktor,
* source/codepage/cpfr850.c
! Fixed uppercase chars.
Are you sure that this modification is correct. Such things should be
done by users who know and use given language. And of course it
should
be checked with Clipper because it may break binary compatibility in
index files.
We should document which CPs are Clipper compatible and should not be
touched.
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
