The translations of Calc functions and error codes contain a few typos: Arabic UI: - The functions AVERAGEIF, GAMMA, RATE are translated to Arabic (but none of the other functions). Arabic should consistently use English function names. French UI: - The functions WORKDAY and WORKDAY.INTL have both been translated to "SERIE.JOUR.OUVRE". Swedish UI: - The error code #N/A has been translated to "#Saknas" which is not upper-case as all other error codes (in all languages). Dutch UI: - The functions GAMMA.INV and GAMMAINV have been translated to "GAMMA.INV". - The functions NORM.INV and NORMINV have been translated to "NORM.INV". - The functions T.INV and TINV have been translated to "T.INV". Portuguese (Portugal) UI: - The functions ERROR.TYPE and ERRORTYPE have been translated to "TIPO.ERRO". (no such problem in pt_BR though). Romanian UI: - The functions IFERROR and ISERROR have been translated to "ISERROR" (ouch!).
Right for the french UI, Daniel, This was seen a couple days ago, and corrected now. Second function SERIE.JOUR.OUVRE was renamed SERIE.JOUR.OUVRE.INTL and will be available in the master and next LO 4.4 and 5.0. I don't knows how you proceeded to detect them, but will be happy to learn a bit more about.
I checked Dutch and Portuguese on Pootle server (eg https://translations.documentfoundation.org/pt/libo_ui/translate/#search=ERRORTYPE&sfields=source,target), I confirm the pb. Sophie/Adolfo: thought you might be interested in this one. Should we cc the different language teams or should we just try to fix this in our brand new Pootle server? (or perhaps another idea on mind?)
Julien, this is best tackled by each language team. I will send a message to the l10n list to let them know about this.
I can confirm the Swedish part and have now made the change in Pootle. Thanks for the report.
@Jacques, I have built a test document to check the translated strings used in formulas. I will attach this document to this issue. Feel free to reuse it as you want, and to forward it to the other l10n teams (I did not check all locales supported in LO by myself).
Created attachment 118542 [details] Test document for function translations
The test document contains a column with formulas using all functions supported in LO 5.0, and another column that extracts the translated function names using the FORMULA() function. Just open the document with a specific UI language, and it will show the translated function names.
(In reply to Daniel Rentz from comment #6) > Created attachment 118542 [details] > Test document for function translations Thanks! Dutch strings corrected.
Nagy: thought you might be interested for Romanian part Adriano: thought you might be interested for Portuguese part For Arabic part, email declared in this page https://wiki.documentfoundation.org/Language_Teams doesn't seem to work.
Julian Thanks Awesome. Correct translation.
Thanks. Correct translations (LO-50-UI, LO-51-UI, LO-Master-UI).
Following Nagy and Adriano's feedback (thank you to them), there's still only Arabic UI to confirm. Daniel: could you give an update with recent LO version? (last one is 5.1.4)
Arabic seems to work as expected in the meantime, all function names are in English now. The only difference is that the English "WEEKNUM" has been translated to "ISOWEEKNUM".
Created attachment 125986 [details] Test document for function translations in 5.1 Note that for 5.1 four functions with *WEEKNUM* name exist in the UI, see https://wiki.documentfoundation.org/ReleaseNotes/5.1#Compatibility_with_ODF_1.2 ISOWEEKNUM WEEKNUM WEEKNUM_EXCEL2003 WEEKNUM_OOO These when saved and reloaded with 5.1 are mapped to ISOWEEKNUM WEEKNUM WEEKNUM ISOWEEKNUM so unfortunately updating the attached document accordingly with all four function names doesn't help. However, I added ISOWEEKNUM. And disabled regular expressions so a . dot in the function name doesn't lead to duplicates anymore ;-)
Created attachment 125987 [details] Test document for function translations in 5.2 Updated with new function names in 5.2, see https://wiki.documentfoundation.org/ReleaseNotes/5.2#New_spreadsheet_functions
Korean language contains two typos (LO 5.1.4.2) IFERROR is translated to ISERROR (collides with real ISERROR) IFNA is translated to ISNA (collides with real ISNA)
Thai UI: - The functions DAYSINMONTH, DAYSINYEAR, DELTA, DISC, ISLEAPYEAR, MONTHS, PRICE, WEEKS, WEEKSINYEAR, YEARS, YIELD are translated to Thai (but none of the other functions). Thai should consistently use English function names instead.
Since I don't have more questions, I put it back 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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
Created attachment 136016 [details] Test document for function name translations in 5.4 Updated with function names as of LibreOffice 5.4
Created attachment 136017 [details] Test document for function name translations in 5.4 Erroneously in the previous attachment included the *_ADD and *_EXCEL2003 names of duplicated functions that lead to duplicate names when reloaded. Removed.
** 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
FWIW, as this is an ongoing check I'll come up with a new document updated for 6-2 function names.
Created attachment 150855 [details] Test document for function name translations in 6.2 New since 5.4: 6.0: FINDB REPLACEB SEARCHB 6.2: REGEX
Hello Eike, See "Bug 125501 - Several function names seems not translatable", solved now for French UI. Jacques
Created attachment 166191 [details] Test document for function name translations in 7.0 New since 6.2: 6.3: FOURIER 7.0: RAND.NV RANDBETWEEN.NV
Dear Daniel Rentz, 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
(In reply to QA Administrators from comment #27) > Dear Daniel Rentz, > > 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. > ... Bug is supposed to be ongoing work for checking the translations.
Created attachment 194864 [details] Test document for function name translations in 24.8 New since 7.0: 24.8: FILTER LET RANDARRAY SEQUENCE SORT SORTBY UNIQUE XLOOKUP XMATCH