Bug 25409 - Newly installed fonts are not all available in some applications
Summary: Newly installed fonts are not all available in some applications
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
: 25700 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-09-05 19:30 CEST by Sébastien Morin
Modified: 2021-09-07 14:09 CEST (History)
2 users (show)

See Also:
Source RPM: drakfont
CVE:
Status comment:


Attachments

Description Sébastien Morin 2019-09-05 19:30:46 CEST
Description of problem:

On a freshly installed Mageia 7.1, installing new fonts leads to inconsistent results : one font can be usable in certain software but not with others.

How reproducible: at least three times already ;)

Steps to Reproduce:
1. Install Mageia 7.1 and run the available updates ;)
2. Download Tintin's fonts from http://www.tintin.free.fr/tintinophilie/telechargement/ for example. (Use the direct link http://www.tintin.free.fr/tintinophilie/telechargement/policestintin.zip if you can't find your way around on that french-speaking website ;)
3. Install the two TTF fonts from the MCC (System >> Manage fonts >> Import)
4. Both fonts (“tintin” and “TinTin Majuscules” should be available from drakfont)
5. Both fonts can also be seen from Plasma's “System Configuration”
6. Open LibreOffice Writer and try to select one of these newly installed fonts, and see that only “Tintin Majuscules” is available inside LO
7. Open The Gimp and try to use one of the Tintin fonts, and see that any of them can be selected and used.

It seems this problem also affects users trying to install Microsoft fonts.
Comment 1 Lewis Smith 2019-09-05 21:40:24 CEST
Assigning to tv as one of the MMC-Fonts authors, and drakconf maintainer.
I could not find a duplicate bug.

Assignee: bugsquad => thierry.vignaud

Lewis Smith 2019-11-15 20:51:10 CET

Summary: Installing new fonts via drakxtools gives inconsistent results => Newly installed fonts are not all available in some applications

Comment 2 Lewis Smith 2019-11-15 20:53:59 CET
*** Bug 25700 has been marked as a duplicate of this bug. ***

CC: (none) => thomas.bigot

Comment 3 Thomas Bigot 2019-11-18 11:42:48 CET
It’s not only about installing new fonts with MCC-fonts, even some RPMs installed during a fresh install contain fonts (for instance URW Palladio) which are not available in some software (Inkscape, LibreOffice).
Comment 4 Sébastien Morin 2019-11-18 13:21:04 CET
(In reply to Thomas Bigot from comment #3)
> It’s not only about installing new fonts with MCC-fonts, even some RPMs
> installed during a fresh install contain fonts (for instance URW Palladio)
> which are not available in some software (Inkscape, LibreOffice).

I am not sure that URW-Palladio was supposed to be used by any software in the first place: I think this font is to be used in LaTeX documents and is made of .vf .pbf and .tmf files.

On the contrary, LO or Inkscape need .otf or .ttf files, AFAIK.

The bug I reported concerns “simple” TTF files which are expected to be usable system-wide; are you sure URW-Palladio comes in the same category?
Comment 5 Thomas Bigot 2019-11-19 16:12:26 CET
Not sure it’s the same bug, but I am sure these fonts were previously available in LibreOffice and Inkscape.

I made a logo using Inkscape using my previous Mageia, with URW Palladio, and now, I cannot work on my logo because of missing fonts when I reopen it with an up-to-date Cauldron.
Comment 6 Thierry Vignaud 2019-11-20 23:17:37 CET
In Inkscape case, it uses pango which recently has switched to harfbuzz and in the process loose the ability to load some old bitmap font formats
See https://gitlab.gnome.org/GNOME/pango/issues/386
Though it's possible to convert some formats: https://gitlab.gnome.org/GNOME/pango/issues/386#note_567676
So that's a different issue than Sebastien's.

Note that your font seems to be available as TTF: https://www.myfonts.com/fonts/urw/palladio?tab=techSpecs
Some free variants seems to be in TTF as well: https://en.wikipedia.org/wiki/Palatino#Free_and_open-source_versions_and_derivatives

As for the original bug, that's strange as drakfont even run fc-cache.

I've only a Fedora machine where I currently am.
Interestingly, after unziping those fonts in /usr/share/fonts/tintin, LO only see "tintin majuscules" but not the other tintin fonts.
Whereas eg: gedit enables to select any of the tintin familly (using the gtk font selector)...

Despite:
$ fc-list |grep -i tintin
/usr/share/fonts/tintin/tintin_majuscule.ttf: Tintin Majuscules:style=Bold
/usr/share/fonts/tintin/tintin.ttf: tintin,瑩湴楮

I seem to recall having hitting that issue but I don't remember what I'd did at that time
Comment 7 Bernard SIAUD 2021-01-17 10:31:09 CET
On a freshly installed Mageia 8 beta2 installing new fonts leads to inconsistent results : one font can be usable in certain software but not with others.

[troumad@localhost ~]$ ll .fonts/FeroxAlternates.ttf
-rwxrwx--- 1 troumad troumad 112008 juil.  6  2020 .fonts/FeroxAlternates.ttf* 

But Lo and gimp don't see this fonts.

I have installed this fonts with mcc : nothing.

CC: (none) => liste

Comment 8 Aurelien Oudelet 2021-07-06 13:17:40 CEST
Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.
Comment 9 Marja Van Waes 2021-09-07 14:09:56 CEST
Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

Status: NEW => RESOLVED
Resolution: (none) => OLD


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