[Bf-translations-dev] Some glitches with translations (or at least Spanish one)

[Gabriel Gazzán]

2012/9/9 Sergey Sharybin <sergey.vfx at gmail.com>

> Hi,
>
> 1) In the *left listing of channels in the Graph Editor*: none of the
>> tooltips, nor the LocRotScale string or the "<object>Action" string are
>> translated. Also the channel names (X Position, Y Position, etc.) remain
>> with the X, Y, Z letters to the left of the string, while in Spanish they
>> should be placed at the (right) end of the word (i.e. X Position <=>
>> Posición X)
>>
>
> That's true and it's not so obvious to fix. Such a strings are
> automatically generated based on property name (which is "Position") and
> vector component name (such as X, Y and Z).
> The question here would be (mostly to others from the translation team) --
> is there some general way to handle such a things from translation files?
> It'll be nice to have some general way handling such a things.
>

That should actually be two separate issues:
1a) strings not translated.
1b) channel X/Y/Z to the left, instead of the right side.

obviously (1a) is more important than (1b)
(1b) is more of a cosmetic issue that doesn't really affect the
understanding of the interface.





>
>
2) The *Scale* term is used in two different contexts, as verb and as noun,
>> each of which in Spanish are written differently:
>> - as a verb: Object Tools>"Scale" and Graph Editor>Key>Transform
>> menu>"Scale". (in Spanish it would be "Escalar")
>> - as a noun: Properties panel>Object context>"Scale:" and View Properties
>> panel>"Scale:". (in Spanish it would be "Escala")
>> in fact in the PO file there are two strings, one "Scale" and the other
>> "Scale:" but for some reason the first one seems to be the only one (I saw)
>> at use.
>>
>
> Properties (like Properties panel>Object context>"Scale:) does not contain
> colons in their names, colon is appending automatically. That's why Scale
> is used in both cases you're mentioning. "Scale:" goes from sequencer's
> transform effect.
>
I've implemented contexts for translations a while ago. Are there some
> issues with them or we simply need to move this words to different contexts?
>

Well, there seems to be issues, but I don't know how to help other than
what I said above (sorry if I don't fully understand your question), what
other kind of information would you need?

I think there should be one string for all the places where the word
*Scale*is triggering a command (i.e. representing a verb).
And another string for all the places where the word *Scale* is labeling
the current scale value or values of an element (i.e. representing a noun).
That is also valid for other words, such as *Transform*, *Translate*, *
Position*, *Rotate*, that in English could stand in place of a verb or a
noun but causes issues in other languages where the infinitive form of the
verbs are not written the same as the corresponding nouns.

To fully understand what it looks like now, imagine a part of the UI where
the users can read the transform values of an object and it currently says:
*Position: 0,0,0   Rotation: 0,0,0  To scale: 1,1,1*
it's strange.



> 6) The string *Active Keying Set used to insert/delete keyframes* don't
>> seem to be in the po file.
>>
>
>
> Not actually sure what does it mean. Is it about default name for Keying
> Set is not translatable? Otherwise i'm not so familiar with animation
> part..
>

The tooltip appears when you hover the mouse over the "two keys" icon on
the bottom right of the (Timeline) UI.
In fact when you click on the icon, the combo box that appears, shows all
of its options also untranslated.

Thanks for listening!

Gabriel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-translations-dev/attachments/20120910/7a98a0c6/attachment.htm