Bug 103069 - Context synonyms menu does not show tags available on the corresponding thesaurus
Summary: Context synonyms menu does not show tags available on the corresponding thesa...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Linguistic (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: All All
: low minor
Assignee: Not Assigned
Depends on:
Blocks: Thesaurus
  Show dependency treegraph
Reported: 2016-10-09 19:14 UTC by Tiago Santos
Modified: 2022-02-06 03:43 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:
Regression By:


Note You need to log in before you can comment on or make changes to this bug.
Description Tiago Santos 2016-10-09 19:14:31 UTC
This is related to tdf#99999, so same example:

- Select in English (USA) language;
- type the word "normally";
- Right click→Synonyms.

Expected result:
- Show only synomyns: “usually”, “unremarkably”, “commonly” and “ordinarily”;
- Alternativelly, it could show also “remarkably (antonym)”.

Atual result:
- “usually”, “unremarkably”, “commonly”, “ordinarily” and “remarkably” are given as alternatives. 
- Antonym tag can be seem using the Thesaurus dialog, pressing Ctrl+F7 over the word. This procedure shows the expected result.

This bug applies to every tag/extra info that exists inside brackets. This bug affects all languages and it is not due to thesaurus construction issues. 
This is also relevant for all other tags that appear after the words. Exemplifying:
‘(tag) word (tag)’ should be presented as ‘word (tag)’

Possible solution:
Only strip the content inside parenthesis after selecting the words. 
That way, the replaced word does not have extra information, but the user is given all the relevant information to help him make a good decision.
Comment 1 Buovjaga 2016-10-24 11:21:46 UTC

Win 7 Pro 64-bit, Version: (x64)
Build ID: 8f96e87c890bf8fa77463cd4b640a2312823f3ad
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
Locale: fi-FI (fi_FI); Calc: CL
Comment 2 QA Administrators 2018-02-05 03:27:49 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2020-02-06 03:35:59 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2022-02-06 03:43:42 UTC
Dear Tiago Santos,

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