and in some places 0xFFFD is used, which is "REPLACEMENT CHAR"
I think we should sync all the cps in this regard.
Brgds,
Viktor
On 2008.11.02., at 22:49, Szakáts Viktor wrote:
Sorry, 1253 and 1254 are counter examples, but the
trend really looks like to leave these positions
0x0000.
Brgds,
Viktor
On 2008.11.02., at 22:12, Szakáts Viktor wrote:
Hi Przemek,
I'm converting a few remaining Unicode conversion tables
to the Harbour format, but I cannot decide based on the
existing ones, whether the correct behavior for non-defined
Unicode char positions should be zero or the normal ASCII
char itself?
F.e. 0x90 in uc1257.c is zero, while in uc1250 it's 0x09,
officially this position is UNDEFINED in both of these.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour