https://bugzilla.redhat.com/show_bug.cgi?id=1779123
Bug ID: 1779123
Summary: Pango no longer supports type1 fonts
Product: Fedora
Version: rawhide
Status: NEW
Component: pango
Assignee: p...@redhat.com
Reporter:
https://bugzilla.redhat.com/show_bug.cgi?id=1779123
Nicolas Mailhot changed:
What|Removed |Added
Doc Type|--- |If docs needed, set a value
--- Com
https://bugzilla.redhat.com/show_bug.cgi?id=1779123
--- Comment #2 from Michael J Gruber ---
(In reply to Nicolas Mailhot from comment #1)
> LibreOffice already dropped Type 1 support for the same reasons several
> years ago
>
> And it produced the same kind of user pushback.
>
> And in the e
https://bugzilla.redhat.com/show_bug.cgi?id=1753295
--- Comment #86 from Michael J Gruber ---
If you have any helpful information about the transition from type1 fonts
please comment in bug 1779123 .
--
You are receiving this mail because:
You are on the CC list for the bug.
_
https://bugzilla.redhat.com/show_bug.cgi?id=1779123
--- Comment #3 from Nicolas Mailhot ---
The transition from Type 1 already happened years ago while you were not
looking.
Thanks to TEX Gyre, and LibreOffice dropping Type1 support, and years of work
by many people, including myself, includi
https://bugzilla.redhat.com/show_bug.cgi?id=1779123
--- Comment #4 from Nicolas Mailhot ---
As for conversion to OpenType, CFF OpenType (OTF) was specifically designed to
allow Adobe converting its large store of Type1 fonts to OpenType without data
loss (the outline format within OTF is pretty
https://bugzilla.redhat.com/show_bug.cgi?id=1779123
--- Comment #5 from Nicolas Mailhot ---
See also:
https://docs.microsoft.com/en-us/typography/opentype/spec/namesmp
https://glyphsapp.com/tutorials/naming
--
You are receiving this mail because:
You are on the CC list for the bug.
_
https://bugzilla.redhat.com/show_bug.cgi?id=1779123
--- Comment #6 from Michael J Gruber ---
(In reply to Nicolas Mailhot from comment #3)
> The transition from Type 1 already happened years ago while you were not
> looking.
Keep issueing personal accusations and get flagged.
> Thanks to TEX
https://bugzilla.redhat.com/show_bug.cgi?id=1748495
--- Comment #27 from Peng Wu ---
(In reply to Nicolas Mailhot from comment #26)
> If that is intended to be the long-term solution, I can add it to packaging
> guidelines. But fonttosfnt need to end up in the distribution proper, not a
> copr
