Apache OpenOffice (AOO) Bugzilla – Issue 10112
Document prints fine in Word and not in open office writer
Last modified: 2013-08-07 14:38:26 UTC
I found a document that does print well under Word and not under OpenOffice Writer 1.0.1. I edited a bit to make it a bit smaller, but the test is reproducible. The file will be attached. I hope it arrives ... (The original file is called chapter2_generationED2.doc and refers a chapter from a book about xdoclet that I download from www.theserverside.com).
Created attachment 4058 [details] Word file that doesn´t print well in OO
Reassigned to MRU
MRU->CMC: The only issue I can find is, that there is a page break after the TOC when the document is imported. The TOC itself is empty, because there are no TOC entries available and the TOc becomes updated after import.
Created attachment 4487 [details] example sxw file.
Not the ww8 filter, or if it is, its a subtle matter. cmc->fme: Open newly attached .sxw file. The first line *in* the toc has "page break before" enabled with page number start of "1". The toc lists the headings in the doc. There is only one. Change the heading "Code generation" to e.g. default style. Now (and heres the meat of the matter) update->index->table for the toc and now the para following the toc gets the page break before property and so leave the toc standing on its own on page one. Any ideas ?
.
FME: In SwTOXBaseSection::Update() there is some code that removes the content and inserts an empty txtnode that contains the break attributes. After the update the empty txtnode is removed again and the attributes are applied to the first txtnode in the tox section. Unfortunately this does not work if the tox section is empty after the update. In this case the break attribut is applied to the next txtnode after the tox. The bugdoc contains an table of contents which is empty after an update. Common, non-empty tables of contents are not affected. I'll change the target.
SBA: According to the OpenOffice.org roadmap (see http://tools.openoffice.org/releases) this issue was retargeted to "OOo Later".