I've found the fact that the English words doesn't determine the gender of the term causing problems too.<br>For example "New (object)" in Spanish should be "Nuevo (objeto)", but "New (texture)" should be "Nueva (textura)".<br>
That makes the use of a single text string problematic for translating into languages with similar gender structures as Spanish.<br><br>Greetings,<br>g<br><br><br><div class="gmail_quote">2012/3/3 Bastien Montagne <span dir="ltr"><<a href="mailto:montagne29@wanadoo.fr">montagne29@wanadoo.fr</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">In fact, rather than "noun", "verb" and "adjective" contexts (I doubt<br>
the later would be much used, btw), I’d rather have an "operator"<br>
context – theoretically, operators should always be verbs (as they *do*<br>
something), while simple settings should always be nouns (as they *are*,<br>
represent something). In your example, Group as verb should only be used<br>
by grouping operator, while group as a noun should only be used by<br>
settings controlling which groups are used/selected/etc. This would also<br>
enforce good practices in labels themselves!<br>
<br>
Note also that we will have a default, not-named context, used for most<br>
common cases (e.g. "Volume" as space would be generic context, while<br>
"Volume" as sound would have it’s "Audio" context…).<br>
<br>
But agree this is a bit a tricky subject, as ideally we want to cover<br>
all problems (in all languages!!!) with as few contexts as possible… So<br>
let’s discuss a bit more, then I’ll start adding a few, most needed<br>
contexts, and we’ll see how it goes, processing by tries and errors if<br>
needed.<br>
<br>
Another idea, we could end having a few (3, 4 at most) holdall<br>
"disambiguation" contexts, to be used for corner cases when we can’t<br>
find a better solution…<br>
<br>
Le 03/03/2012 12:08, Michael Färber a écrit :<br>
<div class="HOEnZb"><div class="h5">> Hi all,<br>
><br>
><br>
> I thought a little bit about how to proceed with contexts:<br>
><br>
> Contrary to Sergey's commit message (see original message of Bastien<br>
> below), I believe that "Noun" and "Verb" contexts should be used as well<br>
> as something like "Brush" and "Modifier" contexts.<br>
> For example, the word "Group" can mean "to group" and "a group", but in<br>
> most cases it won't be relevant whether a group refers to a particle<br>
> group, an FCurve group, a node group etc. Moreover, the same word can<br>
> have different meanings in one context like "Particle" -- one may refer<br>
> to a "particle group", but one may also want to "group particles".<br>
><br>
> For this reason, I strongly advocate the use of "Noun", "Verb", and<br>
> "Adjective" contexts, which would solve about 80% of the context<br>
> problems on my TODO list. However, in the remaining cases I think we<br>
> should use other contexts as well, for example for "volume", which may<br>
> mean "audio volume" (context "Audio") and "spatial volume" (context<br>
> "Space"?).<br>
><br>
> What do you think? Can you think of translation examples requiring more<br>
> complicated contexts?<br>
><br>
><br>
> Kind regards,<br>
> Michael Färber<br>
><br>
><br>
> On 12/22/2011 10:24 PM, Bastien Montagne wrote:<br>
>> Hi translators and devs!<br>
>><br>
>> Sergey just added a way to have contexts in Blender RNA, so the hunt is<br>
>> open! :P<br>
>><br>
>> Now, we have to organize a bit things, as adding a context implies<br>
>> modifications of Blender code (nothing hard, but let’s try avoiding<br>
>> unneeded noise and cluttering with hundreds of various contexts). Also,<br>
>> adding a context will impact all translations. Having superfluous<br>
>> contexts in some languages is inevitable, but let’s try to avoid it as<br>
>> much as possible too.<br>
>><br>
>> To quote Sergey’s commit message, « Think context like "BRUSH" or<br>
>> "MODIFIER" are preferable than "NOUN" and "VERB" because in some cases<br>
>> the same english noun used in different areas better be translated<br>
>> differently to make translation more native. »<br>
>><br>
>> So here is what I propose (as we have a tracker, let’s use it!) :<br>
>> * Translators send requests for a new context to<br>
>> <a href="http://projects.blender.org/tracker/?atid=522&group_id=183&func=browse" target="_blank">http://projects.blender.org/tracker/?atid=522&group_id=183&func=browse</a> ,<br>
>> with headers of report/request formatted this way: "[CONTEXT]<br>
>> NAME_OF_CONTEXT". Request should also contain the po-paths of the<br>
>> affected properties.<br>
>> * Request is discussed a bit, and if it seems reasonable, context is<br>
>> added to code.<br>
>> * Translators can also send requests (on ML or tracker) to add<br>
>> properties to an existing context.<br>
>><br>
>> Note that the list of contexts currently in use will be in stats of each<br>
>> weekly report from now on.<br>
>><br>
>> Best regards,<br>
>> Bastien<br>
>> _______________________________________________<br>
>> Bf-translations-dev mailing list<br>
>> <a href="mailto:Bf-translations-dev@blender.org">Bf-translations-dev@blender.org</a><br>
>> <a href="http://lists.blender.org/mailman/listinfo/bf-translations-dev" target="_blank">http://lists.blender.org/mailman/listinfo/bf-translations-dev</a><br>
> _______________________________________________<br>
> Bf-translations-dev mailing list<br>
> <a href="mailto:Bf-translations-dev@blender.org">Bf-translations-dev@blender.org</a><br>
> <a href="http://lists.blender.org/mailman/listinfo/bf-translations-dev" target="_blank">http://lists.blender.org/mailman/listinfo/bf-translations-dev</a><br>
<br>
_______________________________________________<br>
Bf-translations-dev mailing list<br>
<a href="mailto:Bf-translations-dev@blender.org">Bf-translations-dev@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-translations-dev" target="_blank">http://lists.blender.org/mailman/listinfo/bf-translations-dev</a><br>
</div></div></blockquote></div><br>