Created attachment 112004 [details] Writer-Ctrl+F2-Variables tab 1. Start Writer 2. Chose Insert - Fields - More fields or press Ctrl+F2 3. Chose Variables tab 4. Select Set variable, Insert Formula or User Field in Type list 5. Format list contains untranslatable string Standard It has no KeyID (5 symbol hash) in LO 4.4 beta2.
(In reply to Serg Bormant from comment #0) > > It has no KeyID (5 symbol hash) in LO 4.4 beta2. Given the date of this bug report, I'm going to guess that should read 4.4 RC2 ? Version -> 4.4.0.2 rc
(In reply to Robinson Tryon (qubit) from comment #1) > Given the date of this bug report, I'm going to guess that should read 4.4 > RC2 ? > > Version -> 4.4.0.2 rc Beta 2 was recorded above because RC doesn't contain qtz/KeyID locale. This also hasn't KeyID in daily dev build: Version: 4.4.1.0.0+ Build ID: f3ea88ef4431541ef85a26412b71e0e29b5cc529 TinderBox: Win-x86@51-TDF, Branch:libreoffice-4-4, Time: 2015-01-09_11:06:04 And yes it is untranslatable in both 4.4.0.1 rc and 4.4.0.2 rc.
(In reply to Serg Bormant from comment #2) > Beta 2 was recorded above because RC doesn't contain qtz/KeyID locale. > > This also hasn't KeyID in daily dev build: Ah, okay, thanks for the heads-up. We've got to make that information available to QA so we can triage these bugs. (In reply to Serg Bormant from comment #0) > REPRO STEPS: 0. Install a KeyID build https://wiki.documentfoundation.org/Language#KeyID > 1. Start Writer > 2. Chose Insert - Fields - More fields or press Ctrl+F2 > 3. Chose Variables tab > 4. Select Set variable, Insert Formula or User Field in Type list > 5. Format list contains untranslatable string > > Standard > > It has no KeyID (5 symbol hash) in LO 4.4 beta2.
The string 'Standard' comes from the localedata database, e.g., i18npool/source/localedata/data/en_US.xml. I do not think it even is translatable currently.
*** Bug 90306 has been marked as a duplicate of this bug. ***
I can confirm this in LibreOffice version 5.0.3 RC1
The 'Standard' number format code key word can be translated and is translated in various languages, just that these locale data files are not part of the UI translation, for reason that in some context you need a basic understanding of syntax and semantics of those locale data items. Btw, it might help to mention which locale we are talking about and what word it should be instead of Standard.. note that a Writer's field locale must not necessarily be identical to the UI locale, it depends on the language context of the text it appears in. Bug 90306 is not a duplicate as it mentions several other untranslated strings. However, I'm not going to reopen that as I don't know if those items were translated in the mean time.
** 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.1.6 or 5.2.3 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-20161108
With master sources updated yesterday, "Standard" is still untranslatable (tests with KeyID + Italian)
I can only point to comment 7 and underline that locale data is independent of the UI language. Any and all locales can be chosen for data in any UI language. If the "Standard" word should be translated in more locales I'm happy to accept either patches or proposals with a translated word and I'll change locale data.
** 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
Created attachment 160793 [details] One-line patch for zh-CN locale data Still present for zh-CN with version 7.0.0 alpha1, just that the English string has changed from "Standard" to "General". I've attached the patch needed to translate this string for i18npool/source/localedata/data/zh_CN.xml. @Eike, would you please apply this change? The format is old context diff, which is the best I can do on my Windows system for now. Hope it's good enough.
Sure, I can apply, if a Chinese word is what people expect to see in the number format codes instead of 'Standard'.. The English locales' keyword btw never was Standard but always General, except in en_NA and en_ZA. The original reporter probably saw the Russian locale's keyword Standard, he didn't tell.
(In reply to Eike Rathke from comment #13) > Sure, I can apply, if a Chinese word is what people expect to see in the > number format codes instead of 'Standard'.. I'm not sure I've understood this comment correctly, but yes, for the two cases I've found so far (1. Insert > Fields > More Fields... dialog in Writer, and 2. Format > Cell... dialog in Calc), I believe users with Chinese UI would prefer seeing my translation "常规" over the English word "General". If only my words is not convincing, I've added Kevin Suo, another Chinese user and long time contributor, to CC list and hope he can confirm my translation.
Eike Rathke committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/6193bf1541be95c3679cdc5c4a96d4ab5fc5218c Change [zh-CN] keyword 'General' to '常规', tdf#88233 It will be available in 7.0.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(In reply to Ming Hua from comment #14) > If only my words is not convincing, I've added Kevin Suo, another Chinese user and long time contributor, to CC list and hope he can confirm my translation. Yes, that makes sense. I have not looked into the locale data for many years (my first commit to the source code started many years ago from the locale data xml file). Verified fixed on master and 7.1 beta1 for Simplified Chinese locale. Also, I don't think we should keep this bug open in case others want to change that word for other locales - if they want they can file a new report.