Documentation: Section column output/Keep multi-column page layout
My question concerns the Scroll exporter documentation.
Some time not too long ago, the option "Render section macros as table" (if that was the designation) has been removed from the Word exporter in favor of the option "Keep multi-column page layouts". However, the documentation still describes how to define a style for sections macros: https://help.k15t.com/scroll-word-exporter/latest/server/defining-a-section-column-output-148668660.html
My understanding is that the specified style Scroll Section Column would now be obsolete as the option is no longer available. Am I mistaken? On the other hand, the new option seems to be missing in the documentation here too: https://help.k15t.com/scroll-word-exporter/latest/server/export-to-word-160661567.html
Is the documentation simply not up to date or did I miss something here?
Best regards
Cordula
-
Hi Cordula, thanks for your post.
I think this is a oversight on our part and the documentation hasn't been updated. Since Scroll Word Exporter v4.2, we have introduced the option to support the Confluence page layouts, in addition to the Section-Column macro formatting as tables. To preserve this styling you would need to enable the Keep multi-column page layouts export option that you mentioned.
Does this work for you?
I have updated our documentation accordingly to prevent other users experiencing the same question.
Thanks, Thomas (K15t)
-
Hi Thomas,
this actually erases the misunderstanding on my side that the section/macro would not be supported anymore at all in favor of the Confluence page layouts. So, that's solved.
I do have two follow-up questions, though:
1) Is it expected behaviour that all the content is enclosed in tables? That way headings cannot be used to structure the exported document as they are not formatted as headings anymore. I do not see how that is supposed to be helpful.
2) When exporting a page with a section/column macro using the bundled "Documentation Layout" with the activated option "keep multi-column page layouts", I would expect the content within the macro to be formated in the Scroll Section Column style as it is described https://help.k15t.com/scroll-word-exporter/latest/server/defining-a-section-column-output-172603384.html However, it seems to be exported int he Scroll Table Normal style which makes me wonder whether that is what it's supposed to and for what the Section column style would be then.
Cheers
Cordula
-
Hi Cordula,
To answer you questions in order;
1) Is it expected behaviour that all the content is enclosed in tables? At the moment this is the expected behaviour and due to limitation in the approach to support these layouts, it does currently come at a cost of the heading formatting. However, we are aware that this is something that users will require and therefore have an open improvement for supporting properly formatted headings in these layouts. You can view the related Jira issue here: https://k15t.jira.com/browse/EXP-479. In the meantime, please sign up to our JIRA (via https://k15t.jira.com/) in order to watch and comment on this issue. We'll then send a notification for every status update.
2) When exporting a page with a section/column macro using the bundled "Documentation Layout" with the activated option "keep multi-column page layouts", I would expect the content within the macro to be formated in the Scroll Section Column style. This is correct - was this not the case for you? With the latest version, when exporting either the Confluence page layouts and/or Section-Column macros, the exported Word file will use the Scroll Section Column table style (see below):
If this is not the case for you, please could you reach out to us via support@k15t.com and send us an XML export for the page that reproduces this problem. To export the content of a single Confluence page, please follow these instructions: https://help.k15t.com/creating-a-xml-export-of-a-single-page-111903666.html. Additionally, please could you also include a copy of the export template that you're using.
Thanks in advance, Thomas (K15t)
Please sign in to leave a comment.
Comments
3 comments