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

[Gabriel Gazzán]

I could not fine much time for hunting more occurences, but I'll do it.
For now I see this ones
Add > Metaball > "*Ball*", would be "Bola" or "Esfera" (both female)
Rogid Body Joint constraint Pivot Type: *"Ball"* would be "Esférico" (male)

but I suspect this one would already be differenciated by other contexts.

Also Mirror is currently problematic, because it is used as Symmetry and as
Reflection and in Spanish we would need one distinct word for each case.
"Simetría" and "Reflexión", but could also be used as a name "a Mirror",
and that would be "un Espejo".

g


2012/3/5 Michael Färber <01mf02 at gmail.com>

>
>
> On 03/03/2012 12:26 PM, Bastien Montagne wrote:
>
> 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…
>
>
> I like the idea of having an "operator" context, I think represents more
> closely the Blender terminology. :)
> I agree with most that you said.
>
>
>
> On 03/03/2012 04:39 PM, Gabriel Gazzán wrote:
>
> I've found the fact that the English words doesn't determine the gender of
> the term causing problems too.
> For example "New (object)" in Spanish should be "Nuevo (objeto)", but "New
> (texture)" should be "Nueva (textura)".
> That makes the use of a single text string problematic for translating
> into languages with similar gender structures as Spanish.
>
> Greetings,
> g
>
>
> Gabriel, that's a quite good point. Are there more examples like "New"?
> Would it solve the problem to have a context for each occasion where "New"
> appears? (A "World" context, a "Texture" context, ...)
>
> I created a small, incomplete list of ambiguous words:
>
>
>    - Scale -> operator, noun
>    - Render -> operator, noun
>    - Group -> operator, noun
>    - Fill -> operator, noun
>    - Mirror -> operator, noun
>    - Change -> operator, noun
>    - Set -> operator, noun
>
>
>
>    - Manual -> noun, adjective
>    - Light -> noun (sunlight), adjective (light fur)
>     - Open -> operator, adjective
>    - Clear -> operator, adjective
>
>
>
>    - Delete -> operator, key context (on keyboard)
>    - None -> context for each individual situation? (see "New" above)
>     - Volume -> no context (space), audio context
>     - Rate -> no context, sampling context (or change to "Sampling Rate"
>    in code?)
>
>
> What do you think about these solutions?
>
>
> Kind regards,
> Michael Färber
>
> _______________________________________________
> Bf-translations-dev mailing list
> Bf-translations-dev at blender.org
> http://lists.blender.org/mailman/listinfo/bf-translations-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-translations-dev/attachments/20120306/f2918382/attachment.htm