a letter with diacritics + combining macron below/low line (U+0331/U+0332) wrongly rendered

[Mariusz-W]

In Windows 11 accented letters with high diacritics (e.g., á, ê, ü, …), when followed by combining macron below or combining low line place the macron or the low line under the glyph and under the diacritic, or just under the diacritic, not under the glyph. The result in either case looks ugly and often ureadable.

The affected applications:

1. Windows terminal
2. Gvim
3. mintty

and, probably, several others.

The letters with diacritics are entered as SINGLE Unicode codepoints, not as letters with combining diacritics.

System: wholly updated Windows 11 with JuliaMono shipped with Windows (Version 0.060)

The same applications display accented letter with combining low diacritics correctly when I use Cascadia Mono , Consolas , Courier New , JetBrains Mono .

[cormullion]

Thanks. I don't know why it does that, but when I do I'll fix it!

[cormullion]

out of interest- what language are these characters appearing in?

[Mariusz-W]

Latin accented characters with diacritics appear in all European languages that use Latin alphabet with a single exception of English. Characters with horizontal bars below the glyph are essential for :

1. working with archival documents
2. Natural Sciences (especially in Mathematics, Physics, Engineering,…)
3. Philology

I work in each of the above mentioned fields and I am relying in my daily work on monospaced fonts. Of all the currently available monospaced fonts, JuliaMono has an advantage of providing a greater coverage of Unicode symbol blocks than most of the competition. That is essential for people doing lots of work in the areas I mentioned.

The reported bug should be easy to fix: apparently, the dimensions of the glyph box are wrongly set if the glyph was created by adding an accent to another glyph. I will appreciate very much your fixing this bug and your continuing adding additional Unicode symbols to JuliaMono.

[cormullion]

@Mariusz-W I made some small changes to see if I could fix this. I've uploaded them here to master branch, as part of ongoing v0.061 development, although not yet released. I'd be interested to know if this fixes the issue or introduces any new problems.

[Mariusz-W]

Thank you. I just made a number of initial tests and the result looks great.

I noticed that your implementation of the combining macron below and combining low line allows iteration: the subsequent application of the combining macron below or combining low line places the corresponding bars at even distances below the last one. If so, then I may add to my initial request also Latin alphabet letters with LOW diacritics. At the moment JuliaMono treats well ç in French, but mishandles Polish and Lithuanian ‘ogonek’ letters in the Latin Extended-A Unicode block.

[cormullion]

then I may add to my initial request also Latin alphabet letters with LOW diacritics. At the moment JuliaMono treats well ç in French, but mishandles Polish and Lithuanian ‘ogonek’ letters in the Latin Extended-A Unicode block.

Best to open a separate issue for each bug. Visual examples of problems are useful too.

[Mariusz-W]

There seems to be a single issue here: some Latin glyphs with added diacritics report incorrectly their box dimensions. For example, the glyphs for ą , ę and other vowels with ‘ogonek’ accent, don’t take into account the ‘ogonek’ .

There is a larger issue here regarding the essential difference between how ‘combining macron below’ and ‘combining low line’ function:

1. ‘Combining macron below’ is used to differentiate (not to emphasize) a single glyph from the same glyph unmarked by the macron below. Such use is an everyday experience in Mathematical Sciences (including Physics and Engineering).

2. ‘Combining line below’ is used to emphasize (not to differentiate) a string of glyphs. The implementation of ‘combining line below’ must therefore produce the effect of placing a continuous line under the emphasized string. Such use has been common since the early days of hand writing.

I can open a separate ticket about it.