linuxdcpp-contributors team mailing list archive

[Steven Sheehy <question158821@xxxxxxxxxxxxxxxxxxxxx>]

Question #158821 on LinuxDC++ changed:
https://answers.launchpad.net/linuxdcpp/+question/158821

    Status: Open => Answered

Steven Sheehy proposed the following answer:
So basically you're asking for more translator comments to help identify
string context? One thing you may be underestimating is the name of the
file in which the string occurs. It's not ideal, but usually you can
tell by the name where it will appear. For example, if it's in
linux/settingsdialog.cc you know that it will appear in the preferences.
Admittedly it doesn't tell where in the preferences it is, but that at
least narrows it down.

There is quite a bit of translator comments already in places, but
there's definitely room for more. I tried to add comments to the strings
I thought needed it as I came across them, but it's a bit tedious to do
this for all strings. You can make a list of strings that you would like
us to add comments to and we can try to update them. Or even better, you
can add the translator comments yourself and send us the patch. :)

It doesn't take programming knowledge - just grep for the string in
linux/ folder then add a single line comment directly above the string
like so:

// TRANSLATORS: <your message here>

For glade files - just grep for the string in glade/ folder then add a
comments attribute like so:

<property name="translator_credits" translatable="yes" comments="Please
do not translate. Launchpad will automatically replace this text with
the names of the translators for the current language.">translator-
credits</property>

So as you find where strings are and what translator comment would help
to clarify its translation, you can add it to the source then send us
the patch.

-- 
You received this question notification because you are a member of
LinuxDC++ Contributors, which is an answer contact for LinuxDC++.