Description: At this moment, the functionality of Zotero in LibreOffice Writer is much worse than MS Word due to limitations in LO Writer. Even though LibreOffice Writer has the option to apply field shadings, it does not do the same for bookmarks, so it is difficult to distinguish citations in text. This is because there's no shading for Bookmarks in LibreOffice, which also, unfortunately, makes it much easier to accidentally corrupt/edit citations in-text. Moreover, I used to be able to simply copy and paste Zotero citations in MS Word to other parts of the text. However, I noticed that in Linux with LO Writer saving in docx and storing references either as bookmarks or ReferenceMarks I cant. This is due to another limitation in LO Writer being able to cut and paste citations, but not make duplicates (copy-paste). Zotero is the leading reference management software and it's really disappointing the due to LO Writer limitations many people heavily using reference manager software (e.g. academics) are forced to stick to MS Word just for that, when LO Writer is such a rich and mature software on par or many times better than MS Word. Please consider improving support for Zotero. Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: -
see work on bug 121945 and bug 121958 *** This bug has been marked as a duplicate of bug 121945 ***
I'm reopening this as this is not duplucicate of bug 121945. I'm not asking for better in-built references, I'm pointing out about the field handling
LibreOffice Fields are not editable in-text which is a requirement for Zotero citations, so Zotero cannot use them. There is partial support for Word fields in LibreOffice, but there has not been any updates on that front in a while and the support isn't good enough for Zotero to be able to use it.
It is a straight up duplicate, do not reopen without understanding our BZ workflow for enhancement. Scope of work needed for bug 121945 fully encompasses the issue in OP here. *** This bug has been marked as a duplicate of bug 121945 ***