[Bf-translations-dev] "bpy.types.NodeFrame" using bad string.

[Bastien Montagne]

This is a known issue, at least partially solvable with contexts… But I 
was asked some time ago to do no more edits in code regarding such 
translations matters, so it won’t be fixed in any foreseeable future.

On 07/08/2013 21:13, Gabriel Gazzán wrote:
> the function:
> *  bpy.types.NodeFrame*
>   (the frame in which we can put node editor nodes into)
> should not be using the same "Frame" string that other time-related 
> functions use.
>
> it's impossible to do a good translation of it until someone separates 
> this function from the other ones.
>
> I personally have no idea how to do this myself, so I could only post 
> the petition here from time to time. And I will keep doing so... ;)
>
> Thanks for listening!
> Gabriel
>
>
>
> _______________________________________________
> Remember to *NEVER* commit to our svn's /trunk, but *ALWAYS* to relevant language po file under /branches!
>
> Found a missing msgid? Edit this doc: http://goo.gl/XcWcr
>
> Have some disambiguation issue (i.e. same english word that should be translated in more than one way, depending on the context)? Edit this doc: http://goo.gl/VzppJ
> _______________________________________________
> 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/20130807/3255573d/attachment.htm