Bug 128539 - LO63: Tips of the Day do not lead to l10'd help but to en-US help pages
Summary: LO63: Tips of the Day do not lead to l10'd help but to en-US help pages
Status: RESOLVED DUPLICATE of bug 127756
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
6.3.0.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-01 17:30 UTC by Martin Srebotnjak
Modified: 2019-11-02 08:26 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Srebotnjak 2019-11-01 17:30:14 UTC
Description:
The Tip of the Day additional info link sometimes leads to LO help page.
But:
- it does not lead to the version's help page but to old help (i.e. to 6.2 instead to 6.3 help pages for LO63);
- it leads to online help and not to installed help, if available (it opens internet connection even if you have local and even localized help already installed on your computer;
- it leads to en-US pages and the links are hard-coded, so no way to open a localized help page for a localized tip of the day.

Is this feature really ready for prime time use to be enabled for localized builds?

Steps to Reproduce:
1. Open LO with Tip-of-the-Day enabled.
2. Example: localized tip for "Tools > Detective > Mark invalid data" includes the additional info link to en-US help page: https://help.libreoffice.org/6.2/en-US/text/scalc/01/06030800.html
3. Open the link  ...

Actual Results:
You get an out-of-date, unlocalized & online (and not offline) help page.

Expected Results:
Up-to-date, localized & offline (if available) help page.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Martin Srebotnjak 2019-11-01 17:31:54 UTC
BTW, using LO6322 with sl-SI langpack on macOS.
sl-SI localized help page should open.
Comment 3 Roman Kuznetsov 2019-11-02 08:26:52 UTC
it was fixed for 6.4 only

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