There are MSOffice documents that refer to "TmsRmn" and "Helv" fonts, and fontconfig doesn't suggest suitable replacements. https://support.microsoft.com/en-us/kb/82860 "TmsRmn and Helv ... We still have the exact same fonts, but now under the names MS Sans Serif and MS Serif" https://support.microsoft.com/en-us/kb/68536 "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 ?
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.
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: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
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.
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug could not be fixed.