Closed toebes closed 8 months ago
I'll look into it! What version of the font (check glyph U+E843 perhaps ) and what text environment are you working in?
Running in Chrome on Windows 11 (rendered from a web page). Problem also shows up in Word.
This looks like one of those weird situations where it's hard to know what the problem is and thus how to fix it. I can and can't reproduce it, depending on what application I'm using (MacOS only though).
Safari browser is quite happy, as long as the CSS line height is sufficient:
But Firefox browser refuses point blank:
In a Terminal, it also looks OK:
although some other terminals are unhappy (eg Kitty):
Some text editors are quite happy (eg CotEditor):
Others try their best but don't really get it right (eg BBEdit):
I speculate that, because the "j" + "mark" is pushing the limits of the bottom of the font, some applications will just say "No", particularly if the current line height tells them to. (Some applications let lines overlap, others don't.)
Also I discovered that the "j" character is not considered by font building apps to have any mark attachments at all, so the "j" in JuliaMono doesn't by default have a bottom mark anchor (although it's easy to add). It's therefore possible that some applications don't bother to do marks on "j" glyphs. I don't know for sure - seems odd that they would check, to be honest.
Adding a bottom anchor is easy (can be in the next release) but might not always change the geometry problem or persuade applications to show what they don't want to. JuliaMono has long descenders, and it's not easy to change them.
So, short of increasing the available line height to give some encouragement to applications that need it, I can't see a quick solution.
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!
For now, my code just makes sure not to pick those specific descenders when using the letter j. I'm happy to try anything else if you get any insights!
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.