[Libreoffice-bugs] [Bug 124591] Noto fonts don't display correctly in Microsoft (sorry, yes) Office 2016, please update to at least 2.001
bugzilla-daemon at bugs.documentfoundation.org
bugzilla-daemon at bugs.documentfoundation.org
Tue Apr 9 06:25:01 UTC 2019
https://bugs.documentfoundation.org/show_bug.cgi?id=124591
V Stuart Foote <vstuart.foote at utsa.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |khaledhosny at eglug.org,
| |vstuart.foote at utsa.edu
Blocks| |71732
--- Comment #2 from V Stuart Foote <vstuart.foote at utsa.edu> ---
I verify the missing code page details, opening the v2.000.GOOG build Noto
fonts with FontCreator, but can not confirm the impact of the missing Code Page
Character Ranges--at least in an en-US locale.
On a system with the Noto v2.00 build fonts installed with LibreOffice 6.2, LO
generated ODF, OOXML and at least DOCX are rendered in MS Word 2016 with no
loss of font fidelity. The Noto Sans and Noto Serif Regular fonts are parsed
and read by MS Word.
On same system with an ODF exported to PDF (font subset) the PDF renders using
the Noto fonts as composed.
So on the originating system this appears pretty benign. Of course it could be
more severe reopening on a different system, or for locale using other scripts.
But, probably best to move to more current Noto sources that have been patched
when available as this seems legitimate for some locales.
@Khaled?
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=71732
[Bug 71732] [META] Bugs related to text rendering, typography and font features
in LO
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20190409/82557a3a/attachment-0001.html>
More information about the Libreoffice-bugs
mailing list