The Noto fonts in version 2.000 that are currently installed with LibO Version 6.2.x do not display correctly in Microsoft Office 2016. They are substituted with other fonts there. This is not strictly a LibO problem, but I am probably not the only (home) user of LibO who also has Microsoft Office in parallel (for job related reasons). Updating the Noto fonts to version 2.001 in LibO would fix this, see here:
So it's not a Microsoft problem but a bug in the Noto fonts distributed with LibO.
Steps to Reproduce:
1. Install Libreoffice (from version 6.x with Noto fonts)
2. Write document with Noto font (Noto Serif, Noto Sans)
3. Open document in Microsoft Office 2016.
Noto fonts are substituted with other fonts in Microsoft Office.
User Profile Reset: No
Use the latest version of Noto fonts (2.001) to avoid this problem.
Thanks for your bug report.
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.
That is a known bug in certain versions of Noto fonts that lacked code pages bits in the OS/2, which makes them not work on certain Windows applications that use the code pages to determine what character ranges the font supports before using fallback fonts (not only MS Office, but I believe other applications using RichEdit component as well).
I think we should upgrade our version since technically the version we have is broken on Windows even though LibreOffice itself is unaffected.
What are the prospects of having this fixed? It is apparently not a priority for LibO developers, but I suppose updating the Noto fonts to version 2.001 would not be very difficult.