New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: font (A-OTF Shin Go Pr6N) not working #11054
Comments
Does that font have a character at code point 0x3072? |
it does 0x3072 is ひ (hi) a hiragana character, this font is japanese so it has the character, it seems to be using a fallback font. my language is set to english and it dosnt give me any dbg: [fontcache] Font is missing glyphs to display char error but still seems to be using a fallback. i made i python script to check all the characters in the langfiles i got here from github and it says there are no missing characters in the whole english us langfile ive tried setting the font with the console it seems to be saying the font is set the arial after i do which i assume is the fallback also the font is otf idk if that matters |
|
here is my log, but i think its just using the fallback font, this is my whole log, what im confused about is that its giving me no error about missing glyphs when starting the game but still wont use the font and only seems to error cus the fallback font dosnt support kana when reading a readme with japanese text.
|
This particular font isn't freely available, so it's not something we test with. |
ive tried with this font and it still seems to be doing the same thing. |
That font isn't freely available either. It may be zero cost, but it requires a login to obtain. This is a known-issue though, if the chosen font doesn't have every single required character, the game prefers to use only the fallback font -- which may also not have every character, but by then it doesn't then 'fallback' to the chosen font. |
the confusion im having is why it goes to fallback cus it dosnt say in the logs that there are any missing characters, i made a python script to check the whole langfile and it found nothing that didnt match if i try a language setting that the font dosnt have all the characters it does say an error about it when i start the game, but using english it says nothing but still uses a fallback anyway |
Most languages stick with the 3-letter latin currency codes in the name string, however some translations are... clever... and use the currency symbol instead. Whilst this may look nice, it can cause issues with fonts as some scripts have a specific limited set of fonts which do not include these symbols. Instead, hard code the currency code list and add it when drawing the currency name.
Most languages stick with the 3-letter latin currency codes in the name string, however some translations are... clever... and use the currency symbol instead. Whilst this may look nice, it can cause issues with fonts as some scripts have a specific limited set of fonts which do not include these symbols. Instead, hard code the currency code list and add it when drawing the currency name.
Most languages stick with the 3-letter latin currency codes in the name string, however some translations are... clever... and use the currency symbol instead. Whilst this may look nice, it can cause issues with fonts as some scripts have a specific limited set of fonts which do not include these symbols. Instead, hard code the currency code list and add it when drawing the currency name.
Most languages stick with the 3-letter latin currency codes in the name string, however some translations are... clever... and use the currency symbol instead. Whilst this may look nice, it can cause issues with fonts as some scripts have a specific limited set of fonts which do not include these symbols. Instead, hard code the currency code list and add it when drawing the currency name.
Most languages stick with the 3-letter latin currency codes in the name string, however some translations are... clever... and use the currency symbol instead. Whilst this may look nice, it can cause issues with fonts as some scripts have a specific limited set of fonts which do not include these symbols. Instead, hard code the currency code list and add it when drawing the currency name.
Most languages stick with the 3-letter latin currency codes in the name string, however some translations are... clever... and use the currency symbol instead. Whilst this may look nice, it can cause issues with fonts as some scripts have a specific limited set of fonts which do not include these symbols. Instead, hard code the currency code list and add it when drawing the currency name.
Most languages stick with the 3-letter latin currency codes in the name string, however some translations are... clever... and use the currency symbol instead. Whilst this may look nice, it can cause issues with fonts as some scripts have a specific limited set of fonts which do not include these symbols. Instead, hard code the currency code list and add it when drawing the currency name.
Version of OpenTTD
1.13.3, windows 10
Expected result
the font to work
Actual result
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:
when using A-OTF Shin Go Pr6N and trying to read readme with japanese text (likely just the fallback font not supporting the characters):
0x3072 is ひ
Steps to reproduce
use A-OTF Shin Go Pr6N or seemingly any other type of shin go font, or probably other fonts too
The text was updated successfully, but these errors were encountered: