-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
4.2.12, 6.9.0
-
14
-
Severity 2 - Major
-
5
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Words fail to wrap in PDF export:
Problem description:
When exporting a page to PDF, the export is breaking single words apart and wrapping parts of the word to the next line.
Current behavior:
This is a test page on customer's Confluence:
This is the PDF after the PDF export:
Steps to reproduce:
1. Click on Tools
2. Export PDF
3. Compare the Confluece page with the PDF exported. You can see the words wrapped wrong. (see the screen shots)Expected Behavior:
The PDF wraps correctly the words when needed.
Workaround
Enter this CSS in Confluence Admin > PDF Stylesheet
body, p, li, td, table, tr, .bodytext, .stepfield {
word-wrap: normal;
}
.wiki-content p {
word-wrap: normal;
}
NB: This will negate the changes made to resolve https://jira.atlassian.com/browse/CONF-24533. If you have long words (ie URL strings) that do not break, they will run off the edge of the page rather than wrap to the next line.
Also Note this additional workaround to PDF stylesheet application:
- causes
-
-
- Closed
-
- is caused by
-
-
- Closed
-
- is related to
-
-
- Gathering Impact
-
- relates to
-
-
- Closed
-
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
[CONFSERVER-26230] Words break unnecessarily when wrapping in PDF export
I used page layout >> three column section in confluence page.
and after exporting to pdf of that confluence page, page layouts are overlapping in pdf
used confluence version 6.15.1
Issue still present in (6.8.2) - workaround was successful while waiting on a proper bug fix from Atlassian.
Boris P
added a comment - The workaround doesn't seem to work for me in 5.10.1
Is this issue still unresolved?
Boris P
added a comment - The workaround doesn't seem to work for me in 5.10.1
Is this issue still unresolved? What is the status on this?? Can this be resolved as soon as possible? I totally agree with Karie's comments above. PDF export really needs to be improved on for this issue as well as CONF-31307. We shouldn't have to resort to using Adobe products after the export to clean up our documentation.
Anna McDonald
added a comment - Still having this issue in v5.6.6 - any progress towards a resolution?
Anna McDonald
added a comment - Still having this issue in v5.6.6 - any progress towards a resolution? 
Karie Kelly
added a comment - Hopefully Atlassian understands that because the PDF export is so very buggy, it cannot be effectively used for generating any documentation, especially anything is customer facing. We used it significantly in 3.5.x; but, since upgrading to 4.x, it has become useless and has resulted in us going back to Word documents and sharepoint for maintaining documentation - unfortunate given the value a wiki should provide - collaboration and sharing of information.
Karie Kelly
added a comment - Hopefully Atlassian understands that because the PDF export is so very buggy, it cannot be effectively used for generating any documentation, especially anything is customer facing. We used it significantly in 3.5.x; but, since upgrading to 4.x, it has become useless and has resulted in us going back to Word documents and sharepoint for maintaining documentation - unfortunate given the value a wiki should provide - collaboration and sharing of information. 
Dan Metz
added a comment - Note, this issue is still affecting us. The workaround does not work. I have located the issue. It is due to inconsistent implementation of span tags for coloring text in a page. Occasionally, due to edits in the page, a span tag coloring text may end or start in the middle of a word even if the entire text is meant to be the same color. This can be seen in the HTML output for a page. Example:
<span style="COLOR: rgb(0,0,0);">Sou</span>rce(s):
The span tags setting color must be implemented more intelligently.
Dan Metz
added a comment - Note, this issue is still affecting us. The workaround does not work. I have located the issue. It is due to inconsistent implementation of span tags for coloring text in a page. Occasionally, due to edits in the page, a span tag coloring text may end or start in the middle of a word even if the entire text is meant to be the same color. This can be seen in the HTML output for a page. Example:
<span style="COLOR: rgb(0,0,0);">Sou</span>rce(s):
The span tags setting color must be implemented more intelligently. So glad that I've finally found this workaround. Have wasted several hours trying to fix this problem using different CSS options, but hadn't tried defining "word-wrap: normal;" for the wikicontent. This information should be more easily accessible. When a company has documentation and an answers forum you don't expect to have to trawl the bug system to find out how to make the product work sensibly!
Having the same experience.
Destroying the utility of a high priority use case.