https://bugs.documentfoundation.org/show_bug.cgi?id=114855
V Stuart Foote <vstuart.foote@utsa.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needsUXEval |
Status|NEW |RESOLVED
CC|libreoffice-ux-advise@lists |khaledhosny@eglug.org,
|.freedesktop.org |michael.meeks@collabora.com
| |, quikee@gmail.com,
| |vstuart.foote@utsa.edu
Resolution|--- |DUPLICATE
--- Comment #2 from V Stuart Foote <vstuart.foote@utsa.edu> ---
There is no internal UI for working with OpenType 1.8 OTF Variable fonts. Work
flows would need to be altered as would printing and export.
Why would we change over to Source Sans Variable now? Absent correct handling
of the variable font--we would get an arbitrary and likely unusable rendering
of the font--or more likely a fall-back to another on system font. We'd just be
wasting space in the deployment package.
Until such time as support for OTF 1.8.2 "fvar" (bug 103596) is implemented
substituting this or any other variable font makes no sense.
Duping this to bug 103596, as only when that enhancement is undertaken would it
make sense to adopt any variable font.
*** This bug has been marked as a duplicate of bug 103506 ***
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 114855] Replacing Source Sans Pro by Source Sans Variable · bugzilla-daemon
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.