Bug 137132 - Provide a list of cross references in the Navigator (so they can be easily found)
Summary: Provide a list of cross references in the Navigator (so they can be easily fo...
Status: RESOLVED DUPLICATE of bug 137741
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-29 17:41 UTC by R. Green
Modified: 2020-11-06 15:02 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Writer file showing a problem with cross-references (120.66 KB, application/vnd.oasis.opendocument.text)
2020-09-29 17:41 UTC, R. Green
Details

Note You need to log in before you can comment on or make changes to this bug.
Description R. Green 2020-09-29 17:41:34 UTC
Created attachment 165951 [details]
Writer file showing a problem with cross-references

Version: 7.0.0.3 (x64)
Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e
CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win
Locale: en-GB (en_GB); UI: en-GB
Calc: threaded

Open the attached Writer file. At the end of the file is a numbered list: In real life, this could be a Bibliography or list of references at the end of an article, for example.

On page 1, I have entered cross-references linked to the numbers in the list.

PROBLEM: I would now like to (character) style these cross references, but how do I find them, except by scanning the text with the naked eye: tedious and error prone if you have a lot of references.

SUGGESTION: Provide a list of cross-references in the Navigator panel (just as you do for hyperlinks). Double-clicking moves the cursor to the selected position.
Comment 1 Dieter 2020-11-06 07:48:07 UTC
I think your request is covered by bug 137741. Do you agree?

=> NEEDINFO
Comment 2 R. Green 2020-11-06 12:37:12 UTC
Looks like it. OK to close bug report.
Comment 3 V Stuart Foote 2020-11-06 15:02:50 UTC

*** This bug has been marked as a duplicate of bug 137741 ***