Am Dienstag, 4. Februar 2014, 21:29:32 schrieb Richard Levitte: > Hi, Hi,
> With the recent addition of "export" as a noun in
> src/common/imageio.c (that string had previously only existed as
> button labels, which I consider as verbs (in imperative tense, should
> anyone wonder ;-))), I have myself a closer look at how the macros C_
> and NC_ are used.
>
> My quick investigation showed that module names are used for context
> in some case, function (like "accel") in others. While this works
> when the strings are (more or less) complete sentences, it's worse
> with some single word strings. Simply put, this doesn't help
> translators at all.
>
> The example I have are the words "export" and "import". In English,
> they could be verbs ("to export" and "to import") and they could be
> nouns ("an export" and "an import" or short for "export module" and
> "import module"). In other languages, these words translate
> differently depending on how they are used (in Swedish, it's
> "exportera" when used as a verb, "export" when used as a noun).
>
> So, from a translator point of view, it would be MUCH more helpful if
> the context would be used in a linguistic point of view, by being a
> hint on how the string is used (especially in these not so obvious
> cases). Besides, this would mean that translators wouldn't have to
> translate "import" and "export" the same way in several places just
> because that button (verb) exist in several modules ;-)
there are different reasons to have context. Yours is that the word is
translated differently, in that case I agree that a differentiation according
to
that makes sense. However, with "accel" and also "preferences" it's also a
matter of formatting. In the general GUI we have mostly lower case strings
while in these (partly auto generated) cases they might all start with caps in
some languages (I did it that way in German).
> Thoughts?
"preferences" unfortunately has to stay as it is since that code is auto-
generated. Unless there is an urgent need to change that, then I could add an
optional <context> tag to the xml file from which we generate the code.
When a string doesn't exists with context and you feel the need for it, go
with linguistic contexts. If the string already has a context due to different
locations where it gets used you probably have to be creative. It's a decision
on a by-case basis.
> Note: if these context strings are used somewhere else, please inform
> me. In that case, would it be possible to simply add information for
> translators?
>
> Cheers,
> Richard
Tobias
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
