On 08/16/2011 10:51 PM, Mark Schonewille wrote:
Hi Richmond,
I wrote this yesterday already. The availability of byte and char indicate that
RunRev is aware of this problem. Unfortunately, RunRev hasn't actually taken
action to solve it yet.
For now, it is just a fact that fields who have the
Hi Richmond,
I wrote this yesterday already. The availability of byte and char indicate that
RunRev is aware of this problem. Unfortunately, RunRev hasn't actually taken
action to solve it yet.
For now, it is just a fact that fields who have the unicodeText property set,
need two bytes for a c
I'm going to say that if you were to delete the first char of a 2 byte unicode
char and then put more unicode text after it, things would not go so well, but
I am just guessing.
Bob
On Aug 16, 2011, at 12:06 PM, Richmond Mathewson wrote:
> I did this:
>
> set the useUnicode to true
> set th
