We’re embedding a TTF font file in our app using the JUCE binary data mechanism. The font only includes glyphs for latin and cyrilic languages, and so for langauges like Chinese, Korean, and Japanese we were relying on a fallback font being implicitly chosen.
On macOS this works as expected.
On Windows however, the text was completely blank - not even the placeholder [] characters were shown.
If we instead installed the font to the system, and used the juce::Font {"MyFont"} constructor, we had the expected behaviour where a fallback font was used for any glyphs that aren’t included in the specified font. However we don’t want to rely on the user having the font isntalled on their system - we want to be able to use an embedded font.
The returned result from juce::translate() is populated, so it’s something to do with the drawing of that text. We’re drawing the text using a juce::AttributedString.
I’ll try to find time to put together a PIP to reproduce the bug, but it should be as simple as using an embedded font and then trying to display a glyph on Windows that’s not included in that font.