Bug 36094

Summary: Welsh Localised key combinations very awkward and inconsistent (at least on OS X 10.4.11)
Product: LibreOffice Reporter: cfr <reescf>
Component: LocalizationAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: sasha.libreoffice
Priority: medium    
Version: 3.3.2 release   
Hardware: PowerPC   
OS: macOS (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description cfr 2011-04-08 19:16:43 UTC
PPC G4 1.5 GHz OS X 10.4.11
LibO with Welsh (cy) language pack

First, I should say that I *very* much appreciate the efforts to localise for Welsh. Nothing I say should be interpreted in a way inconsistent with that. (I figure I probably sound frustrated but I do not fail to appreciate the efforts put into providing localisation for so many languages.)

The localisation for Welsh alters the keyboard combinations in ways which are inconsistent with the OS X norm and also internally inconsistent. That is, I have Welsh as the default for my OS X interface (insofar as this is possible - Apple hasn't gone out of its way or anything). I also have it set for the interface in LibreOffice.

This is very awkward however because system wide, command + a, for example, means "select all" but in LibreOffice it *sometimes* means "select all" and it *sometimes* means "open file". This means that I am continually getting the open file dialogue when I don't want it. This happens in the help browser, for example, which alters the combinations. It also happens  for the main LibreOffice interface (choosing a new document type to start, say) In the main application interface for Writer (when editing a document, say), the localisation doesn't change the combinations even when the menu items have been translated.

To make things even more confusing, the language pack doesn't change all of the keyboard shortcuts but only some of them. So command + q still quits even though this does not work for Welsh at all. (For one thing, there's no 'q' in Welsh.)

So in order to figure out what keys to use, the user has to somehow be conscious of the fact that she is (a) using LibreOffice; and (b) using sub-part so-and-so of LibreOffice (am I in Writer? have I opened help from Writer? am I in the main startup interface?); and (c) she has to remember which parts of the latter interfaces have been localised and which have not. So hiding, quitting etc. are not localised and use English keys, whereas starting a new text or calc document etc. are and use Welsh, while select, open etc. are localised in some bits of LibreOffice but not others.

It is quite difficult to think of a way this could be made more confusing.

For the OS I'm using, I would prefer the menus etc. to be translated but no keyboard shortcuts to be localised whatsoever. So quitting should be "Gadael" rather than "Quit" but it should still use command + q. This also avoids the problem that the OS won't allow certain key combinations to be used for certain things. (Firefox uses command + g for quit but it just fails to have any effect whatsoever.)

But obviously this might not be best for all OS setups.

But the localisation should at least be consistent within the LibreOffice interface even if it is not possible to make it consistent with the OS.
Comment 1 Jan Holesovsky 2011-04-14 05:22:32 UTC
Would you be able to help creating the shortcuts for Welsh, please?  It means adding them to:

http://cgit.freedesktop.org/libreoffice/libs-core/tree/officecfg/registry/data/org/openoffice/Office/Accelerators.xcu

Hopefully the structure of the file is reasonably easy to understand :-)

When you have that, would be great to send a patch to libreoffice@lists.freedesktop.org; see

http://wiki.documentfoundation.org/Development/Patch_Handling_Guideline
Comment 2 Björn Michaelsen 2011-12-23 12:01:19 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 3 sasha.libreoffice 2012-02-27 06:08:52 UTC
In 3.5.0 problem still exist?
Comment 4 Florian Reisinger 2012-08-14 13:57:19 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 5 Florian Reisinger 2012-08-14 13:58:41 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 6 Florian Reisinger 2012-08-14 14:03:14 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 7 Florian Reisinger 2012-08-14 14:05:28 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian