Description: Ubuntu Linux 64 bit. LibreOffice 5.3.0.2 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
Hello Leif, *, thank you for reporting this bug :) I can confirm it with OS: Debian Testing AMD64 LO: Version: 5.3.0.2 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". HTH Thomas.
*** Bug 107361 has been marked as a duplicate of this bug. ***
See attachment 132762 [details] from the duplicate bug.
.
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.
Gabor: Is this something you can look into?
(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.
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.
*** Bug 114446 has been marked as a duplicate of this bug. ***
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
still reproducible with Version: 6.1.4.2 (x64) Build-ID: 9d0f32d1f0b509096fd65e0d4bec26ddd1938fd3 CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc:
*** Bug 131845 has been marked as a duplicate of this bug. ***
Backport for 6.4 on review here: https://gerrit.libreoffice.org/c/core/+/91614
Sorry wrong bugtracker
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 MassPing-UntouchedBug