https://bugzilla.redhat.com/show_bug.cgi?id=2547637
--- Comment #4 from Jocelyn Falempe <[email protected]> --- Yes, kmscon can't handle non monospace font. I don't know how gnome-terminal can do that, as the basic of a terminal is that all cells have the same pixel dimension. Normally even if the name "monospace" matches vazirmatn, kmscon explicitly asks for monospace font with: FcPatternAddInteger(ftfont->pattern, FC_SPACING, FC_CHARCELL); FcPatternAddInteger(ftfont->pattern, FC_SPACING, FC_MONO); FcPatternAddInteger(ftfont->pattern, FC_SPACING, FC_DUAL); https://github.com/kmscon/kmscon/blob/main/src/font/font_freetype.c#L179 Also using Vazirmatn font, it's obvious the latin characters are not monospace. the 'm' is much longer than the 'n' https://fonts.google.com/specimen/Vazirmatn So maybe gnome-terminal uses another font for latin char ? your screenshot shows that 'm' and 'n' are clearly different from the vazirmatn font. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2547637 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202547637%23c4 -- _______________________________________________ fonts-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
