[Bf-translations-dev] i18n: contexts now available!

[Bastien Montagne]

In fact, rather than "noun", "verb" and "adjective" contexts (I doubt 
the later would be much used, btw), I’d rather have an "operator" 
context – theoretically, operators should always be verbs (as they *do* 
something), while simple settings should always be nouns (as they *are*, 
represent something). In your example, Group as verb should only be used 
by grouping operator, while group as a noun should only be used by 
settings controlling which groups are used/selected/etc. This would also 
enforce good practices in labels themselves!

Note also that we will have a default, not-named context, used for most 
common cases (e.g. "Volume" as space would be generic context, while 
"Volume" as sound would have it’s "Audio" context…).

But agree this is a bit a tricky subject, as ideally we want to cover 
all problems (in all languages!!!) with as few contexts as possible… So 
let’s discuss a bit more, then I’ll start adding a few, most needed 
contexts, and we’ll see how it goes, processing by tries and errors if 
needed.

Another idea, we could end having a few (3, 4 at most) holdall 
"disambiguation" contexts, to be used for corner cases when we can’t 
find a better solution…

Le 03/03/2012 12:08, Michael Färber a écrit :
> Hi all,
>
>
> I thought a little bit about how to proceed with contexts:
>
> Contrary to Sergey's commit message (see original message of Bastien
> below), I believe that "Noun" and "Verb" contexts should be used as well
> as something like "Brush" and "Modifier" contexts.
> For example, the word "Group" can mean "to group" and "a group", but in
> most cases it won't be relevant whether a group refers to a particle
> group, an FCurve group, a node group etc. Moreover, the same word can
> have different meanings in one context like "Particle" -- one may refer
> to a "particle group", but one may also want to "group particles".
>
> For this reason, I strongly advocate the use of "Noun", "Verb", and
> "Adjective" contexts, which would solve about 80% of the context
> problems on my TODO list. However, in the remaining cases I think we
> should use other contexts as well, for example for "volume", which may
> mean "audio volume" (context "Audio") and "spatial volume" (context
> "Space"?).
>
> What do you think? Can you think of translation examples requiring more
> complicated contexts?
>
>
> Kind regards,
> Michael Färber
>
>
> On 12/22/2011 10:24 PM, Bastien Montagne wrote:
>> Hi translators and devs!
>>
>> Sergey just added a way to have contexts in Blender RNA, so the hunt is
>> open! :P
>>
>> Now, we have to organize a bit things, as adding a context implies
>> modifications of Blender code (nothing hard, but let’s try avoiding
>> unneeded noise and cluttering with hundreds of various contexts). Also,
>> adding a context will impact all translations. Having superfluous
>> contexts in some languages is inevitable, but let’s try to avoid it as
>> much as possible too.
>>
>> To quote Sergey’s commit message, « Think context like "BRUSH" or
>> "MODIFIER" are preferable than "NOUN" and "VERB" because in some cases
>> the same english noun used in different areas better be translated
>> differently to make translation more native. »
>>
>> So here is what I propose (as we have a tracker, let’s use it!) :
>> * Translators send requests for a new context to
>> http://projects.blender.org/tracker/?atid=522&group_id=183&func=browse ,
>> with headers of report/request formatted this way: "[CONTEXT]
>> NAME_OF_CONTEXT". Request should also contain the po-paths of the
>> affected properties.
>> * Request is discussed a bit, and if it seems reasonable, context is
>> added to code.
>> * Translators can also send requests (on ML or tracker) to add
>> properties to an existing context.
>>
>> Note that the list of contexts currently in use will be in stats of each
>> weekly report from now on.
>>
>> Best regards,
>> Bastien
>> _______________________________________________
>> Bf-translations-dev mailing list
>> Bf-translations-dev at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-translations-dev
> _______________________________________________
> Bf-translations-dev mailing list
> Bf-translations-dev at blender.org
> http://lists.blender.org/mailman/listinfo/bf-translations-dev