#299 Support for UTF-8 term names needed ASAP

[David Osumi-Sutherland]

UTF-8 support is currently lacking:

Even if "allow extended characters" is chosen under text editor in the configuration manager. Pasting in a UTF-8 character into a name in OE causes a fatal error verification flag. Loading a file with a UTF-8 character in a name - the character is rendered by OE2 as its 2 character ascii equivalent as well as triggering the same 'fatal error' verification check flag.

It would be great if OE2 had complete UTF-8 support - i.e.- able to render, save and load UTF8 characters in any field (presumably excepting IDs and tag names.

[Midori Harris]

Is it a bug that the fatal error message appears even when the 'allow extended characters' box is checked?

(And if not, what is that option supposed to do?)
m

[Midori Harris]

SF 2212705 - 'unicode support' - is related, so I'm increasing its priority too.

https://sourceforge.net/tracker/?func=detail&aid=2212705&group_id=36855&atid=418260

[Nomi Harris]

I think term names can now include UTF-8 characters--can you check this and verify? If it doesn't work, please post one or more examples of term names that cause a fatal error.