[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 140546] Koffice don't embed fonts during printing Koffice don't
From:       Kurt Pfeifle <pfeifle () kde ! org>
Date:       2007-01-25 17:16:54
Message-ID: 20070125171654.1058.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=140546         




------- Additional Comments From pfeifle kde org  2007-01-25 18:16 -------
OK, I'm now sitting again in front of the PC in question (but have only a few \
minutes); it is a SUSE 10.0 with KDE 3.5.5 and many updates from their repositories:

  $> fc-match "Vera Sans"
  arial.ttf: "Arial" "Regular"

On a different system (Sidux/current/unreleased) which is basically a Debian Sid \
(unstable), I get this:

    $> fc-match "Vera Sans"
    Bitstream-Vera-Sans.ttf: "Bitstream Vera Sans" "Roman"

OOo on Sid is 2.0.4.dfsg.2-3, on SUSE-10.0 it is 2.0.0.99.143-0.1. I'll need to test \
my .odt file on that Debian system as well, later....

One thing I see and find remarkable: OOo ships (on both systems) with a directory \
full of .afm files called "psprint/fontmetric/" (.afm files are metrics for \
PostScript fonts -- will not be relevant to TT fonts, but anyway...)

So one step further I am here now, thanks to you two: it *likely* is a local setup \
problem: 

 - fc-match shows different matches on SUSE and on Debian. 
 - Debian matches exactly, and SUSE "matches" Arial for Vera Sans, 
 - KWord on SUSE the same Vera document doesnt look like the OOo/SUSE. 
 - Debian's actual behavior with the document I need to verify still.

Cheers+thanks,
Kurt


[prev in list] [next in list] [prev in thread] [next in thread]