The totals row/column header in pivot tables is composed of two separate strings: "Total" = key-ID gX9QE, location: globstr.hrc:154, context: STR_PIVOT_TOTAL "Result" = key-ID nRMet, location: globstr.hrc:141, context: STR_TABLE_ERGEBNIS This makes it very difficult to translate correctly. It should be substituted with a proper single string: "Total Result". Looking at the string definitions in the code (admittedly with layman's eyes) I get the suspicion that there may be more compounding in play besides the aforementioned: https://opengrok.libreoffice.org/xref/core/sc/inc/globstr.hrc#154 has "Total", "Data", "Group" https://opengrok.libreoffice.org/xref/core/sc/inc/globstr.hrc#140 has "Grand", "Result". If that is indeed the case, all the possible combinations should be replaced with respective composites as single strings.
Played around some more with a pivot table and found that "Total" is also compounded with these: "Sum" = FDigt, globstr.hrc:181, STR_FUN_TEXT_SUM "Count" = SZAUf, globstr.hrc:183, STR_FUN_TEXT_COUNT "Average" = B58nD, globstr.hrc:185, STR_FUN_TEXT_AVG "Median" = AoUSX, globstr.hrc:186, STR_FUN_TEXT_MEDIAN "Max" = YMzF9, globstr.hrc:187, STR_FUN_TEXT_MAX "Min" = A8fBH, globstr.hrc:188, STR_FUN_TEXT_MIN "Product" = oZVg5, globstr.hrc:189, STR_FUN_TEXT_PRODUCT "StDev" = 6FXQo, globstr.hrc:190, STR_FUN_TEXT_STDDEV "Var" = NhH7q, globstr.hrc:191, STR_FUN_TEXT_VAR All of these are also used on their own. Not sure about the other strings I mentioned in comment #0. The issue is inherited from OOo (found an old spreadsheet created with OOo 3.2.0 that shows "Total Result" translated in a way that could only stem from string compounding).
Let's set to NEW.
** 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 repro in current master.
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
*** Bug 171413 has been marked as a duplicate of this bug. ***
Since "my" Bug 171413 has been declared a duplicate of this very old and very inactive one, I'd like to boost it. Having prominent cells in a pivot table stick out like a sore thumb because they are not translated is a serious issue even for private use, let alone anything (semi-)professional, where presentation sometimes matters. This issue alone might prevent people from ditching Excel for Calc, since pivot tables are an essential tool for may applications. I understand that there are non-trivial reasons in the current implementation of pivot tables that make the main results label hard to translate. Are there any devs "in charge" for pivot tables and if so, are they aware of this issue? Is there any way I can help?