-
Notifications
You must be signed in to change notification settings - Fork 29
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
Combining characters with lower case j doesn't always render the combining character for some glyphs. #199
Comments
I'll look into it! What version of the font (check glyph U+E843 perhaps ) and what text environment are you working in? |
I've done some more playing and interestingly enough, on the Mac with Chrome the j renders correctly. I've tried tweaking line height on Windows, but it doesn't seem to have an impact. However, I did observe something. It isn't that the annotation isn't there, but the annotation is shifted off to the right. Here's an example that it is obvious with: M̳j̳y̳y̳j̳ And another: M̲jy̲yj̲ |
It's all quite frustrating for font makers and font users... I hope you can find a solution - perhaps another font - that works more reliably for you! |
But your font is excellent! |
This issue has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
I really like the font! Great job there. However, I'm finding that some of the combining characters don't appear to work with the lower case letter j.
In this case I am using it as a webfont for the Codebusters website when generating a Baconian cipher. However, for some of the combining glyphs, it simply doesn't render for the letter j only with the JuliaMono font. I've pasted the list below and included a screen snapshot to show how it renders both with JuliaMono and with Courier New. I considered that it might be related to descenders and included the letter y to show that it is specific to the letter j. Unfortunately I can't make the bug report here use the font and github's mono font does appear to render it correctly.
The text was updated successfully, but these errors were encountered: