Created attachment 45099 [details] The master file and the subfiles generated in OpenOffice 3.3.1 In earlier version of OpenOffice upto 3.3.1, it is possible to break up a master document into a set of smaller file each contains a chapter in the master document file, provided that each chapter had use the Heading style appropriately. (i.e Heading 1 for the Chapter Title, Heading 2 for Subtitle,... body text for the text in the body of the chapter). When the master file has been set up like this. To break it up in OpenOffice, one would choose File->Send->Create Master Document. Upon saving the master file, OpenOffice would generate a master file and a set of files each contain a chapter. Please see attachment for the files generated when MasterFileToBeBrokenUp.odt is broken into test.odm (the master file) and test1.odt, test2.odt, test3.odt.... LibreOffice generate neither the master test.odm file, nor the test1.odt, test2.odt, test3.odt... It generated nothing. In short, the Feature that break the master document into a set of subdocument files no longer work
Not reproduced. The create master document works for me on 3.4 rc1.
(In reply to comment #1) > Not reproduced. The create master document works for me on 3.4 rc1. My platform is SLED 11 sp1 i586. Since the original problem was reported in Windows, would some one else confirm the issue on Windows xp/ Windows 7 ? Thank you!
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian
I have verified this bug on all LibreOffice Version 3.4.4 and 3.5. The bug is still there. Breaking Up Master Document into subdocuments failed exactly as describe previously. Please used the attached master file to try breaking up if you can not reproduce the failure. Thanks.
thanks for re-testing ! we rely on users to re-check their bugs vs. the latest versions :-) I imagine the problem persists for 3.6 but perhaps worth a check. So re-opening. Thanks.
dlphan: could you use an open format to compress the files like .zip, .gzip, ... and attach the new file? (I can't unrar it with Debian)
Created attachment 65786 [details] zip file of the reporter The reporter sent me the zip so I attach it.
On pc Debian x86-64 with Debian package 3.5.4.2, I reproduce the problem. With 3.5 sources updated 2 days ago, I don't reproduce the problem. Did you try with 3.5.5? If you reproduce the problem with it, you must wait 3.5.6 or test one of its pre-release
This bug is incorrectly in REOPENED status - moving to NEW. If it's been resolved in the past 2 years - please set to RESOLVED -> WORKSFORME. Thanks
The reason for not breaking up the file is that the used styles Heading 1/Heading 2 have an outline level "body text" (see 'Outline & Numbering' page in dialog "Edit paragraph style") OTOH there are the styles "Dau Chuong" and "Tieu Mac" that are children of Heading1/2 and they have an appropriate outline level.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
According to comment 14, this bug should be closed if it contains false formatted content. Can someone verify this?
No feedback since 2012. Moreover, I tried with LO 6.3.4 on pc Debian x86-64, it generated an odm file. dlphan: 1) Could you give a try to a recent LO version? 2) Also so can you give a look at https://bugs.documentfoundation.org/show_bug.cgi?id=35845#c14 Let's put this one to WFM meanwhile. Of course, don't hesitate to reopen this tracker if needed.