|
|
|
Issue Links:
|
Part
|
|
This issue incorporates:
|
|
|
CONF-11409 CSS declared in web-resources should be included in RSS, Word and PDF exports.
|
|
|
|
 |
|
CONF-7623 PDF lacks title information from {code}-tags
|
|
|
|
|
|
|
CONF-6421 Links generated by the ContentByLabel-Macro are broken in PDF-exports
|
|
|
|
|
|
|
CONF-4104 Sections width not correctly displayed in PDF export
|
|
|
|
|
|
|
CONF-5564 Columns borders in PDF export always appear
|
|
|
|
|
|
CONF-2592
Export to HTML - index links not correct
|
|
|
|
|
|
|
|
|
|
|
CONF-6606
Images created by Gallery Macro are not correctly created into PDF-exports
|
|
|
|
|
|
CONF-3427
PDF export doesn't handle {color} tag properly
|
|
|
|
|
|
CONF-6533
New Code Macro is not correctly exported to PDF
|
|
|
|
|
|
|
CONF-3904 PDF Export - Hint macro not exporting correctly
|
|
|
|
|
|
|
CONF-6880 An indent macro which works well in PDF exports
|
|
|
|
|
|
|
CONF-4644 Fix PDF rendering of macros and images
|
|
|
|
|
|
|
CONF-10252 Support Navmap when it is exported to HTML format
|
|
|
|
|
|
|
|
|
|
CONF-10264
dynamictasklist2 does not format correctly on pdf export
|
|
|
|
|
|
Reference
|
|
This issue relates to:
|
|
|
|
CONF-7868 PDF Export with user created Macros crash
|
|
|
|
|
|
|
CONF-7425 Error in pdf export using content formatting macro
|
|
|
|
|
|
|
|
|
|
|
|
CONF-4551 Add all possible rendering output types to PageContext#getOutputType()
|
|
|
|
|
|
|
|
|
|
|
This issue is related to:
|
|
|
CONF-7598 Allow macros to add resources (e.g. images) to an export
|
|
|
|
|
|
CONF-11540 Resources requested by macros should be rendered in exports and notifications and other situations
|
|
|
|
|
|
|
At the moment, macros and other plugins that generate content are aware of their render mode but don't have the facilities to correctly render themselves for the destination format. The following things are often broken in the export of macros:
- links, especially to Confluence content
- images
- styles and complex markup
To fix this, macro plugins need access to a link/image URL generator for Confluence content.*
A better API that indicates which render modes are required would also help. The current method of relying on the author to check a field in the RenderContext means that the export render modes are often forgotten.
This issue incorporates specific instances of this problem.
- There is actually a linkRenderer in the renderContext already. But to use it means creating a Link object, which itself requires a GenericLinkParser, a Manager and the object to be linked to. Not the easiest interface to work with.
|
|
Description
|
At the moment, macros and other plugins that generate content are aware of their render mode but don't have the facilities to correctly render themselves for the destination format. The following things are often broken in the export of macros:
- links, especially to Confluence content
- images
- styles and complex markup
To fix this, macro plugins need access to a link/image URL generator for Confluence content.*
A better API that indicates which render modes are required would also help. The current method of relying on the author to check a field in the RenderContext means that the export render modes are often forgotten.
This issue incorporates specific instances of this problem.
- There is actually a linkRenderer in the renderContext already. But to use it means creating a Link object, which itself requires a GenericLinkParser, a Manager and the object to be linked to. Not the easiest interface to work with.
|
Show » |
|
.
Improvement
in our company's wiki we have the same problems exporting pdf.
Confluence 2.2.9
Stefan