[Date Prev][Date Next][Thread Prev][Thread Next][Thread Index]
RE: [XaraXtreme-dev] UNICODE problems in cxfrec [Fwd: [XaraXtreme-commits] Commit Complete]
- From: "Gerry Iles" <GerryI@xxxxxxxx>
- Date: Mon, 31 Jul 2006 18:00:27 +0100
- Subject: RE: [XaraXtreme-dev] UNICODE problems in cxfrec [Fwd: [XaraXtreme-commits] Commit Complete]
While writing just the low byte of a TCHAR as an ascii char isn't
strictly correct, it shouldn't actually get used much. It certainly
gets used in the document header record and it also seems to be used in
export hint records (where it should be safe) and also in the export
info records saved by the name gallery code (it writes a class name so
this should also be safe).
These really do all need fixing. There is also this bit at the top of
// This define has different meaning under linux
...which looks somewhat dodgy...
From: owner-dev@xxxxxxxxxxxxxxxx [mailto:owner-dev@xxxxxxxxxxxxxxxx] On
Behalf Of Alex Bligh
Sent: 31 July 2006 17:27
Cc: Alex Bligh
Subject: [XaraXtreme-dev] UNICODE problems in cxfrec [Fwd:
[XaraXtreme-commits] Commit Complete]
There are a couple of other occurrences of this in the same file.
I am loathe to fix them as they are to do with saving. The
WriteASCII one looks particuarly dodgy. Can writing just the
low byte of a TCHAR be right?
$ Scripts/all.sh | xargs egrep -n "if(n)?def +UNICODE"