GNOME Bugzilla – Bug 474889
Bad string in /src/metacity.schemas.in.h:78
Last modified: 2007-12-09 23:51:43 UTC
The string explains an option (concluding that it lead to buggy behaviour). Many translation teams expressed that they see no sense in translation this string into 133 as it is far longer than any normal schemas explanation. There is also doubt that the option is useful at all.
Sorry for the typos: The string explains an option (concluding that it leads to buggy behaviour). Many translation teams expressed that they see no sense in translating this string into 133 languages as it is far longer than any normal schemas explanation. There is also doubt that this option is useful at all.
For reference, the string is: "Setting this option to false can lead to buggy behavior, so users are " "strongly discouraged from changing it from the default of true. Many actions " "(e.g. clicking in the client area, moving or resizing the window) normally " "raise the window as a side-effect. Set this option to false to decouple " "raising from other user actions. Even when this option is false, windows can " "still be raised by an alt-left-click anywhere on the window, a normal click " "on the window decorations, or by special messages from pagers, such as " "activation requests from tasklist applets. This option is currently disabled " "in click-to-focus mode. Note that the list of ways to raise windows when " "raise_on_click is false does not include programmatic requests from " "applications to raise windows; such requests will be ignored regardless of " "the reason for the request. If you are an application developer and have a " "user complaining that your application does not work with this setting " "disabled, tell them it is _their_ fault for breaking their window manager " "and that they need to change this option back to true or live with the bug " "they requested. See also http://bugzilla.gnome.org/show_bug.cgi?id=445447#c6." This comment was born out of the frustration of people setting this option when they shouldn't, and then complaining about the results. So: 1. I think it's beyond question that asking to translate this string into 133 languages, for an option whose use is strongly discouraged, is unfair on the translators. 2. I don't believe users are going to read that much text in the long description in any language. 3. I'd be quite happy with getting rid of the option entirely, and reducing it to some sort of configure option, because it is such a nuisance. But I would like to hear some feedback from my colleagues on this. (Can we actually remove GConf options, anyway, or will it break compatibility?) So this is something we need to decide. 4. If we keep the option as an option, I recommend changing the long description to: "Many actions (e.g. clicking in the client area, moving or resizing the window) normally raise the window as a side-effect. Setting this option to false, which is strongly discouraged, will decouple raising from other user actions. See http://bugzilla.gnome.org/show_bug.cgi?id=445447#c6."
I should have just ignored Havoc when he requested that the option be renamed to "raise-on-click". Sure, the name already existed elsewhere so certain users might know to look for something like this under this name...but really it's a very stupid name given the overloaded meaning. The previous name was much less likely to cause such confusion. We can go with #4, but we really do need to add something like "and ignore raise requests generated by applications" after the text "will decouple raising from other user actions".
Hup. Any movement on this? Would it be okay if I changed it before string freeze?
Um, sure, any time in the next two months should be fine.
k, done.