Bug 119499 - Spanish translation is missing in LibreOffice 6.1 - Calc - Spanish Version
Summary: Spanish translation is missing in LibreOffice 6.1 - Calc - Spanish Version
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Localization (show other bugs)
Version:
(earliest affected)
6.1.0.3 release
Hardware: All All
: medium normal
Assignee: Adolfo Jayme Barrientos
URL:
Whiteboard: target:6.2.0 target:6.1.1
Keywords:
: 119500 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-08-26 01:31 UTC by Albert Acer
Modified: 2018-09-03 20:48 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Albert Acer 2018-08-26 01:31:19 UTC
Description:
Translation errors in the following path of the Calc component of LibreOffice 6.1, Spanish Version:
Menu Bar> 'Datos' Menu> 'Define Range' option
Menu Bar> 'Datos' Menu> 'Select Range' option


Steps to Reproduce:
1. LibreOffice 6.1 Spanish Version> Calc> Menu Bar
2. 'Datos' Menu
3. 'Define Range' option; 'Select Range' option

Actual Results:
1. LibreOffice 6.1 Spanish Version> Calc> Menu Bar
2. 'Datos' Menu
3.1 'Define Range' Translation missing
3.2 'Select Range' Translation missing

Expected Results:
1. LibreOffice 6.1 Spanish Version> Calc> Menu Bar
2. 'Datos' Menu
3.1 'Definir Rango' instead of 'Define Range'
3.2 'Seleccionar Rango' instead of 'Select Range' 


Reproducible: Always


User Profile Reset: Yes



Additional Info:
[Information automatically included from LibreOffice]
Locale: es
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no
Comment 1 Albert Acer 2018-08-26 01:34:57 UTC
Este error en la traducción debería ser resuelto en la versión 6.1.1.

This translation error should be resolved in version 6.1.1.
Comment 2 Xisco Faulí 2018-08-28 10:35:46 UTC
The translation is done in 

https://translations.documentfoundation.org/es/translate/#search=Define%20Range...&sfields=source,target&soptions=exact&unit=151013650&offset=0

and

https://translations.documentfoundation.org/es/translate/#search=Select%20~Range...&sfields=source,target&soptions=exact&unit=151013651&offset=0

But I can reproduce it in

Versión: 6.1.0.3
Id. de compilación: efb621ed25068d70781dc026f7e9c5187a4decd1
Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; 
Configuración regional: es-ES (es_ES); Calc: group threaded

@Julien, @Adolfo, is it a problem with the ellipsis ?
Comment 3 Xisco Faulí 2018-08-28 10:43:18 UTC
*** Bug 119500 has been marked as a duplicate of this bug. ***
Comment 4 Julien Nabet 2018-08-28 12:09:28 UTC
(In reply to Xisco Faulí from comment #2)
>...
> @Julien, @Adolfo, is it a problem with the ellipsis ?

I'm not expert about typography but English message seems to use plain dots, see:
- https://opengrok.libreoffice.org/xref/core/officecfg/registry/data/org/openoffice/Office/UI/CalcCommands.xcu#1623
- https://opengrok.libreoffice.org/xref/core/officecfg/registry/data/org/openoffice/Office/UI/CalcCommands.xcu#1633

If ok for plain dots, I can do the changes quickly.

Waiting for your feedback.
Comment 5 Adolfo Jayme Barrientos 2018-08-28 18:26:09 UTC
I don’t know why you’re bringing up the ellipsis. It doesn’t matter! What matters in the translation is choosing the right placement for the accelerator (~).
Comment 6 Julien Nabet 2018-08-28 19:59:18 UTC
Just for information, with master sources updated today, I could reproduce this.
Comment 7 Xisco Faulí 2018-08-29 08:19:01 UTC
(In reply to Adolfo Jayme from comment #5)
> I don’t know why you’re bringing up the ellipsis. It doesn’t matter! What
> matters in the translation is choosing the right placement for the
> accelerator (~).

Ahh, you're right. I meant the accelerator, not the ellipsis...
Comment 8 Julien Nabet 2018-08-29 20:17:56 UTC
Checking translation/source/es/officecfg/registry/data/org/openoffice/Office/UI.po on master sources, I noticed there were no translation indeed here:
   3052 #: CalcCommands.xcu
   3053 msgctxt ""
   3054 "CalcCommands.xcu\n"
   3055 "..CalcCommands.UserInterface.Commands..uno:DefineDBName\n"
   3056 "Label\n"
   3057 "value.text"
   3058 msgid "~Define Range..."
   3059 msgstr ""
   3060 
   3061 #: CalcCommands.xcu
   3062 msgctxt ""
   3063 "CalcCommands.xcu\n"
   3064 "..CalcCommands.UserInterface.Commands..uno:SelectDB\n"
   3065 "Label\n"
   3066 "value.text"
   3067 msgid "Select ~Range..."
   3068 msgstr ""

Christian: thought you may have some ideas. Indeed Pootle has the translation but it's not present in the translations/source.
Comment 9 Adolfo Jayme Barrientos 2018-08-29 20:37:53 UTC
Solved for next RC.
Comment 10 Xisco Faulí 2018-08-30 08:18:26 UTC
(In reply to Adolfo Jayme from comment #9)
> Solved for next RC.

Could you explain how it was solved ?
Comment 11 Adolfo Jayme Barrientos 2018-09-03 20:48:07 UTC
> Could you explain how it was solved ?

Newer versions of Pootle can be confusing. It showed you a preexisting translation for that exact string, but it wasn’t “committed”, so it didn’t end up in the POs. All I did was accepting the suggestion.

I’m sorry for not finishing the Spanish translation on time for the release. My life’s been a whirlwind these last couple of weeks, and I’ve been struggling to keep up.