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 608826 - Add comments and context information to aid translation
Add comments and context information to aid translation
Status: RESOLVED FIXED
Product: solang
Classification: Other
Component: General
git master
Other Linux
: Normal normal
: ---
Assigned To: Debarshi Ray
solang-maint
Depends on:
Blocks:
 
 
Reported: 2010-02-02 18:33 UTC by André Klapper
Modified: 2010-04-16 08:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Fixes some of the issues (15.87 KB, patch)
2010-02-02 20:32 UTC, Debarshi Ray
none Details | Review
Proposed fix (17.46 KB, patch)
2010-02-02 21:29 UTC, Debarshi Ray
none Details | Review

Description André Klapper 2010-02-02 18:33:41 UTC
#: ../src/application/main-window.cpp:668
msgid "translator-credits"
msgstr ""
Comment for Translators welcome, like "Translators: Put your name heres"
http://live.gnome.org/TranslationProject/DevGuidelines

#: ../src/application/main-window.cpp:672
msgid "%1 Website"
http://live.gnome.org/TranslationProject/DevGuidelines

#: ../src/renderer/browser-renderer.cpp:207
#: ../src/renderer/enlarged-renderer.cpp:349
#: ../src/renderer/slideshow-renderer.cpp:143
#: ../src/renderer/slideshow-renderer.cpp:187
msgid "Previous"
#: ../src/renderer/browser-renderer.cpp:222
#: ../src/renderer/enlarged-renderer.cpp:363
#: ../src/renderer/slideshow-renderer.cpp:152
#: ../src/renderer/slideshow-renderer.cpp:196
msgid "Next"
Which subject do these words refer to? Is it always the same subject? In non-english languages these words vary depending on the gender of the subject, hence it cannot be correctly translated currently.

#: ../src/renderer/enlarged-renderer.cpp:293
#: ../src/renderer/slideshow-window.cpp:74
#: ../src/renderer/slideshow-window.cpp:109
#: ../src/renderer/slideshow-window.cpp:118
#: ../src/renderer/slideshow-window.cpp:127
msgid "In"

Very hard to translate properly without context.
Comment 1 Debarshi Ray 2010-02-02 20:31:25 UTC
(In reply to comment #0)

> #: ../src/application/main-window.cpp:672
> msgid "%1 Website"
> http://live.gnome.org/TranslationProject/DevGuidelines

Sorry, but I could not figure what the problem is. Can you please point it out?
Comment 2 Debarshi Ray 2010-02-02 20:32:13 UTC
Created attachment 152875 [details] [review]
Fixes some of the issues
Comment 3 André Klapper 2010-02-02 20:45:58 UTC
Adding a comment what %1 stands for is welcome. I assume it is the project name, however it makes it way easier for translators to know what they handle here :)

Great patch, thanks so much (also for the fast response)!
Comment 4 Debarshi Ray 2010-02-02 21:29:54 UTC
Created attachment 152879 [details] [review]
Proposed fix

Thank you for your attention and interest.
Comment 5 Debarshi Ray 2010-02-02 21:32:59 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.
Comment 6 Claude Paroz 2010-02-04 18:49:44 UTC
Sorry, but you abused the use of context.
Contexts should only be used when you have to disambiguate two identical strings used in two different contexts in your program (say "Export" used as a verb and "Export" used as a noun). They are not meant to add comments for translators.

When you just need to add some information needed by translators to help understanding the context, just use Translator comments, that is comments located on the line just before the translatable string in your source code.

Thanks anyway for your efforts for translators :-)
Comment 7 Debarshi Ray 2010-02-05 14:01:34 UTC
(In reply to comment #6)
> Sorry, but you abused the use of context.
> Contexts should only be used when you have to disambiguate two identical
> strings used in two different contexts in your program (say "Export" used as a
> verb and "Export" used as a noun). They are not meant to add comments for
> translators.

Do you think everything is wrong or you are pointing out specific changes?

For the single word strings it is easy to imagine that they might be used in different contexts in the future even if they are not now. So rather than hunting them down and changing comments to contexts later on, I thought it would be better to do them from the beginning.
Comment 8 Claude Paroz 2010-02-05 20:27:51 UTC
You're the judge to decide when you really want to use a context marker. I just want to make sure you don't always use context when you only want to add translator comments. It might lead to duplicate work for translators, because each different context string duplicates the string in the po file. It is desirable in some specific cases, but not always, of course.

If it is clear for you, feel free to close the bug.
Comment 9 Debarshi Ray 2010-02-07 20:33:51 UTC
(In reply to comment #8)

Thanks for the clarification. I am not going to change anything right now to disturb the translations. But the next time I change a bunch of translatable strings I will go over the whole thing again and make adjustments if needed to avoid burdening the translators with too many small changes here and there. (As of now I think the "%1 Website" string should have had a comment instead of a context.)