Still jumping without thinking… If native char 202 or unicode char 202 is a word boundary in Windows it is a real bug — but is that the case?
Native char 202, a non-breaking space, should (or maybe shouldn’t) be a word boundary in Mac - the docs say word boundaries are space, tab and return. Whether the change between versions of LC is bug or not is questionable, but not one which will be addressed in current versions (a deprecated bug?). One of course should not be using chars at all. NumtoCodepoint(202) is circumflex E on the Mac, and is not a word boundary, and surely that is also the situation on Windows. Neville _______________________________________________ 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
