Bug 134668 - There is no section template access - couldn't assign content to multi column design
Summary: There is no section template access - couldn't assign content to multi column...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Page-Layout-Columns
  Show dependency treegraph
 
Reported: 2020-07-08 23:57 UTC by Vollbracht
Modified: 2023-05-10 14:43 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
ToC Style in Styles.xml (14.53 KB, application/vnd.oasis.opendocument.text)
2020-07-08 23:57 UTC, Vollbracht
Details
ToC in office:automatic-styles (14.65 KB, application/vnd.oasis.opendocument.text)
2020-07-09 00:07 UTC, Vollbracht
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vollbracht 2020-07-08 23:57:41 UTC
Created attachment 162818 [details]
ToC Style in Styles.xml

In earlier days OOo has had columns in paragraph templates. Now we have columns in sections. But there is no access to a section's design so that I could assign it to an other section.
Currently I have a hundred xhtml files that need to be formatted for umpteen pages each, containing sections that should be multi column and others that shouldn't.

By now a section's styling information is in office:automatic-styles within content.xml It would be best if it were handled as per sample of paragraph styles. I fail to see why style:family="section" shouldn't appear in office:styles/style:style but in office:automatic-styles/style:style only. So there's no need to change odt format for this.

Current version will just ignore section styling in Styles.xml as you can see in attached tInStyles.odt

Same section styling in office:automatic-styles is regarded with minor problems.
Comment 1 Vollbracht 2020-07-09 00:07:54 UTC
Created attachment 162819 [details]
ToC in office:automatic-styles

saxon9 XSLT generated content from xhtml and given odt template

template was edited with kate to provide section style used by subsequently generated content.

Section style is unused in the template. So whenever I edit the template in LO/OOo that section style is gone.
Comment 2 Regina Henschel 2020-07-09 21:11:11 UTC
(In reply to Vollbracht from comment #0)
> In earlier days OOo has had columns in paragraph templates.

I don't know any version, that had columns in paragraph styles. There exist columns in frame styles.

> 
> Same section styling in office:automatic-styles is regarded with minor
> problems.

Which problems do you get? I can use the same style for several sections.

I too find no restriction of style elements of family "section" to automatic-styles.

Would if be sufficient for you, if the 'Format Sections' dialog would allow to copy the set of options from one section to another?
Comment 3 Vollbracht 2020-07-09 22:18:02 UTC
(In reply to Regina Henschel from comment #2)
> (In reply to Vollbracht from comment #0)
> > In earlier days OOo has had columns in paragraph templates.
> 
> I don't know any version, that had columns in paragraph styles. There exist
> columns in frame styles.
> 

Early versions of OOo or StarOffice. I never worked with anything else if I could avoid.

> > 
> > Same section styling in office:automatic-styles is regarded with minor
> > problems.
> 
> Which problems do you get? I can use the same style for several sections.
> 

Had a generated document where in second section the beginning was invisible. after inserting and removing a line break before that section, everything was fine.

> I too find no restriction of style elements of family "section" to
> automatic-styles.
> 
> Would if be sufficient for you, if the 'Format Sections' dialog would allow
> to copy the set of options from one section to another?

No! Automatic styles still won't persist if they aren't used, so I couldn't create a template containing such styles.

Wouldn't it be much easier to integrate section template handling into the means of handling paragraph, character, frame, page, number and table styles instead of creating a "copy style properties" solution?
Comment 4 Regina Henschel 2020-07-09 22:44:53 UTC
Request is clear now.

(In reply to Vollbracht from comment #3)
> Wouldn't it be much easier to integrate section template handling into the
> means of handling paragraph, character, frame, page, number and table styles
> instead of creating a "copy style properties" solution?

No, "Copy style properties" would have similar level as writing a Basic macro. Using custom styles for sections requires a lot of changes in core.