Bug 105429 - Names of new default set of cell styles not localized
Summary: Names of new default set of cell styles not localized
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Localization (show other bugs)
(earliest affected) rc
Hardware: All All
: medium normal
Assignee: Not Assigned
: 107361 114446 131845 (view as bug list)
Depends on:
Blocks: Calc-Styles Not-Localizable 90937
  Show dependency treegraph
Reported: 2017-01-18 20:04 UTC by Leif Lodahl
Modified: 2022-04-04 03:30 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Leif Lodahl 2017-01-18 20:04:38 UTC
Ubuntu Linux 64 bit.
LibreOffice Danish language pack (da-DK)
In Calc the names of cell styles are in English (Standard, Accent, Heading, Status, Text etc.)

These strings have been translated for months now.

Actual Results:  
Style names are in English

Expected Results:
Style names should be in Danish

Reproducible: Always

User Profile Reset: No

Additional Info:

User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0
Comment 1 Thomas Hackert 2017-01-21 13:34:01 UTC
Hello Leif, *,
thank you for reporting this bug :) I can confirm it with

OS: Debian Testing AMD64
LO: Version:
Build-ID: 5ad7b2889021c491af62f7930a4b1cb631392f16
CPU-Threads: 4; BS-Version: Linux 4.5; UI-Render: Standard; VCL: gtk2; Layout-Engine: neu; 
Gebietsschema: de-DE (de_DE.UTF-8); Calc: group
(parallel installed, following the instructions from https://wiki.documentfoundation.org/Installing_in_parallel/Linux with de_DE lang- as well as helppack)

so setting the status to "NEW".
Comment 2 Gabor Kelemen (allotropia) 2017-05-19 07:55:20 UTC
*** Bug 107361 has been marked as a duplicate of this bug. ***
Comment 3 Gabor Kelemen (allotropia) 2017-05-19 07:58:25 UTC
See attachment 132762 [details] from the duplicate bug.
Comment 4 Oliver Brinzing 2017-05-19 08:30:41 UTC Comment hidden (obsolete)
Comment 5 Yousuf Philips (jay) (retired) 2017-05-30 05:47:42 UTC
So the issue is that the names are being pulled from the xml file, so there are no code strings that can be set for translation.
Comment 6 Yousuf Philips (jay) (retired) 2017-10-19 10:10:33 UTC
Gabor: Is this something you can look into?
Comment 7 Gabor Kelemen (allotropia) 2017-10-19 12:59:19 UTC
(In reply to Yousuf Philips (jay) from comment #6)
> Gabor: Is this something you can look into?

Sure, I already tried to understand what's going on, but without success so far.
Comment 8 Markus Mohrhard 2017-10-19 19:05:14 UTC
ScOrcusFiltersImpl::importODS_Styles is the method that does the importing.

Most likely the only reasonable solution is to extract the style names and store them in an additional list that can then be translated and mapped back during import. Note that the ID part of the style name needs to stay the en_US string.
Comment 9 Yousuf Philips (jay) (retired) 2017-12-13 22:43:36 UTC
*** Bug 114446 has been marked as a duplicate of this bug. ***
Comment 10 QA Administrators 2018-12-14 03:55:40 UTC Comment hidden (obsolete)
Comment 11 Oliver Brinzing 2018-12-15 09:18:32 UTC
still reproducible with

Version: (x64)
Build-ID: 9d0f32d1f0b509096fd65e0d4bec26ddd1938fd3
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc:
Comment 12 Julien Nabet 2020-04-03 08:53:36 UTC
*** Bug 131845 has been marked as a duplicate of this bug. ***
Comment 13 Julien Nabet 2020-04-03 09:04:39 UTC Comment hidden (off-topic)
Comment 14 Julien Nabet 2020-04-03 09:05:38 UTC Comment hidden (off-topic)
Comment 15 QA Administrators 2022-04-04 03:30:56 UTC
Dear Leif Lodahl,

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