TextEditor should support international characters via fallback fonts

TextEditor must properly support fallback fonts to allow JUCE applications and plugins to function properly for users whose alphabets and filenames include characters outside the latin alphabet.

Note that using Arial Unicode is not a long term solution, aside from the UI design limitation this imposes :-

Arial Unicode MS was originally commissioned by Microsoft Office as an extended version of the Arial typeface to support a large set of international characters. The font was included with Office but not Windows. Over time the Unicode standard grew to the point where it was not possible to include all encoded characters in a single font file, so today most applications rely on font linking or font fallback to provide appropriate language support when a selected font doesn’t include the characters you need. We stopped servicing and updating Arial Unicode and no longer install it as part of Office. However, updated versions of the font are available from Monotype.

It’s such a basic feature but never worked…

I know, it’s almost the difference between works for 20% of the worlds population or doesn’t :slight_smile:

2 Likes

Big +1 from my end, too! Our standalone app does a lot of text rendering also with string attributes (bold, italic, underline, strikethrough).

Since JUCE doesn’t have any fallbacks in place and Arial Unicode doesn’t have a bold font face, the user now needs to decide whether they want to have rich text editing (with a different font) or if he wants to work in “international” mode with wider glyph support but no rich text editing…

1 Like

Let’s write a subclass of TextEditor that supports this, so it can display characters other than English. Arial unicode is just not a valid workaround.

Arial Unicode MS was originally commissioned by Microsoft Office as an extended version of the Arial typeface to support a large set of international characters. The font was included with Office but not Windows. Over time the Unicode standard grew to the point where it was not possible to include all encoded characters in a single font file, so today most applications rely on font linking or font fallback to provide appropriate language support when a selected font doesn’t include the characters you need. We stopped servicing and updating Arial Unicode and no longer install it as part of Office. However, updated versions of the font are available from Monotype. Follow the links below if you have dependencies on it.