After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 757076 - "second" string needs different translation depending on context in Swedish
"second" string needs different translation depending on context in Swedish
Status: RESOLVED FIXED
Product: gthumb
Classification: Other
Component: general
unspecified
Other Linux
: Normal minor
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2015-10-24 23:17 UTC by Anders Jonsson
Modified: 2015-12-18 17:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Add context for seconds (1.16 KB, patch)
2015-12-12 22:44 UTC, Anders Jonsson
none Details | Review

Description Anders Jonsson 2015-10-24 23:17:29 UTC
Hi,
in the GUI of gthumb there is the string "seconds" in two places.

#: ../extensions/change_date/data/ui/change-date.ui.h:15
#: ../extensions/slideshow/data/ui/slideshow-preferences.ui.h:6
msgid "seconds"
msgstr "sekunder"

This is right for the change-date string.

This however need splitting because of the other string in Swedish. In the slide-show usage it is the part of a longer string:

#. This is the first part of the phrase "change automatically, every x seconds", where x is an input control that let the user choose a value.


In this usage, Swedish would use the singular form "sekund" instead.



My suggestion is thus to add a msgctxt so the two usages of the string can have different translations.
Comment 1 Anders Jonsson 2015-12-12 22:44:10 UTC
Created attachment 317257 [details] [review]
Add context for seconds

This adds a "Every x seconds" context to the "seconds" string for slideshow-preferences. This enables the two strings "seconds" to be translated independently from each other.
Comment 2 Michael Chudobiak 2015-12-18 17:30:51 UTC
This problem has been fixed in the unstable development version.

Thank you!