Created attachment 476067 [details] fc-match -v "Times New Roman" Description of problem: Archaic "Berling Antiqua" has an alternative name field of "Times New Roman". I guess here that there's arguably no bug seeing as the font *does* name itself Times New Roman in one of its name fields, but it is a real nuisance as it gets preferred above e.g. Liberation Serif if you have the misfortune to install it How reproducible: 100% Actual results: fc-match "Times New Roman" berling.ttf: "Times New Roman" "Normal" Expected results: Ideally we could somehow blacklist/scrub the "Times New Roman" name from "Berling Antiqua"
I see the upstream bug has been closed as "resolved fixed". Does that mean that this bug can be closed wontfix? 1. This clearly isn't a bug in fontconfig. 2. Wherever the original archaic "Berling Antiqua" came from, the reporter could update this buggy font from the (presumably) newer one that ships with Microsoft Reader version 2.1.1, freely downloadable from Microsoft. For reference, this product ships version 1.10 of the Berling Antiqua family, with sha1sums: bcd01a33bf2786142661df99178f8bfc2fa21674 berlingb.ttf f8a4347e2d085813cb7775bc47ceb89346669157 berlingi.ttf 70728414597a7e97d33e48ae487753db8999adba berling.ttf 367460e710ebd2bcda129daa8ab3e92f55a9e1d7 berlingz.ttf None of these fonts have a name record of "Times New Roman".
I agree. it's not a bug in fontconfig but a font bug. though a workaround could be added to it, there are no reason to keep using old one since the fix is available.
1d46f4484fa3db03583d369d1028bb7784783925 berling.ttf For reference, sha1sum of the offending version, probably very old, and we've hacked around it in LibreOffice itself.