To: QA (original post); l10n (localization issue) Hello everyone :)
On 19/12/2006, at 10:48 PM, Petr Dudacek wrote:
this message is related mainly to the Polish mnemonics but I suppose that it might be useful for the other languages as well. Therefore posting on this alias.
It is relevant to my language. Thankyou for posting it here.
some moments ago I fixed issue 69356 - PL: In Polish localization, two main submenus have the same accelerator (http:// www.openoffice.org/issues/show_bug.cgi?id=69356). A brief look at the menus in the Polish build reveals that there are more duplicate mnemonics (there are even cases where a single letter is used for 3 menu items - such as 'k' in Plik menu in Writer).
I've been fixing these dratted things since we first submitted our translation. I have a long list of them from QA, to fix in the next version.
Instead of filing an issue for every occurence of such problem, I suggest the following:There's been a Call for Action some time ago (search for "Call for Action: Mnemonics in OOo" in the archive of this alias). This initiative had a goal of improving the current status of mnemonics for different languages. More info can be found at http:// wiki.services.openoffice.org/wiki/Mnemonics_LocalisationA wiki page with tables for Polish exists here: http://wiki.services.openoffice.org/wiki/Mnemonics_PL
Ooh, this would be really helpful. :)Could I please have a blank copy of the wiki page (no Polish examples) to use in the VI project?
BTW, is there an easier way of identifying each mnemonic string in the translation file than simply grepping through and guessing which belongs where? Is the KeyID part of the string?
In general, there are two things to be done:1. Go through the (first level) mnemonics in the Polish build, find those that should be reassigned to a different letter and mark these desired changes into the tables on the wiki page. This should be done by you as the native users of the software.2. Once the table is updated, a single issue containing a link to the table is opened and all the new mnemonics are fixed in the translation database - I'll take care of that. Have a look at http://qa.openoffice.org/issues/show_bug.cgi?id=70907 as an example of such issue.
Yes, this makes sense. It would really help a lot to have a table like this. I know I'll have users falling over themselves to report the mnemonic clashes in version 2.1, which I will mostly have fixed in the translation files, so it would help a lot to be able to point them to this table, which could have a column for "Fixed in 2.2".
If you are interested in fixing the mnemonics this way, just let me (and the alias) know - I'll assist you with whatever is necessary.
I am, and please do. :)I would like to take this opportunity to describe two of the issues for my language in choosing keyboard shortcuts.
1. No accented letters can be used. Vietnamese is mostly composed of accented letters.
2. Vietnamese is also composed of monosyllabic, _short_ words.Combine the two of these, and we have very few options for mnemonics. The larger the number of menu items or dialogue controls, the more likely it is that we can't provide a unique shortcut for each one.
Consider, for example: Hide Ẩn (you can only choose N) Compress Nén (ditto) Red Đỏ (no choice)When we fill in our table, I invite you to come and have a look. In many cases, it is impossible, with the current constraints, to set unique shortuts. Until we can start using accented letters (we have 72 distinct vowels), or someone comes up with another way of handling mnemonics, we are going to have widespread accelerator conflicts.
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do)
http://groups-beta.google.com/group/vi-VN
PGP.sig
Description: This is a digitally signed message part
