Bug 14021

Summary: Some glyphs should not be marked as ligatures
Product: DejaVu Reporter: Kiyoshi Aman <kiyoshi.aman>
Component: Mono SansAssignee: Deja Vu bugs <dejavu-bugs>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: medium CC: bl.bugs, moyogo
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Kiyoshi Aman 2008-01-11 05:32:57 UTC
Some glyphs [fi and fl, particularly] should not be ligated in a fixed-width font; they don't offer any readability enhancements and, in fact, hinder usage by the visually impaired.
Comment 1 Ben Laenen 2008-01-11 05:38:09 UTC
What version are you using? We removed the ligature rules a long time ago, now they're only discretionary.
Comment 2 Kiyoshi Aman 2008-01-12 04:24:55 UTC
Ubutu Gutsy has 2.19 and not any later versions.
Comment 3 Ben Laenen 2008-01-12 04:36:05 UTC
I've just checked our 2.19 version, there is no "liga" (ligature) rule defined for the "fi" and "fl" ligatures, only "dlig" (discretionary ligature). Only liga is applied by default, not dlig (except when you managed to patch Qt or Pango in such a way that it does, of course). Can you post a screenshot?
Comment 4 Kiyoshi Aman 2008-01-13 04:37:44 UTC
Sure: http://www.aerdan.org/gallery/dvsm.png
Comment 5 Ben Laenen 2008-01-13 05:52:45 UTC
Really, I have no idea how you get that ligature. Is that a normal Gnome application (I don't recognize it). Do you get the ligatures as well in Gedit? In FireFox? Could you manually install the latest DejaVu Mono (don't install Sans from 2.22, it's buggy) and check if you still get ligatures?
Comment 6 Kiyoshi Aman 2008-01-13 15:49:54 UTC
Yes, I get the ligatures in Gedit and Firefox. I'll install the latest DVSM and see if that helps any, yes.
Comment 7 Kiyoshi Aman 2008-01-13 16:07:39 UTC
It seems to be working fine if I manually install DVSM into my ~/.fonts, even though the system-installed version that ships with Hardy [updated to Hardy last night] exhibits the issue I was reporting.

I'm thinking I should take this up with Ubuntu now; do you agree?
Comment 8 Denis Jacquerye 2008-01-13 16:25:49 UTC
(In reply to comment #7)
> It seems to be working fine if I manually install DVSM into my ~/.fonts, even
> though the system-installed version that ships with Hardy [updated to Hardy
> last night] exhibits the issue I was reporting.
> 
> I'm thinking I should take this up with Ubuntu now; do you agree?
> 

I'm using an up to date Ubuntu Hardy but I cannot reproduced the bug. ttf-dejavu 2.22 is currently on Hardy.
What do you get with the following command?
fc-list "DejaVu Sans Mono:style=Book" file
Comment 9 Kiyoshi Aman 2008-01-13 17:13:20 UTC
I get the following:

aphrael@kitsune:~$ fc-list "DejaVu Sans Mono:style=Book" file
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono.ttf:
/home/aphrael/.fonts/DejaVuSansMono.ttf:
Comment 10 Denis Jacquerye 2008-04-16 23:34:06 UTC
(In reply to comment #9)
> I get the following:
> 
> aphrael@kitsune:~$ fc-list "DejaVu Sans Mono:style=Book" file
> /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono.ttf:
> /home/aphrael/.fonts/DejaVuSansMono.ttf:

Where does /home/aphrael/.fonts/DejaVuSansMono.ttf come from?
Comment 11 Kiyoshi Aman 2008-04-17 00:39:29 UTC
/home/aphrael/.fonts/DejaVuSansMono.ttf is from your (DejaVu's) packaging of 2.22.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.