Hi Ben,
I think that the chunk names for unicode should be exactly the same as
for english text, but they should act differently if either the text
being operated on is unicode text or the useUnicode has been set to true.
Note that other development tools don't have this problem at all.
Operations on English text work the same way as on unicode text and
there is no need to even think about the encoding.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553
Use Color Converter to convert CMYK, RGB, RAL, XYZ, H.Lab and other
colour spaces. http://www.color-converter.com
Buy my new book "Programming LiveCode for the Real Beginner"
http://qery.us/3fi
LiveCode on Facebook:
https://www.facebook.com/groups/runrev/
On 3/11/2014 19:15, Benjamin Beaumont wrote:
Hi All,
We're in the process of adding some new chunk types in LiveCode 7 and we
would appreciate suggestions for a particular chunk name.
The new chunk types are:
naturalword (breaks on unicode word boundaries)
sentence (breaks on unicode sentence boundaries)
paragraph (Same behaviour as current 'line' chunk)
The first chunk is called 'naturalword' because 'word' is already in use.
Renaming the current 'word' chunk to 'token' to free up 'word' is not an
option for backward compatibility. We are also limited by the current
parser which doesn't allow us to use the form:
put natural word 1 of "this is a string of words"
'naturalword' is the clearest internal suggestion at the moment and we'd
love to get the input from community members if there is an even clearer
option.
Warm regards and thank you for your input.
Ben
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
