GNOME Bugzilla – Bug 156975
GIMP: Stroke Selection wrongly translated into "Stryk val" in swedish
Last modified: 2009-01-01 19:03:35 UTC
The swedish word "stryk" (among it meanings is stroke) has several meaning, and in its context in the GIMP Edit meny, the meaning will be "Cancel selection" rather than "paint along selection". I suggest adding the preposition "längs" which clarifies the meaning of this meny entry and leaves no room for interpreting it as "Cancel selection": "Stryk längs val"
Good point. We have to consider that "stroke" is being used for multiple similar operations, and whatever we decide should work consistently. We currently have lines like po/sv.po:msgstr "Stryk markering med tidigare värden" po/sv.po:msgstr "Stryk markering" po/sv.po:msgstr "Stryk slinga med tidigare värden" po/sv.po:msgstr "Stryk slinga" po/sv.po:msgstr "Stryk linje" po/sv.po:msgstr "Stryk med ett målarverktyg" po/sv.po:msgstr "Stryk kanal" po/sv.po:msgstr "Det finns inget aktivt lager eller kanal att stryka till." po/sv.po:msgstr "Kan inte stryka tom kanal." po/sv.po:msgstr "Ingen markering att stryka." po/sv.po:msgstr "Välj strykningsstil" po/sv.po:msgstr "Kan inte stryka tom väg." Adding "längs" would not work for "Stryk kanal" for instance, since "kanal" does not imply something you can move along. I agree that this should be fixed, but would prefer if we could find a better expression altogether. I will ask about this on the Swedish translation mailing list; please comment further either there or here in the bug.
Strings where "längs" is appropriate: po/sv.po:msgstr "Stryk markering med tidigare värden" po/sv.po:msgstr "Stryk markering" po/sv.po:msgstr "Stryk slinga med tidigare värden" po/sv.po:msgstr "Stryk slinga" po/sv.po:msgstr "Stryk linje" Need no for a preposition: po/sv.po:msgstr "Stryk med ett m�larverktyg" I don't know what this one implies, therefore cannot propose anything (perhaps "i" or "till"): po/sv.po:msgstr "Stryk kanal" I think this one need the preposition "i" (~ eng. "in") in Swedish: po/sv.po:msgstr "Det finns inget aktivt lager eller kanal att stryka i." Whereas "stryka" cannot be used without a preposition in here (its meaning will always be "cancel"), I propose "i": po/sv.po:msgstr "Kan inte stryka tom kanal." po/sv.po:msgstr "Ingen markering att stryka." No need to add a preposition in here: po/sv.po:msgstr "Välj strykningsstil" "längs" should be used in here: po/sv.po:msgstr "Kan inte stryka längs tom väg." Even though it might not be a such good solution, I think there is no way we (you) can come up with a way where the same preposition can be used everywhere and at the same time being grammatically correct (and keeping it somewhat easy to understand also). One thing that made me recognize this in the first place was that I have no knowledge of the English original strings (I have been running my GNOME in swedish ever since -- mostly as a proof-of-concept) and therefore couldn't recognize the strings' original meaning. my 2 öre --mikael
I was thinking more on the possibility of finding some other term than "stryka" altogether. I'm not at all happy about that word, not the least because of it's double meaning, but also because it isn't really very descriptive of the operation. I keep feeling there should be a much more natural term to use for this. I of course agree that we couldn't use the same preposition in all the strings, no matter what solution we end up with.
It would be nice if you could come to a conclusion here and fix the problem. I will be doing a last pre-release of GIMP tomorrow (if time permits) and we want to get 2.2.0 out by the end of this month.
OK, sorry. I did not close this with a resolution, as it is a pretty general problem and I didn't really consider fixing it "for real" in the 2.2 timeframe. So, for now, I'll go with Mikael's suggestion and we can take up this subject again later if warranted.
You don't need to resolve the bug if you think it isn't fixed yet. I was only wondering if this has been taken care of for 2.2. Sorry that I didn't realize that this had happened.
No, you were right; this should be closed, as I have done the changes we discussed in this bug. If/when we get to do a real overhaul of the terminology, it should be a new set of bug entries. I'm leaving this as closed as it is fixed for now.