For what it's worth glyph 226 (Hex E2) in Unicode has a â (a
circumflex), and glyph 232 (Hex E8)
has a è ( e grave): so your initial font seems Unicode compliant
Here's a good place to check this sort of thing:
https://www.unicode.org/charts/
(this is, in some respects, my spiritual home on the internet).
Now: knowing that that font is Unicode compliant you should be able to
transform things
back and forth between characters and numbers using numToCodePoint and
codePointToNum.
I'm not sure why you are having trouble importing these characters.
A 'trick' is to do something like this:
set the unicodeText of field "fiddlyDo" to the unicodeText of WHATHAVEYER.
Richmond.
On 4.06.2018 02:31, David Epstein via use-livecode wrote:
I am importing some text where certain characters do not look right. When I
test their charToNum values I get, for example, 226 and 232. 226 is shown as a
comma, but should be a lower case a with a circumflex, and 232 is shown as an
upper case e with an umlaut but should be a lower case e with accent grave. Is
there some font I can choose, or some other action I should take, to get these
(and others) to display properly?
David Epstein
_______________________________________________
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
_______________________________________________
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
