Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 235341 - [fix available] Letters overlap in pdf of OOo
Summary: [fix available] Letters overlap in pdf of OOo
Alias: None
Product: Fedora
Classification: Fedora
Component: freetype
Version: 6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact: Brock Organ
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-04-05 10:03 UTC by Paul Smith
Modified: 2008-05-06 19:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-06 19:28:13 UTC

Attachments (Terms of Use)
Small screenshot of the pdf output (deleted)
2007-04-05 10:03 UTC, Paul Smith
no flags Details
A small odt file exhibiting overlapping letter in the pdf output (deleted)
2007-04-05 10:04 UTC, Paul Smith
no flags Details
patch to freetype to fix this (deleted)
2007-04-07 11:20 UTC, Caolan McNamara
no flags Details | Diff

System ID Priority Status Summary Last Updated 74609 None None None Never

Description Paul Smith 2007-04-05 10:03:25 UTC
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.

Comment 1 Paul Smith 2007-04-05 10:03:25 UTC
Created attachment 151747 [details]
Small screenshot of the pdf output

Comment 2 Paul Smith 2007-04-05 10:04:37 UTC
Created attachment 151748 [details]
A small odt file exhibiting overlapping letter in the pdf output

Comment 3 Patrick 2007-04-05 13:14:37 UTC
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

Comment 4 Caolan McNamara 2007-04-05 14:56:57 UTC
Can I get the rpm -q output of 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.

Comment 5 Paul Smith 2007-04-05 15:15:37 UTC
Here, it is:

$ rpm -q

Comment 6 Robin 2007-04-05 15:36:48 UTC
OpenOffice has just released version 2.2.  This could be fixed already.  Many
major improvements and much faster in saves/opens and macro operation.

Comment 7 Caolan McNamara 2007-04-06 09:56:27 UTC
nah, I believe this is
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

Comment 8 Caolan McNamara 2007-04-07 11:19:18 UTC
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

Comment 9 Caolan McNamara 2007-04-07 11:20:00 UTC
Created attachment 151911 [details]
patch to freetype to fix this

Comment 10 Sammy 2007-04-07 21:52:10 UTC
When I recompile freetype with the above patch it is crashing ooimpress
and anything that uses freetype in FC6!

Any reason?

Comment 11 Sammy 2007-04-08 15:44:13 UTC
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!

Comment 12 Sammy 2007-04-08 15:52:12 UTC
If one converts the document to another font like Arial the problem
does not exist (it is in NewTimesRoman originally)!

Comment 13 Bug Zapper 2008-04-04 06:46:55 UTC
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
the change.

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: 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

Comment 14 Paul Smith 2008-04-25 18:51:53 UTC
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.


Comment 15 Rodd Clarkson 2008-05-04 00:56:08 UTC
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.

Comment 16 Bug Zapper 2008-05-06 19:28:12 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.