Often, when exporting a Writer document of OpenOffice to pdf (using
the embedded icon), I get some letters overlapping contiguous letters.
A small screen-shot and an odt file are attached.
Created attachment 151747 [details]
Small screenshot of the pdf output
Created attachment 151748 [details]
A small odt file exhibiting overlapping letter in the pdf output
Just a confirmation. I opened the odt file, exported it as a pdf and checked it
with both Document Viewer and the latest Adobe for Linux on an up to date FC6
box. I saw the reported issue 2x:
1) first paragraph, the "t" & "s" in "the streets of Kiev" are overlapping
2) second paragraph, the "i" & "t" in "MPs to submit" are overlapping
Can I get the rpm -q output of openoffice.org-core please so that I'm sure I'm
looking at the same versions. I seem to see a small overlap in the b&m of submit
on FC-6, but not the other one reported ones.
There might be a scaling issue behind why I don't get the same results.
Here, it is:
$ rpm -q openoffice.org-core
OpenOffice has just released version 2.2. This could be fixed already. Many
major improvements and much faster in saves/opens and macro operation.
nah, I believe this is http://www.openoffice.org/issues/show_bug.cgi?id=74609
which is not fixed in 2.2.0 either, I'll backport that workspace to FC-6 and
devel. I think I've seen this before, it's where freetype and OOo disagree on
the glyph advancement values for glyphs.
Will be in the next FC-6 update, i.e. >= 2.0.4-5.5.19
Nah, that doesn't fix it. What fixes it is the next attachment. This is a
problem in freetype in FC-6 which wasn't in FC-5 or in FC-7. Same as bug 224539
Created attachment 151911 [details]
patch to freetype to fix this
When I recompile freetype with the above patch it is crashing ooimpress
and anything that uses freetype in FC6!
OK. I have built the latest freetype-2.3.3 which is working in general.
HOWEVER, the exact same problem exists when I convert the example odt
Is the above patch from the freetype cvs tree, If it is so then it does
not solve the problem.
By the way, we cannot access the bug 224539!
If one converts the document to another font like Arial the problem
does not exist (it is in NewTimesRoman originally)!
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
The problem occurred only with Times New Roman. I do not have that font anymore
on my computer (have removed msttcorefonts), and therefore I cannot test whether
the bug is really fixed.
Having read through this and done some (limited) testing I would suggest that we
could close this bug.
The original reporter can't reproduce it due to changes in his system
In f9-preview, the page in questions renders fine (using TimeNewRoman).
The original report was in regard to F6, which is no longer supported and f7
will soon be dropped (if it was even a problem there), so assuming it's not an
issue in f8 then it's not likely to cause problems.
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.