Bug 106599 - Citations produced by JabRef in Libreoffice can't be copied to another part of the same document
Summary: Citations produced by JabRef in Libreoffice can't be copied to another part o...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Bibliography
  Show dependency treegraph
 
Reported: 2017-03-17 17:21 UTC by ph0boss
Modified: 2023-04-02 19:26 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Example document with JabRef citation (8.00 KB, application/vnd.oasis.opendocument.text)
2017-03-17 17:56 UTC, ph0boss
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ph0boss 2017-03-17 17:21:51 UTC
Description:
JabRef is a citation manager (jabref.org). When inserting the citation from whithin JabRef everything works fine. When you try to copy the citation from one part of the document to another, it is pasted as a simple text, not as a reference.

Steps to Reproduce:
1. Insert a citation somewhere in the text
2. Copy text and citation
3. Paste in another part of document

Actual Results:  
No formatting is preserved. Text is pasted as plain text, loosing citation formatting

When text is cut-pasted formatting is preserved, but only for the first paste.
When text is copy-pasted to another document the formatting is preserved, but only for the first paste.

Expected Results:
Citation formatting should be preserved in all cases listed above


Reproducible: Always

User Profile Reset: No

Additional Info:
The bug has already been posted at JabRef bugtracker:
https://github.com/JabRef/jabref/issues/1878


User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
Comment 1 Xisco Faulí 2017-03-17 17:30:21 UTC
Hello,

Thank you for reporting the bug. Please attach a sample document with a citation from JabRef, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 2 ph0boss 2017-03-17 17:56:02 UTC
Created attachment 131966 [details]
Example document with JabRef citation

Added file as required
Comment 3 Xisco Faulí 2017-03-18 14:48:08 UTC
Confirmed in

- Version: 5.4.0.0.alpha0+
Build ID: d3b5bd4a07a619db6bee1c39c32280ac3c620532
CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

- Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)

- LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4
Comment 4 QA Administrators 2018-03-19 03:33:42 UTC Comment hidden (obsolete)
Comment 5 ph0boss 2018-03-24 06:55:40 UTC
Bug is still present in Libreoffice 6.0.2
Comment 6 QA Administrators 2019-03-25 03:44:46 UTC Comment hidden (obsolete)
Comment 7 SergeiD 2020-02-18 13:43:51 UTC
Bug is still present in Libreoffice 6.4.0
Comment 8 QA Administrators 2022-02-18 03:41:55 UTC
Dear ph0boss,

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 https://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://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug