Bug 77460 - Exporting to PDF from Presentation corrupts letter spacing with some fonts
Summary: Exporting to PDF from Presentation corrupts letter spacing with some fonts
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.2.3.3 release
Hardware: All macOS (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-15 01:08 UTC by Rich Teer
Modified: 2015-04-01 14:51 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Presentation that reproduces the bug (52.85 KB, application/vnd.oasis.opendocument.presentation)
2014-04-15 01:08 UTC, Rich Teer
Details
PDF exported from MacOS1068+LOv4303. (258.30 KB, application/pdf)
2014-07-22 12:17 UTC, Owen Genat (retired)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rich Teer 2014-04-15 01:08:02 UTC
Created attachment 97374 [details]
Presentation that reproduces the bug

I have a presentation (a sample of which is attached for the purposes of reproducing this bug) which uses the font Helvetica Neue. It looks OK in the presentation itself, but when I export it to PDF the letter spacing goes seriously awry, to the point of making the PDF unusable. :-(

If I open the exact same .odp file in LO 4.0.6 and export it to PDF, the issue does *not* present itself; the resulting PDF file is fine.
Comment 1 Owen Genat (retired) 2014-07-22 12:17:36 UTC
Created attachment 103279 [details]
PDF exported from MacOS1068+LOv4303.

Appears to work fine here under MacOS 10.6.8 using v4.3.0.3 Build ID: fcd3838c4097f7817b5b3984fd88a44e1edd8548 (x86) but please check the attached as I have no reference to work against.
Comment 2 Owen Genat (retired) 2014-07-22 12:19:25 UTC
Status set to NEEDINFO. Please change the status back to UNCONFIRMED once the the provided attachment has been checked / a newer version of LO has been tested and the results reported back here. Thanks.
Comment 3 QA Administrators 2015-02-19 04:34:25 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team

Message generated on: 2015-02-18
Comment 4 QA Administrators 2015-04-01 14:51:46 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

-- The LibreOffice QA Team This NEEDINFO Message was generated on: 2015-04-01

Warm Regards,
QA Team