Tamil Fonts not displaying correctly, overlapping with other characters

[sharand]

🗹 Requirements

• [x] I have searched the issues for my issue and found nothing related and/or helpful
• [x] I have searched the FAQ for help
• [x] I have searched the Wiki for help

🎯 Subject of the issue

Tamil Fonts not displaying correctly, overlapping with other characters

🔧 Your Setup

• Which font are you using (e.g. Anonymice Powerline Nerd Font Complete.ttf)? -Font Used: MesloLGS NF
• Which terminal emulator are you using (e.g. iterm2, urxvt, gnome, konsole)? -iterm2
• Are you using OS X, Linux or Windows? And which specific version or distribution? -OS X

★ Screenshots (Optional)

Tested Tamil Text: அகர முதல எழுத்தெல்லாம்; ஆதி பகவன் முதற்றே உலகு.

[Finii]

Thanks for the good issue report (useful data given and glyphs to copy and paste for experiments) :+1:

The first letter in your example is this I assume:

Which is empty in the patched Meslo as well as our source:

The only font I have installed that contains that letter:

has it with no negative bearings (overlap into next character). Despite of that my terminal (tilix) renders the fallback font like in your iterm, with overlap.

In (Libre Office) writer on the other and it renderes with the correct width (no blanks typed in here):

So this issue has nothing to do with the patched font but with your terminal and how it handles font fallback. Sorry there is nothing we can do about it (except adding tamil letters to the patch set ;).

Addendum:

When I use FreeSerif in my terminal, it ... 'works' but the advance width in the monospaced terminal is then adjusted to fit the widest glyph which looks kind of ugly for roman letters:

The only terminal that I am aware of that handles double width characters in some way is the (new?) MS Windows Terminal.

Maybe other people have more ideas, especially with OS-X my knowledge is very limited. So I leave this open for a while, albeit I deem this closed.

Edit: Correct half-eaten-fruit's OS name

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a new issue, complete the issue template with all the details necessary to reproduce, and mention this issue as reference.