Bug 133170 - Line styles: duplicate & apparently unused definitions
Summary: Line styles: duplicate & apparently unused definitions
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.0.0.0.alpha0+
Hardware: All All
: low trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Shapes-Line
  Show dependency treegraph
 
Reported: 2020-05-19 12:44 UTC by Mihkel Tõnnov
Modified: 2024-09-03 03:14 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
"extra" line style available when UI language is Key-ID (98.46 KB, image/png)
2020-05-19 12:44 UTC, Mihkel Tõnnov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mihkel Tõnnov 2020-05-19 12:44:20 UTC
Created attachment 161006 [details]
"extra" line style available when UI language is Key-ID

There are 22 (0...21) defined line styles (RID_SVXSTR_DASH...).
Among these, there's two sets of duplicates:

RID_SVXSTR_DASH12, "Fine Dashed" (keyID xWgiA in current master), shown only if UI language is Key-ID (see screenshot).
RID_SVXSTR_DASH13, "Fine Dashed" (u34Ff), shown normally

RID_SVXSTR_DASH14, "Dashed" (hT4CE), shown normally
RID_SVXSTR_DASH20, "Dashed" (ibALA), not shown in UI

One more is not shown in UI and has a strangely unspecific name:
RID_SVXSTR_DASH21, "Line Style" (qEZc6)

Also RID_SVXSTR_DASH15, "Line Style 9" (T7sVF), could really use a more specific name.
Comment 1 Buovjaga 2020-09-02 19:39:21 UTC
Repro for the ones seen in UI with KeyID

Arch Linux 64-bit
Version: 7.1.0.0.alpha0+
Build ID: d784e711c102f204552c3c816636da01b1085f61
CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: kf5
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 29 August 2020
Comment 2 QA Administrators 2022-09-03 03:39:21 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2024-09-03 03:14:48 UTC
Dear Mihkel Tõnnov,

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

MassPing-UntouchedBug