#299 Support for UTF-8 term names needed ASAP

OBO-Edit 2.x
closed-fixed
OBO-Edit (271)
7
2011-09-22
2009-04-17
No

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.

Discussion

  • Midori Harris

    Midori Harris - 2009-04-18

    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

     
  • Nomi Harris

    Nomi Harris - 2011-09-15
    • status: open --> open-fixed
     
  • Nomi Harris

    Nomi Harris - 2011-09-15

    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.

     
  • Nomi Harris

    Nomi Harris - 2011-09-22
    • status: open-fixed --> closed-fixed
     

Log in to post a comment.