Hi Petr, all, Petr Dudacek wrote:
>Hi Simon, Bert, All, > >this is a proposal how to fix keyboard shortcuts. > >There are some top-level menu items that have their shortcuts assigned >incorrectly - File (Bestand) and Edit (Bewerken) share 'b', Save and >Close under File menu share 's' etc. This definitely needs to be fixed >to improve usability of the applications. But as you can see in the mail >below, we have very little experience with Dutch software and therefore >we need your help with assigning the correct shortcuts. The idea is that >you would prepare a document with the shortcut assignments based on your >everyday experience - you know much better than us how the shortcuts >should be assigned - and send it to me. I'll file issues for that and >Ian will fix them in the database. This way, we'll have not only fixed >the current shortcut issues but we'll also have a useful document for >future releases. > >This is a proposal, so any comments or additions are welcome... > > > Sounds good to me! >Thanks, >Petr > >PS: For Save (Opslaan) and Close (Sluiten) that share 's', do you think >it's ok to reassign Opslaan to use 'p'? > > Actually, it's ~Openen, (Open) and ~Opslaan (Save) that share 'O'. Also there is Alles ~opslaan (Save All), but for some reason I cannot access this item using ALT+O (any idea why?) In OOo 1.1 we have ~Openen, O~pslaan, and Opslaan ~als. Keeping the accelerators the same as in 1.1 would make it easier for existing users to switch to OOo 2.0, that should be an important consideration. Also you don't have to reinvent the wheel. Shall I start to make an overview for the Writer top level menu? > >Simon Brouwer píše v Čt 13. 10. 2005 v 09:13 +0200: > > >>Hi Petr, >> >>Petr Dudacek wrote: >> >> >> >>>Hi Simon, >>> >>>yes, you're completely right, top-level menu items are much more >>>important than the rest of the GUI and their mnemonics shouldn't be >>>doubled (the Open/Save case is probably the best example). We will fix >>>these, but as we don't have so much experience with using Dutch >>>software, your help would be much appreciated here. I'd like to ask you >>>and/or the members of the Dutch community to >>> >>>file issues for mnemonics that you want to change and assign them to >>>iano (please don't forget to include the keyids of the strings into the >>>bug description) >>> >>>OR >>> >>>prepare a list of menu items where you want the mnemonics to be changed >>>(with the new mnemonics included, of course), send them to me and I'll >>>take care of filing issues for them. >>> >>> >>>Is this ok for you? >>> >>> >>> >>> >>> >>Sure! >>In fact I think there are already two volunteers who have offered to >>look into this specifically. >>The waiting is now for the new review build... >> >> >> >>>Thanks, >>>Petr >>> >>> >>> >>>Simon Brouwer píše v St 12. 10. 2005 v 21:40 +0200: >>> >>> >>> >>> >>>>Hi Petr, all, >>>> >>>>At 13:49 12-10-2005, Petr Dudacek wrote: >>>> >>>> >>>> >>>> >>>>>Hi Bert, >>>>> >>>>>my comments below... >>>>> >>>>>-- snip -- >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>> I'm not a programmer, so I'm not sure how all this works, but >>>>>> does this only involve placing or removing a "~" in the >>>>>> strings? >>>>>> If so, I don't see why we can't remove all the doubles now. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>There's a script that assigns the mnemonics automatically. The '~' is >>>>>used just to override the script's results. So the most systematic >>>>>approach is to modify the script. For now I'd suggest not to consider >>>>>double mnemonics as bugs because fixing of all of them would take too >>>>>much time and resources (and because it is possible to use them in the >>>>>GUI). Again, I agree that having double mnemonics is a problem and >>>>>should be fixed in further releases. I'll try to start a discussion >>>>>about this with the guys in Hamburg. >>>>> >>>>> >>>>> >>>>> >>>>I think that at least in the top level menus the mnemonics should be >>>>assigned with good judgement, for example the menu items that are most >>>>often used should have their own mnemonic that is also as easy to remember >>>>as possible. >>>> >>>>I just had a look at the present Dutch OOo 2.0 RC2 build. >>>> >>>>In the Writer ~Bestand (File) menu, both the items ~Openen (Open) and >>>>~Opslaan (Save) have the same mnemonic. Therefore, to save the file you >>>>have to press ALT+B, ALT+O, ALT+O, ENTER which is *four* key combinations >>>>instead of two otherwise. And I can't even activate the menu item "Alles >>>>~opslaan" using the keyboard. >>>> >>>>By the way, the top menu items ~Bestand (File) and ~Bewerken (Edit) share >>>>the same mnemonic, and between top menu items pressing the mnemonic again >>>>does not appear to work, so I cannot get to the Edit menu using the >>>>keyboard. >>>> >>>>While it will be less of a problem that mnemonics are automatically >>>>assigned in quieter areas of the UI, I think we do have to evaluate them in >>>>the top level menus of each module, and override them where necessary. >>>> >>>>For those who use mnemonics, this will make the software considerably more >>>>user friendly. By limiting ourselves to the top level menus I think it will >>>>not significantly delay the release schedule. >>>> >>>> >>>>Vriendelijke groet, >>>>Simon Brouwer. >>>> >>>> >>>> >>>>>>>nl.openoffice.org <<< >>>>>>> >>>>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> >>> >> >> > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- Vriendelijke groet, Simon Brouwer. >>> nl.openoffice.org <<< --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
