[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#254817: openoffice.org: mistaken font information on hand-installed font



Package: openoffice.org
Version: 1.1.1-3
Severity: important

I hand installed four truetype font files using dfontmgr.  All had
correct information indicating shape, etc.  They are all of a single
type, with a regular, bold, italic, and bold italic font.  Nothing is
wrong AFAICT in the defoma world or the fontconfig world.

When I start oowriter and look at the character format widget, the
font is listed as having only an Italic and Bold Italic version (no Regular
or Bold).  If I select Italic, it reports that the font exists for
both printer and screen.  If I selec Bold Italic, I get the *same
font* (not the heavier version), and it reports that the "closest
matching style will be used".  Killer of killers: the font being
displayed is the Bold Italic font!  (Even though the widget claims
that it is the Italic which is directly available.)

I also know something of what the problem is.  In the my pspfontcache
file, all four font files are found, and the key lines are as follows:

0;Garamond-Normal;1;5;5;2;65535;868;226;94;0;1176;1094;1176;1094;0
0;Garamond-Normal-Italic;1;5;5;2;65535;868;226;94;0;1301;1094;1301;1094;0
0;Garamond-Normal-BoldItalic;1;5;5;2;65535;868;226;94;0;1341;1094;1341;1094;0
0;Garamond-Normal-Bold;1;5;5;2;65535;868;226;94;0;1216;1094;1216;1094;0

Notice that the third and fourth fields are 1 and 5 for *all four
fonts*.  A looksie around intuits that the third field is shape and
the fourth is weight; but the shape of Regular is code 0, and Italic
is 2; the weight of bold is normally 8.  So if I hand edit these to:

0;Garamond-Normal;0;5;5;2;65535;868;226;94;0;1176;1094;1176;1094;0
0;Garamond-Normal-Italic;2;5;5;2;65535;868;226;94;0;1301;1094;1301;1094;0
0;Garamond-Normal-BoldItalic;2;8;5;2;65535;868;226;94;0;1341;1094;1341;1094;0
0;Garamond-Normal-Bold;0;8;5;2;65535;868;226;94;0;1216;1094;1216;1094;0

Suddenly all four fonts are recognized and everything works as it
should.  Of course this is quite fragile: as soon as my pspfontconfig
is regenerated wrt these fonts, the fix will vanish.

So the bug seems clearly to be in getting the information out of the
font files themselves.  I can provide the ttf font files on request to
aid in debugging.

Thomas


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: powerpc (ppc)
Kernel: Linux 2.4.20-ben10
Locale: LANG=C, LC_CTYPE=C

Versions of packages openoffice.org depends on:
ii  dictionaries-common [openoffi 0.22.27    Common utilities for spelling dict
ii  openoffice.org-bin            1.1.1-3    OpenOffice.org office suite binary
ii  openoffice.org-debian-files   1.1.1-2+3  Debian specific parts of OpenOffic
ii  openoffice.org-l10n-en [openo 1.1.1-3    English (US) language package for 

-- no debconf information




Reply to: