Apache OpenOffice (AOO) Bugzilla – Issue 128394
There is no section template access - couldn't assign content to multi column design
Last modified: 2022-01-04 16:27:00 UTC
Created attachment 86963 [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.
Created attachment 86964 [details] ToC Style in Styles.xml
Created attachment 86965 [details] ToC Style in office:automatic-styles Generated file showing 2 sections sharing a style
I see in meta XML file: <meta:generator>LibreOffice/7.0.0.0.beta2$Linux_X86_64 LibreOffice_project/00$Build-0</meta:generator> So, please provide same document build from scratch with AOO.
Setting as Enhancement
(In reply to oooforum (fr) from comment #3) > I see in meta XML file: > <meta:generator>LibreOffice/7.0.0.0.beta2$Linux_X86_64 > LibreOffice_project/00$Build-0</meta:generator> > > So, please provide same document build from scratch with AOO. Sorry! Right now I have no access to my Windows AOO installation due to temporal incompatibility between Linux kernel 5.7.5 and VMWare Player. Although the template for the provided document had been built using LO, the document itself given as proof of concept had been built using saxon9 and xslt from html source. Last thing I saw within my Windows OOo installation was the necessity for that enhancement same way as in LO. Until now the given document cannot be provided from scratch - neither in AOO nor in LO. Its's meant to show how current versions react on documents created with future versions containing the enhancement.
(In reply to vollbracht from comment #5) > Until now the given document cannot be provided from scratch - neither in > AOO nor in LO. Its's meant to show how current versions react on documents > created with future versions containing the enhancement. We wait the same document but build with AOO. We need to reproduce and compare XML content.
I compared LO5 with AOO (Dev build) and I could not find any differences. If it is created with LO7, could it be some changes made in ODF 1.3 instead of ODF 1.2 extended? Can you describe where something should look different?
Thanks for comparing! The problem still is that there is no access to section templates within office suite. There is no need for open document format change. We can create documents using a single section template for several sections. (unzip - edit source - zip) But within office suite every section has its own automatic style. So there's no possibility to change a style for a bunch of sections sharing it except by editing the source. We are able to open a document with a shared section style. We should be able to edit this style and keep it shared when saving the document.
According with Peter to comment #7 AOO must add support ODF 1.3 *** This issue has been marked as a duplicate of issue 128282 ***