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

List:       koffice
Subject:    [Bug 140546] Koffice don't embed fonts during printing Koffice don't
From:       Kurt Pfeifle <pfeifle () kde ! org>
Date:       2007-01-25 15:12:52
Message-ID: 20070125151252.25106.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=140546         




------- Additional Comments From pfeifle kde org  2007-01-25 16:12 -------
@ comment 13 (Thomas):

Thomas, I didn't "give a generic bug report". I commented on one, and discussed it. \
And I created an interesting reference document as well (I think). And I did so \
because that problem is a recurrent one in KDE (not just KOffice, and I said so). \
Yes, it may have touched 10 related topics -- so what? They are "related", and to a \
bit part unsolved. And to a big part also not fully understood by me (that's why I \
ask questions too). I'm trying to *help*, and trying to learn as well.

Thanks for hinting to the "fc-match" command; I didn't know that.

I'm aware that this won't be fixed in KOffice 1.6.x, and I'm not asking for doing it. \
What I'm asking for is help me fully understand the issues, so...

 ...so they can be explained to users, 
 ...so that there may be found workarounds,
 ...so that we could start recommending certain setups (font sets, etc.)
 ...or finally be transformed into a fully HOWTO/tutorial.

Is that asking for too much!?

The impression that was created by the first answer was "Leave me alone, I'm not even \
looking closely at your problem, and I'm not interested in it."

As you may know, I'm currently focussing on *all* printing + font related bugzilla \
entries, trying to find duplicates+invalids+fixed ones. But I don't want to just \
close as many as possible with for the sake of statistics, I want to gain something \
valuable from these investigations.

As for the "interesting reference document" I mentioned above: in the end it may turn \
out that the interesting part of it only reveals that somehow *my* font setup s and \
my font-config installations are b0rken. If so, it was worth while, should it help me \
understand what I need to change. Because I may possibly apply that knowledge to help \
half a dozen or so other users in the next 5 years....

No need to tell me "as you know....$foobar", when I myself outlined the same $foobar \
things in my advice to the user.

As you may be aware (bug 140006), I'm trying to create somewhere, somehow, a \
repository of test cases, reference documents, HowTos, articles and \
automated/scripted tests that deal with these problems (fonts, printing & PDF \
generation) for KDEPrint and KDE in general. And I'll take the liberty to use (in \
part) bugzilla comments a for getting started...

----------------------------

@ comment 14 (Sebastian):


   * How could this be solved, theoretically?
   Figure out why the above is the case + fix it :)   [...]

Hehe... invalid answer. Because I don't allow you to answer the second question by \
repeating my first one, when the first one seems to be unresolved for all of us  :-)


   "it seems the exact same line of text has different lengths"

Yes, and what's more: it seems to use an entirely different font altogether (not just \
different font metrics); you can see that when looking at some of the glyphs.

Thomas' hint about "fc-match" may help me figure it out, finally. Thanks for that, \
again!

What does puzzle me is that KWord still displays "Vera Sans" when indeed it seems to \
use a different font internally. First, that shouldn't happen IMHO. It should (in the \
future KWord 2.0) at least say something like "Vera Sans (emulated by FooBar)" if \
indeed FooBar is the underlying font, no? Second, how can I make KWord running on the \
same system that OOoWriter runs on use the same font that OOoWriter used to create \
that document??


   "did you define the same pagemargin/etc. settings for both of them?"

Yes. If you look again at my comment, you'll see that I created the .odt in \
OOoWriter, then opened in KWord, and first thing verified if the same page and margin \
settings were used here, and they were (because that was a previous issue I had with \
this kind of "conversion").

Also, the .odt is here (attachment 19401) to play with. Download it (if you've time \
and are interested), and open it on your own system in OOoWriter and in KWord and see \
if you experience the same discrepancy or not. If not, that would already narrow down \
the problem to one of my local setup (and the local setups of the many users who see \
the same thing), and it would be a first step to come up with a guide that helps \
avoid these issues.


   "[Scribus...] someone needs to look at there code"

Well, maybe a 10 minute chat on IRC, from developer to developer, would already give \
a good overview (I myself have no idea about it, I'm just posing the question....). \
____________________________________ koffice mailing list
koffice@kde.org
To unsubscribe please visit:
https://mail.kde.org/mailman/listinfo/koffice


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