Bug 1260061 - fallbacks for TmsRmn and Helv
Summary: fallbacks for TmsRmn and Helv
Alias: None
Product: Fedora
Classification: Fedora
Component: fontconfig
Version: 24
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2015-09-04 10:44 UTC by Caolan McNamara
Modified: 2017-09-02 17:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2017-08-08 12:12:42 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Document Foundation 91004 0 None None None Never

Description Caolan McNamara 2015-09-04 10:44:21 UTC
There are MSOffice documents that refer to "TmsRmn" and "Helv" fonts, and fontconfig doesn't suggest suitable replacements.


"TmsRmn and Helv ... We still have the exact same fonts, but now under the names MS Sans Serif and MS Serif"


"Font Family     Bitstream    Canon    Adobe        HP
-----------     ---------    -----    -----        --

Swiss (Helv)    Swiss        Swiss    Helvetica    Universe
Roman (Tms Rmn) Dutch        Dutch    Times Roman  CG Times"

So "Helv" == "MS Serif" and both could be added as part of the Helvetica group of mappings I guess and "Tms Rmn" == "MS Sans Serif" and both are presumably then suitable for mapping to the "Nimbus Roman No9 L"/"Times New Roman" targets ?

Comment 1 Nicolas Mailhot 2015-09-04 12:31:48 UTC
I think you have it backwards :)

Anyway more than new aliases this group of fonts really need a modern implementation in Fedora (trying to use them on modern i18n text is an exercise in frustration, most non-us users will prefer broken aliasing to non-metric-compatible fonts rather than aliasing to implementations missing half the needed symbols). Someone probably needs to revisit packaging TEX Gyre if they finally fixed licensing warts.

Comment 2 Jan Kurik 2016-02-24 13:43:14 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:

Comment 3 Fedora End Of Life 2017-07-25 19:14:46 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora  'version'
of '24'.

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.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 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 this bug is closed as described in the policy above.

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 Fedora End Of Life 2017-08-08 12:12:42 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 5 ompragash 2017-09-02 17:05:20 UTC
This bug could not be fixed.

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