Invisible character treated as word?

[Kay C Lan]

On Wed, Jan 28, 2015 at 9:11 AM, David Epstein <dfepstein at comcast.net>
wrote:

>
> Are there other characters that are always or sometimes invisible that
> cause the same problem?  And what is a remedy?
> Many thanks.
>

In the multi-line msg box:

put empty into msg
repeat with x = 0 to 255
put x & " = " & numToChar(x) & cr after msg
end repeat

On all English OSs the first 32 should be blank. On all English OSs the
chars up to 127 should be identical. On all English OSs char 127 should be
'intentionally blank'. On different OS the chars vary for chars 128 to 255.
On OS X char 202 is also 'intentionally blank' - no idea for Win or Linux.
ASCII 32 is a space, those lower than 32 may or may not cause the same
problem you are seeing.
My suggested solution is where ever the data originally came from, prior to
inputting into your fields, variables or custom properties, it should be
tested to confirm that the data only contains ASCII chars 48 to 57 (unless
you include thousand separators and or decimal points, in which case you'd
have to include their ASCII equivalents as well).

HTH