As advised by the good folks on the list, custom properties are capable of
storing Unicode text, but typing it in the Contents window of the property
inspector is not a good idea. Instead, establish the text in a field first,
then assign it to the custom property from the unicodeText of the field.
Slava Paperno wrote:
Has anyone successfully stored and retrieved non-Roman text using a custom
property?
Is my syntax wrong?
get the cDefaultText of field "MyField"
set the unicodeText of field "MyField" to it
This may be helpful or it may be a red herring, but FWIW I've had
robust, predic
Hey Slava,
custom properties are binary, so it should work. What I suspect not to be
working is using the Inspector to set it (I am highly suspicious that it uses
the TEXT of the field, not the UnicodeText and so you lose some bytes).
Try a different field called "myInput". Then in a button: