Hi Clive,
> But I'm curious why an assumption like this (1 byte =3D=3D 1 character) > would simplify your record packing problem. It is not the "coding" that concerns me, it is the storage.
I have to pack a huge amount of data into the Palm. Unless I am= fundamentally mistaken, double byte characters will require twice as much storage per string as single byte= characters.
I think maybe there is a fundamental misconception here. A "double-byte" encoding such as Shift-JIS is more accurately described as a "mixed-width" encoding, where every character occupies either one OR two bytes in a string.
So the "twice as much storage" requirement only exists if the character in fact actually needs two bytes to represent it (as is the case for Kanji, Hiragana, full-width Katakana, etc).
-- Ken -- Ken Krugler TransPac Software, Inc. <http://www.transpac.com> +1 530-470-9200
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
