Bug 525498

Summary: wrongly encoded glyphs after U+10000
Product: [Fedora] Fedora Reporter: Denis Jacquerye <moyogo>
Component: liberation-fontsAssignee: Caius Chance <K9>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: dwmw2, fonts-bugs, i18n-bugs, K9, petersen
Target Milestone: ---Keywords: i18n
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-10-19 01:49:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
path reajusting encodings none

Description Denis Jacquerye 2009-09-24 15:23:45 UTC 
Since 1.04 the codepoints U+10000...U+10013 in Liberation Sans, U+10000...U+1000B in Liberation Serif, and U+10000...U+1000E in Liberation Mono, are filled with characters that used to be out of bound. The glyph don't actually match the codepoints.
For example U+10005 LINEAR B SYLLABLE B001 DA is a fraction four in LiberationSans-Regular.

The error was probably introduced when the font encoding went from Unicode BMP to Unicode Full.
Comment 1 Caius Chance 2009-09-25 01:40:31 UTC 
Would you have any suggestions on the conversion? I have done my best to preserve that but seems at your feedback it was failed.
Comment 2 Denis Jacquerye 2009-09-30 08:28:18 UTC 
Created attachment 363148 [details]
path reajusting encodings

The patch does several things:
- clears duplicates of .notdef, .null and nonmarkingreturn
- renames the out-of-bound glyphs to previous names
- adjusts glyph id and references.
Comment 3 Caius Chance 2009-10-01 01:31:53 UTC 
Thanks Denis.

Is this patch a proper fix which maintain closer quality with the original TTF delivered from Ascender?
Comment 4 Denis Jacquerye 2009-10-06 11:11:06 UTC 
(In reply to comment #3)
> Is this patch a proper fix which maintain closer quality with the original TTF
> delivered from Ascender?  

No, the tables DSIG, hdmx, LTSH and VDMX from the original TTF are not there.

Fontforge can generate a DSIG.
hdmx, LTSH and VDMX are ignored by Fontforge ; they would have to be included in the generated fonts in post-processing.
Comment 5 Denis Jacquerye 2009-10-06 11:16:11 UTC 
As far as I know, no hinting has gone missing and the kern table is the same as in the original font.
Comment 6 Jens Petersen 2009-10-08 02:55:32 UTC 
Denis how did you generate the patch btw? :)
Comment 7 Caius Chance 2009-10-19 01:49:23 UTC 
patch is applied on rawhide