From: D. M. M. <mic...@ro...> - 2009-11-25 22:51:48
|
On Wednesday 25 November 2009, Jani Frilander wrote: > <Action name="insert_0_low" text="&I" shortcut="Z,Y" /> > > to activate that action, I first had to press Z and after that Y. > > So doesn't work in the way first thought. It's supposed to let you press either Z or Y, but in this case I think it doesn't work as you'd expect because of the conflict. > Isn't this like shooting a fly with a cannon? Is it worth it at this point? > > If it works, don't fix it. This one mostly does. It doesn't work. I spent two hours writing explanations of this situation and how to cope with it, making excuses for the crappy solution the whole time, and then going back and replacing the word "solution" with "workaround." Then I ran into "Play" while writing, and knew it was all over. If you have a string called "Play" in your translation, how do you translate it? If it's a keyboard shortcut (referring to the Play multimedia key on those new keyboards the kids are using, I am guessing) then you have to leave it as "Play" in English, or Qt will break it and it won't work, but if it's a tooltip (and there is just such a tooltip) then it should be translated so it doesn't appear in English. Which should you do? How can you know? You can't. It's time to eat it and solve the problem instead of working around it. This is just one example. We can start making excuses again. "Who cares about the Play multimedia key anyway?" "In this case, there is no conflict because 'Play' the tooltip isn't in the same translation context as 'Play' the keyboard shortcut anyway, so there is no real conflict here, and what's the problem?" But no, if it looks like shit and it smells like shit, then I don't have to taste it to find out whether it's shit or not. It's shit. -- D. Michael McIntyre |