Hi Randy,
Hi Viktor,
For backwards compatibility (especially with legacy systems) I think
you need to also support Windows-1252 encoding.
In my understanding (which may be wrong), we have two categories:
- legacy
Subcategory may be Clipper (multiple versions even, as 5.2 and 5.3
isn't always compatible), and other products.
The goal here is to replicate exact collation of these products,
which also means the codepage involved should be whatever used in
those legacy products.
Original Clipper didn't use Windows-* codepages to my knowledge,
but rather the IBM* (aka DOS*) range.
- non-legacy
This can be anything, but to not make things overly complicated,
it's best to stick with existing standards and implement them well.
In this category we can implement Windows-*, ISO-8859-* and
any other CPs (including IBM* but without bugs or any compatibility
restrains).
Currently we have a little bit of both, *ISO and *WIN CPs are
probably all non-legacy, but it's at the moment difficult to tell
the exact status for the rest. While the goal of the rest is mostly
compatibility, not many of them were rigorously tested against
Clipper official and non-official legacy collations AFAICT.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
