[Bug] Custom font doesn't render non-english characters

[pindavka]

Describe the bug
I do not have a font in the cheat

Screenshots

Additional context
meteor 0.4.2, minecraft 1.16.5

[gigglingbed]

Thats because your language is not english, meteor custom font cannot render russian characters.

[RedCarlos26]

Is this a bug or it is just not supported?

[RedCarlos26]

Is this a bug or it is just not supported?

@seasnail8169 ?

[gigglingbed]

Its not really a bug, its known that non english characters don't work but it is something that would be nice to fix.

[SKevo18]

I am having the same issue - no text in the GUI is visible at all. I have just installed the mod (0.4.5, 1.17.1). No other mod except for Fabric API 0.40.1 is enabled. The language I am using is English (UK), switching to US doesn't help either. So this isn't always related to Minecraft's language.

[gigglingbed]

that is a separate bug, try toggling custom font

[gigglingbed]

wait actually no i have no idea what is happening there

[SKevo18]

I've done some more digging in the fonts folder, and managed to fix the issue. Here's what I did:

1. Navigate to %appdata%\.minecraft\meteor-client\fonts (this might vary if you use MultiMC - in that case, locate your instance folder)
2. When I tried to open JetBrains Mono.ttf, Windows said that "It is not a valid font file", although other fonts opened fine. This made me think that the JetBrains font is broken.
3. Remove the broken JetBrains Mono.ttf from the fonts folder.
4. Download a new one from https://www.jetbrains.com/lp/mono/
5. Locate JetBrainsMono-Regular.ttf in the downloaded ZIP
6. Rename it to JetBrains Mono.ttf and drop it in fonts (replace it).

This fixed my issue, and text is visible:

My assumption is that the font file got broken at certain point during my Meteor client installation. My problem was probably not related to this issue, but it might help others with the same issue. This should be put in the FaQ, I could make a PR for it.

[gigglingbed]

the font file isn't broken for anyone else so no it shouldn't be, it was clearly caused by something in your system or something you did