Bug 149738 - Minor inconsistencies in sparkline related UI strings
Summary: Minor inconsistencies in sparkline related UI strings
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
7.4.0.0 beta1+
Hardware: All All
: medium minor
Assignee: Julien Nabet
URL:
Whiteboard: target:7.5.0
Keywords:
: 150519 150699 151409 (view as bug list)
Depends on:
Blocks: Sparklines
  Show dependency treegraph
 
Reported: 2022-06-26 17:18 UTC by Ming Hua
Modified: 2022-10-08 09:57 UTC (History)
7 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 Ming Hua 2022-06-26 17:18:24 UTC
It's great to see sparklines feature added in 7.4.

As a translator I've found the following two small problems with the UI strings for sparklines:

1. The standard UI menu: "Insert > Insert Sparkline...".  All the other entries under "Insert" don't have the starting "Insert".  It's probably better to make it "Insert > Sparkline...".

2. In the "Sparkline Properties" dialog, "Axes" section at the bottom, the "Vertical maximum" label is missing a colon (:) in the end, should be "Vertical maximum:".

I don't think it matters, but this is seen with 7.4.0 beta1 on Windows 11.
Comment 1 Ming Hua 2022-06-26 17:22:54 UTC
One more thing that I don't think necessarily a bug, but worth discussion:

As the help documentation [1] says, the "Stacked" type is also known as win/loss type.  I don't know how it's named in MS Excel, but we already use "stacked" type for regular column charts, and there it's quite different from this "stacked" sparkline.

1. https://help.libreoffice.org/7.4/en-US/text/scalc/01/sparklines.html?DbPAR=CALC
Comment 2 Julien Nabet 2022-07-11 09:27:25 UTC
On pc Debian x86-64 with master sources updated today, I could reproduce this.

I submitted a patch here to fix typos indicated in initial description:
https://gerrit.libreoffice.org/c/core/+/136955

It seems it won't be possible to cherry-pick on 7.4 branch since hard English string & UI freeze is over (see https://wiki.documentfoundation.org/ReleasePlan/7.4)

Sophie/Adolfo: don't hesitate to tell if I'm wrong or if exceptions can be made.
Comment 3 sophie 2022-07-11 10:12:49 UTC
(In reply to Julien Nabet from comment #2)
> On pc Debian x86-64 with master sources updated today, I could reproduce
> this.
> 
> I submitted a patch here to fix typos indicated in initial description:
> https://gerrit.libreoffice.org/c/core/+/136955
> 
> It seems it won't be possible to cherry-pick on 7.4 branch since hard
> English string & UI freeze is over (see
> https://wiki.documentfoundation.org/ReleasePlan/7.4)
> 
> Sophie/Adolfo: don't hesitate to tell if I'm wrong or if exceptions can be
> made.

Thanks for your patch :) String freeze can only be broken for very serious reasons such as security fixes or major inconsistency in the UI. 
As this issue is of minor importance, I don't see the need to break string freeze.
Comment 4 Julien Nabet 2022-07-11 11:31:25 UTC
(In reply to sophie from comment #3)
> ...
> Thanks for your patch :) String freeze can only be broken for very serious
> reasons such as security fixes or major inconsistency in the UI. 
> As this issue is of minor importance, I don't see the need to break string
> freeze.

Ok no pb, it was just to be sure :-)
Comment 5 Commit Notification 2022-07-11 11:32:27 UTC
Julien Nabet committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/f8a84ef8f085251d545597a83d71b5b5b2f547d6

tdf#149738: Minor inconsistencies in sparkline related UI strings

It will be available in 7.5.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 6 Julien Nabet 2022-07-11 11:33:33 UTC
About stack part, let's wait for the result of the discussion if there's one.
Comment 7 Ming Hua 2022-07-11 13:30:27 UTC
Thanks for fixing this, Julien!

(In reply to Julien Nabet from comment #6)
> About stack part, let's wait for the result of the discussion if there's one.
Sure, and I can always open a new bug if necessary.
Comment 8 Ming Hua 2022-08-20 15:22:14 UTC
*** Bug 150519 has been marked as a duplicate of this bug. ***
Comment 9 Heiko Tietze 2022-08-31 08:54:45 UTC
*** Bug 150699 has been marked as a duplicate of this bug. ***
Comment 10 Julien Nabet 2022-10-08 09:57:33 UTC
*** Bug 151409 has been marked as a duplicate of this bug. ***