https://bugs.documentfoundation.org/show_bug.cgi?id=105298

--- Comment #22 from LibreTraining <libretraining.tutori...@gmail.com> ---
(In reply to Thomas Linard from comment #21)

> 
> Btw, please read some background information about nameIDs in font tables,
> like :
> https://glyphsapp.com/tutorials/naming
> 
> The "bugs" you found around nameID 2 are common tricks, thousands of fonts
> use them. If LibreOffice doesn't handle correctly such fonts, LibreOffice
> has a bug (not the fonts!).

I am familiar with the "tricks" used in font files to support older
applications.
FontLab VI has similar documentation and font naming tools.

These were simply errors.
The errors caused an image editor and various font managers to display the
wrong font rather than the one selected.
I fixed the fonts, finished the project which needed that font, 
and forgot about it until I saw this bug report.

Since I fixed and used Avenir LT Std, I have acquired Avenir Next LT Pro.
This updated version of the font family does not have these issues.
In fact the font meta data looks much like my fixed files in the Std version.

-----

OK. 
I will post some other issues in the other "font family" bug reports.
I think it would help to have you testing on the Mac 
the same fonts I am testing on Windows.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to