[Issue 79878] OO.o can not select modern font faces conveniently

[nmailhot at openoffice.org]

To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=79878





------- Additional comments from nmailhot at openoffice.org Tue Aug 17 05:04:42 +0000 2010 -------
TEX fonts are a world in themselves and should not be taken as example of "good"
fonts. TEX usually selects fonts by filename (in TEX macros) when other apps
select fonts by the font name and font face exported in font metadata. As a
result the font name and face exported by TEX fonts are too often a mess that
does not conform to existing font standards (since TEX itself does not use them,
except for very modern TEX engine which have low penetration so far).

The Latin Modern example you give is typical: your table references the filename
(which should be irrelevant, and besides is a human-unfriendly abbreviation that
only makes sense for people that type it instead of selecting it in gui lists),
and the faces listed do not conform to WWS
(http://blogs.msdn.com/text/attachment/2249036.ashx). Standard CSS operators
like bold-er can not work with a face such as "dunhill". (and I've seen much
worse while auditing texlive 2007, for example standard face composants such as
italic split between font family name and font family variant, which had clearly
been generated through a stupid format convertor without ever checking the
result outside of TEX)

While it would be good to accommodate TEX fonts, the priority should be to
accommodate fonts that conform to specs written to help typical GUI apps. If the
TEX world wants its fonts to be used outside of TEX, it has lots of cleaning up
to do.



---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification