If you have some bibliography entries present in your odt file and save it as doc or docx, you lose all bibliography. The actual text of those bibliography entries and index is still present (mostly), but the "metadata" are lost, so you can no longer insert the entries, update the entries or update the index. Simply put, it gets converted to a plain text.
Steps to Reproduce:
1. use the attached .odt file or create a new file by inserting new document-local bibliography entry and add a bibliography index
2. save the document as doc and docx (or see the attached documents)
You can't right click on biblio entries or index and see "bibliography entry" or "edit/update index" menu items. If you add a new index, it's empty. LO is not aware of any biblio in the document.
LO shows "[ CITATION "ABC"]" instead of "[ABC]" for entries. If you try to edit it using the right click menu, you see that all the metadata except title are empty (author, year). If you click "update index" on the index, again all the metadata except title disappear.
Doc and docx work the same way as odt.
User Profile Reset: No, but I tried this on several different computers (same OS, different users).
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0
Created attachment 130474 [details]
odt with some bibliography
Created attachment 130475 [details]
odt converted to doc (broken biblio)
Created attachment 130476 [details]
odt converted to docx (broken biblio)
I also reproduced this bug with LO 184.108.40.206-7.beta2 from Fedora Rawhide.
Win 7 Pro 64-bit Version: 220.127.116.11.alpha0+
Build ID: 1c27286b9d5331634c073cd3e327bd941e61bbb6
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default;
TinderBox: Win-x86@39, Branch:master, Time: 2017-01-23_03:24:17
Locale: fi-FI (fi_FI); Calc: group
Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735
Any chance of having this fixed soon? It's a major regression, seems to me, it corrupts all doc/docx files containing bibliography. That prevents me and probably a lot of other people from using LibreOffice at all.
(In reply to Kamil Páral from comment #6)
> Any chance of having this fixed soon? It's a major regression, seems to me,
> it corrupts all doc/docx files containing bibliography. That prevents me and
> probably a lot of other people from using LibreOffice at all.
How can it be a regression, though, when I could reproduce it with version 3.5?
It's a regression because it used to work fine in older versions. I can't say exactly which, but I'm quite sure the problem wasn't there in the past.
(In reply to Kamil Páral from comment #8)
> It's a regression because it used to work fine in older versions. I can't
> say exactly which, but I'm quite sure the problem wasn't there in the past.
Well, here are the old versions: https://downloadarchive.documentfoundation.org/libreoffice/old/
Instructions for parallel installs: https://wiki.documentfoundation.org/Installing_in_parallel/Linux
However, as the problem is already in 3.5, the regression cannot be bisected (=find out what caused the problem), because our binary bisection repositories stop at 3.5.
Doh, I confused "3.5" with "5.3". If you really reproduced this with 3.5, then it seems I'm very clearly wrong, because that's from 2012, and therefore this is not a recent (last year or so) regression.
** 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!
Still broken in LO 18.104.22.168.
Still broken in LO 22.214.171.124.
Also repro with
Version: 126.96.36.199.alpha0+ (x64)
Build ID: 01837a85004a6f891a09c0a63ed7eff75d634827
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win;
TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-09-01_00:07:05
Locale: en-GB (de_DE); UI-Language: en-US
*** Bug 127185 has been marked as a duplicate of this bug. ***
As Dieter said, this bug has been out for A LOT, and need to be fixed. Thank you