| Summary: | EDITING, FILEOPEN: cross-referencing HEADINGS in a sub-document from master-document fails | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | gui <guigonse> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | CC: | dani3l.grigoras, dgp-mail, emanuele.gissi |
| Priority: | medium | ||
| Version: | 3.4.5 release | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | All | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 107805, 107905 | ||
| Attachments: |
MASTER and SUB-docs with failing cross-references
Repaired MASTER and SUB-document with functionall cross-references |
||
Created attachment 55769 [details]
Repaired MASTER and SUB-document with functionall cross-references
To cross-reference the sub-document HEADINGS from the master-document, first you should cross-reference them from the same sub-document
I think this is merely a clearer description of the workaround indicated in comment 1 (although I am not certain). Added for clarity, in any case: 1. In the sub-document, at the required location (or highlighting the required range), Insert > Cross-reference... > Cross-references tab > Type of "Set reference" / "Bookmarks" > enter a meaningful Name > click Insert. 2. In the master document, Insert > Cross-reference... > Cross-references tab > Type of "Insert reference" / "Bookmarks" > select the required mark > click Insert. It may be that the current problem highlighted by this bug is actually a limitation of ODF. The ODF v1.2 specification is not very clear about how inter-document citations (of headings, bookmarks, or reference mark) are to be treated. I forgot to mention that the provided examples still fail under: - Debian 7.3.0 x86_64 using v4.1.4.2 Build ID: 0a0440ccc0227ad9829de5f46be37cfb6edcf72 - Crunchbang 11 x86_64 using v4.2.0.4 Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71 OS set to All. The Writer Guide v4.0, Ch. 13, pp. 377-380, does however mention that this type of cross-reference between documents requires a reference mark to be set at the anchor point, so it may even be that this particular case is not a bug. ** 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 on a currently supported version of LibreOffice (4.4.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02 BUG confirmed as described in Comment 1 in version 4.4.7.2 over WinXP SP3; I'll check other versions and OS asap. If, as Owen says in Comment 2 and 3, it's supposed to be an expected behaviour, I would like to recommend to enhance it to make HEADINGS levels in sub-docs referable from master-docs. Attachments still reproduce precisely the bug. ** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306 I can confirm it in version 5.3 (I'll check the subversion asap) trying to reference sub-docs headings from containing master-document. ** 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 *** Bug 124401 has been marked as a duplicate of this bug. *** It's still reproducible for me with Version: 6.3.0.0.alpha1+ (x64) Build ID: e92dcfdc7bd7b237e0bee26ff226a102d9e8e766 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-05-14_00:00:57 Locale: en-US (de_DE); UI-Language: en-US Calc: threaded and test documents from bug 124401 Still present in Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: f96004096268f5e71120678e32fc8c74055819aa CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Steps to reproduce 1. Open master document from attachment 5578 (and update links to other documents) 2. Edit the field "Error: Reference source not found" and add the correct cross reference to it (is is already selected in the "Edit Fields" dialog). => Cross Reference is displayed and works correctly 3. Tools => Update => Update All Result: Field changes again to "Error: Reference source not found" Dear gui, 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 No error message anymore when opening master from attachment 55769 [details].
=> RESOLVED WORKSFORME
|
Created attachment 55768 [details] MASTER and SUB-docs with failing cross-references but only if HEADINGS in the sub-document ARE NOT local cross-referenced from itself... Or, in other words, if you write a sub-document in wich you make cross-references to some of its headins, you will then cross-reference this headins from a master document in wich you have inserted the sub-doc; the rest of the headings will look OK when you insert the cross-reference, but doing a "Tools/Update/Update All" will convert all cross-references in a "Error: Reference source not found" message. Here you are a demo of a master and sub document with failing cross-references...