Bug 68836 - No hyphen symbols generated at end-of-line through hyphenation in PDF-export
Summary: No hyphen symbols generated at end-of-line through hyphenation in PDF-export
Status: RESOLVED DUPLICATE of bug 67370
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
4.1.1.2 release
Hardware: x86 (IA32) macOS (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-02 09:35 UTC by heidieboe
Modified: 2013-11-21 20:46 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Buggy PDF-export lacking hyphen symbols at end of line (36.48 KB, application/pdf)
2013-09-02 09:35 UTC, heidieboe
Details

Note You need to log in before you can comment on or make changes to this bug.
Description heidieboe 2013-09-02 09:35:31 UTC
Created attachment 85051 [details]
Buggy PDF-export lacking hyphen symbols at end of line

When generating a PDF-export the hyphen symbols that had been generated automatically through hyphenation do not show up in the exported PDF file.  They do show up in the ODT file.

Problem shows up only when turning on PDF/A option. See attachment.

Problem did not exist in older versions of Libreoffice (e.g. 3.5.4.2)

Also, I can reproduce the bug on at least 5 installations.
Comment 1 a.joensson 2013-09-26 16:04:23 UTC
I can confirm this bug with LO 4.1.1.2 on an iMac with Core i5 processor under OS X 10.6.8: Whenever exporting a LO writer doc into a PDF A/1, all hyphens generated by automatic hyphenation at the end of lines don't show up in the PDF: Hyphens must be added manually, often with an additional line break. Especially in longer and/or important documents (like applications to be send via e-mail) this is really nasty.
Comment 2 Mirosław Zalewski 2013-10-21 07:33:11 UTC
Hi

I can reproduce this issue on LibreOffice 4.1.2, Linux Debian testing amd64. Unfortunately, it has been already reported. Therefore, I mark this report as duplicate of previous one.

If you think that these reports do not concern the same issues, feel free to reopen this bug and provide additional info.

Best regards,
Mirosław Zalewski

*** This bug has been marked as a duplicate of bug 67370 ***