Tk Source Code

View Ticket
Login
Ticket UUID: 0cad8f8802d52b69b6af88f7d1cabf4bc00ba2ec
Title: empty glyphs in a TTF font always rendered using system font
Type: Bug Version: 8.6.7
Submitter: jose1711 Created on: 2017-09-26 20:27:26
Subsystem: 46. Unix Fonts Assigned To: nobody
Priority: 5 Medium Severity: Minor
Status: Open Last Modified: 2017-09-27 20:39:19
Resolution: None Closed By: nobody
    Closed on:
Description:
Abeceda_v4 is a TTF font in which two glyphs are deliberately set as narrower spaces.
Instead of getting a space, these two glyphs are always rendered using a default font.
This issue seems to be Linux-specific (could not reproduce in Windows XP).

Font used for testing: https://freeshell.de/~jose1711/donotdelete/Abeceda_v4.ttf
Test case:
label .foo -text ŅņŅaaaŅnņxŅ -font {Abeceda_v4 200}
pack .foo

Expected result: visible text "aaa nx"
Actual result: ŅņŅaaaŅnņxŅ

Arch Linux, x86_64
User Comments: jose1711 added on 2017-09-27 20:39:19:
Please, can you specify which font editor did you use to display the font?
I am seeing blank characters (spaces) at the aforementioned unicode positions
when viewing in Fontforge.

bll added on 2017-09-26 21:34:02:
Using the Abeceda_v4 font, \u0145 and \u0146 render as Ņ and ņ in the character map program (Latin Extended-A) and also in the font-manager program.  This is not a Tk issue.