Description of problem: Using the Liberation fonts to replace MS core fonts in an OpenOffice text document leads to changes in layout--the fonts appear to have non-equivalent metrics. The same replacement using AbiWord shows perfect metric equivalence. Version-Release number of selected component (if applicable): The LiberationMono-Bold.ttf file is marked as version 1.0 How reproducible: always--depends on font display settings (hinting), see comments at OO.org Additional info: Originally reported to OO.org: http://www.openoffice.org/issues/show_bug.cgi?id=77698 Since the comments there suggest that there may be some issue with the font metrics and/or Freetype, it seemed reasonable to ask you folks take a look as well.
Checking with upstream.
Have we got any obvious test cases with various pages of text in e.g. msoffice under windows in the microsoft fonts and then the same text in the liberation fonts to verify that we get the same no of lines per page and characters per line with msoffice, just a smoke-test sanity testcase ?
I don't know of any, but it would certainly be a good thing to have. Joe, do you have some document you can attach here which demonstrates the problem?
I attached a simple test document to the OO.org issue linked above. I also repeated some tests with that document, and reported what I found there as well. Bottom line: only OO.org builds (on F7) are showing any difference, and only for Times New Roman vs. Lib Serif (roman, italic and bold faces; bold+italic is ok). Also, the difference comes from TNR being rendered narrower; the Lib Serif samples are rendered with the same widths in both OO.org and Fedora builds as well as in AbiWord. So, all the samples have the same width using the Fedora OOo build, and for the OO.org build, it looks like the Liberation fonts are not the source of the problem. Thanks for having a look--I think this can probably be closed.
Hi jensp, would it be viable to use Fedora OOo build by default? Or it had been using already?
> OO.org build, it looks like the Liberation fonts are not the source of the problem. > Thanks for having a look--I think this can probably be closed. Welcome. Closing this bug.