On 2011-04-18 12:49, Александр Мелентьев wrote:

2011/4/18 Andrea Turrini:

...

Hi all, a problem I find when I translate .po files is about collisions between shortcuts. In particular, it is not so easy to decide where to put the& (or _) in translated strings in order to ensure that each shortcut is unique. One possibility (for yast) is to generate .mo files and then to check the result. However this approach is quite slow and not all modules can be checked (e.g., when corresponding hardware is not available).

Do you know an easy way to find shortcut collisions?

Analysing /var/log/YaST2/y2log I am able to find some collision but I still need to launch yast and go throw several configuration steps in order to point out conflicts.

Regards, Andrea Hi, Andrea. There is NO easy way to find shortcut collisions, since gettext provides no way to determine whether two messages will be displayed on one screen at the same time.

Wasn't there an app used in KDE once upon a time? Dr Clash or some such? I remember I tried do figure out a way to handle clashes like these, but for the way I had thought about, you would need a menu tree and a tag telling whether a shortcut is global or not, or a tag telling where a shortcut is valid/active (this menu, this part of the app only, globally etc.), since some shortcuts will not clash despite being identical because they only work inside one specific menu, while others are e. g. app-wide, limited to context or even system-wide. BR, Gudmund -- This message and any replies to it is scanned by http://www.fra.se. Please direct any complaints about this to them. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org