Bug 956453 - Incorrect font aliases for TimesNewRomanPS and TimesNRMT
Summary: Incorrect font aliases for TimesNewRomanPS and TimesNRMT
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: fontconfig
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-25 02:35 UTC by Elliott Sales de Andrade
Modified: 2015-08-13 10:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Elliott Sales de Andrade 2013-04-25 02:35:10 UTC
Description of problem:
As an example, please see this PDF:
http://www.ualberta.ca/~ygu/publications/christian_gji.pdf

It uses several serif fonts that are not embedded:
TimesNewRomanPS
TimesNewRomanPS-Italic
TimesNewRomanPS-Bold
TimesNewRomanPS-BoldItalic
TimesNRMT-SemiBold

When I view it in Firefox's pdf.js, the title and headings are serif, but when I view it in evince, the title and headings are sans-serif. I know pdf.js is not a perfect renderer, but at least it picks the right font.

I filed this report under fontconfig because it is returning the wrong font:

$ fc-match TimesNewRomanPS
DejaVuSans.ttf: "DejaVu Sans" "Book"

$ fc-match TimesNewRomanPS-Italic
DejaVuSans.ttf: "DejaVu Sans" "Book"

$ fc-match TimesNewRomanPS-Bold
DejaVuSans.ttf: "DejaVu Sans" "Book"

$ fc-match TimesNewRomanPS-BoldItalic
DejaVuSans.ttf: "DejaVu Sans" "Book"

$ fc-match TimesNRMT-SemiBold
DejaVuSans.ttf: "DejaVu Sans" "Book"

Using similar fonts nets the correct result:

$ fc-match TimesNewRoman
LiberationSerif-Regular.ttf: "Liberation Serif" "Regular"

$ fc-match Times
n021003l.pfb: "Nimbus Roman No9 L" "Regular"

I am not sure of the difference here, but at least the results are serif.

Version-Release number of selected component (if applicable):
fontconfig-2.10.2-2.fc18.x86_64

Steps to Reproduce:
1. Download above PDF.
2. Open in Firefox's pdf.js
3. Open in evince

Actual results:
Differing fonts for title and headings.

Expected results:
Same fonts for title and headings.

Comment 1 Akira TAGOH 2013-04-25 10:53:45 UTC
Where is that font coming from? why the later case works is we have an alias to recognize that Times New Roman is a serif. you need to have similar things for your fonts.

Comment 2 Elliott Sales de Andrade 2013-04-25 20:39:14 UTC
The font comes from the referenced PDF. While I linked to the author's site, the same thing occurs with the PDF from the journal, so apparently the journal is using those fonts at some point. I have no control over this.

Comment 3 Fedora End Of Life 2013-12-21 13:13:43 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Nicolas Mailhot 2014-01-14 09:23:11 UTC
liberation* and other packages metric-compatible with times new roman probably need to alias those names too in their fontconfig rules


Note You need to log in before you can comment on or make changes to this bug.