Bug 187855 - Ligatures displayed incorrectly in Firefox
Summary: Ligatures displayed incorrectly in Firefox
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Christopher Aillon
QA Contact:
URL: http://www.gnome.org/~jamesh/firefox-...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-03 23:39 UTC by petrosyan
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-09-05 03:48:03 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
screenshot illustration (57.93 KB, image/png)
2006-04-03 23:39 UTC, petrosyan 		no flags Details
bug illustration (1.42 KB, text/html)
2006-07-07 02:43 UTC, petrosyan 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 331716 0 None None None Never

Description petrosyan 2006-04-03 23:39:53 UTC 
Description of problem:
Firefox doesn't display the ligatures correctly. Need to have a font that
supports ligatures such as DejaVu for example. For a demo look at:
http://www.gnome.org/~jamesh/firefox-ligature.html

Version-Release number of selected component (if applicable):
firefox-1.5.0.1-9

How reproducible:
Always

Steps to Reproduce:
1. Install DejaVu fonts (or any other font with ligatures)
2. Go to: http://www.gnome.org/~jamesh/firefox-ligature.html in Firefox

Additional info:
Look at the screenshot.
Comment 1 petrosyan 2006-04-03 23:39:53 UTC 
Created attachment 127264 [details]
screenshot illustration
Comment 2 petrosyan 2006-07-07 02:43:28 UTC 
Created attachment 132037 [details]
bug illustration

This bug has been fixed for Latin alphabet but it still happens for Armenian
alphabet. Attaching a sample HTML file demonstrating the bug for DejaVu Sans
justified case.
Comment 3 petrosyan 2006-09-05 03:48:03 UTC 
It is better to track this bug upstream at
https://bugzilla.mozilla.org/show_bug.cgi?id=331716
Note You need to log in before you can comment on or make changes to this bug.