-
Notifications
You must be signed in to change notification settings - Fork 557
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
Some Korean glyphs are not rendered correctly. #512
Comments
I've just modified the font with fontforge to include those two characters (copied them from |
IBM Plex Sans KR does not support the unicode range Hangul Jamo It appears that in some situations this normalisation is not applied correctly in your environment. |
Hi, thank you for your reply. |
I've managed to come up with a hack, by adding this to my <?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "urn:fontconfig:fonts.dtd">
<fontconfig>
<alias>
<family>sans-serif</family>
<prefer>
<family>IBM Plex Sans</family>
<family>IBM Plex Sans KR</family>
<family>Source Han Sans</family>
</prefer>
</alias>
</fontconfig> This will use It would be great if |
I am using IBM Plex on Linux and sometimes Hangul syllables are not rendered correctly.
For instance, the syllable
아
(\uC544
HANGUL SYLLABLE A) is sometimes rendered as:아
(\u110B
HANGUL CHOSEONG IEUNG,\u1161
HANGUL JUNGSEONG A), that is, the individual parts separated:It doesn't happen when I type those characters (that always works).
But sometimes, people send me files with those weird characters.
I wonder why this is happening. Is it because IBM Plex KR does not support the range
U+1100
toU+302F
?If I install Source Han Sans, which supports that range, I can render those characters.
Moreover, if I set my main font to “IBM Plex Sans KR” it works, but then it doesn't render any accented characters, and the metrics are a bit off.
How can I proceed? Maybe there's some magic fontconfig configuration I have to set up?
Are there any plans to support that Unicode range?
The text was updated successfully, but these errors were encountered: