Problem description: If you create a cross-reference field in an ODT document, with the Type as 'Numbered Paragraphs' and the 'Insert reference to' as Number, then save the file as a 'Microsoft Word 97/2000/XP/2003 (.doc)' file, then close and reopen the .doc file, the field has become changed: its 'Insert reference to' property is now Reference. This has the effect that a cross reference to a numbered paragraph correctly displays a paragraph number in the ODT document, but it displays a blank in the .doc version of the document. Steps to reproduce: 1. Open a new document. 2. Insert a numbered paragraph. 3. In a new paragraph, insert a cross-reference to it, with 'Insert reference to' as Number, as described above. Observe that it correctly displays the paragraph number. 4. Save as ODT, close and reopen the document. Observe that it still correctly displays the field. 5. Right-click on the field and choose Fields. Observe that 'Insert reference to' is still set to Number. 5. Now save the document as .doc, responding 'Keep current format' to the question about formatting. Close it and reopen it (the .doc version). 6. Observe that there is now a blank space displayed for the field. 7. Right-click on the field and choose Fields. Observe that 'Insert reference to' has become Reference. Expected behaviour: That the 'Insert reference to' is not changed upon save in .doc format. Operating System: Linux (Other) Version: 3.4.5 release
Thanks for reporting and these clear steps! I can not reproduce this behavior using Linux Mint 14 x64 with LibreOffice 4.0.0.3 rc3. I also notice you are using a quite old version of LibreOffice (3.4.5). Therefore I think this is already fixed, and would like to advice you upgrade LibreOffice to a newer version. You can download current stable version (3.6.5): https://www.libreoffice.org/download/ Or release candidate of LibreOffice 4.0: https://www.libreoffice.org/download/pre-releases/ You can find an installation guide here: https://www.libreoffice.org/get-help/installation/linux/ Therefore I mark this as WORKSFORME. Feel free retest this and REOPEN this bug if you still can reproduce this behavior with a more recent version. Kind regards, Joren
Hi Joren Installing the latest version did indeed cure the problem. Many thanks for your quick response. (I had such an old version because I use the Red Hat clone CentOS, and, typically for them, that was the latest version they had in their repositories.) Ed
Thanks for your retest and time you invest on reporting this bug. I won't be rude :-), but I'll set the bug status back to 'WORKSFORME' because we don't know exactly which commit this bug resolved... Otherwise: if we do know that, we can set status to FIXED. It's just our workflow ;-). Sorry about that. Kind regards, Joren
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.