A-OTF Shin Go Pr6N font wont work

[BPplays]

some fonts do not work. trying to use A-OTF Shin Go Pr6N doesn't work but using MS Gothic it does work. when using A-OTF Shin Go Pr6N it seems to be using a fallback but not telling me, putting in random keyboard smashing to the font options results in no difference to the font


my openttd.cfg:

Code: Select all

small_font = A-OTF Shin Go Pr6N
medium_font = A-OTF Shin Go Pr6N
large_font = A-OTF Shin Go Pr6N
mono_font = A-OTF Shin Go Pr6N
small_size = 12
medium_size = 14
large_size = 18
mono_size = 14
small_aa = true
medium_aa = true
large_aa = true
mono_aa = true

when using A-OTF Shin Go Pr6N and trying to read readme with japanese text (likly just the fallback font not supporting the characters):

Code: Select all

Unknown debug level 'freetype=1'
dbg: [sprite] 1244 extra sprites, 1244 from baseset, 0 from fallback
dbg: [sprite] 1244 extra sprites, 1244 from baseset, 0 from fallback
dbg: [sprite] 1244 extra sprites, 1244 from baseset, 0 from fallback
dbg: [fontcache] Font is missing glyphs to display char 0x3072 in mono font size
dbg: [fontcache] Font is missing glyphs to display char 0x3072 in mono font size
dbg: [fontcache] Font is missing glyphs to display char 0x3072 in mono font size
dbg: [fontcache] Font is missing glyphs to display char 0x3072 in mono font size

[skc]

That's an issue with the font, not with OTTD.

[BPplays]

but 0x3072 is ひ, a hiragana character that this japanese font has, i think its using a fallback font for some reason

[jfs]

My best guess is that the font needs to be selected by a different name for OpenTTD to find it.

[Auge]

Hello

Is it possible, that the spaces or the dash in the font name breaks it? On terminals and with some INI-parsers you need to enclose strings with chars with special meaning in quotes.

Code: Select all

small_font = 'A-OTF Shin Go Pr6N'

Tschö, Auge