Bug 112354 - Cross-reference categories not shown in text when a document is open in another language installation of LO
Summary: Cross-reference categories not shown in text when a document is open in anoth...
Status: RESOLVED DUPLICATE of bug 44451
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-12 16:01 UTC by siames3
Modified: 2017-12-15 12:06 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
this is the original file (9.39 KB, application/vnd.oasis.opendocument.text)
2017-09-12 16:01 UTC, siames3
Details

Note You need to log in before you can comment on or make changes to this bug.
Description siames3 2017-09-12 16:01:30 UTC
Created attachment 136205 [details]
this is the original file

Hi,

I wrote an .odt in the English version of writer and sent it to my boss who is using the Catalan version. There is a problem with cross-references: even though the indexes say "Illustration Index" and "Index of tables", the cross-references in the text only show the number (not the reference category, which would be "Table" or "Illustration") - they show in the beginning but when you edit the document or press F9 to update them they disappear.

In that other installation, I can see all the references inside the other language's category for table (taula) but when I try to insert yet another one, it behaves the same (only inserts the number of the reference, even though I selected category and number).

Thanks
Comment 1 Dieter 2017-09-23 12:08:42 UTC
Thank you for reporting th bug. I opened the attachment and everything looks fine, using LO 5.4.2.1 (x64). So I can't reproduce it. What version of LO are you using / is your boss using? Can you add a document (for example pdf-document) with the "wrong" result?

I set the status to NEEDINFO. Please change it back to UNCONFIRMED after providing the infos.
Comment 2 Xisco Faulí 2017-12-15 12:06:21 UTC
This is the same problem as bug 44451, Closing as RESOLVED DUPLICATED

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