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

Michael Färber 01mf02 at gmail.com
Sat Mar 3 12:08:14 CET 2012


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



More information about the Bf-translations-dev mailing list