Tue, Jul 17
Thu, Jul 12
Am sorry, but this looks much more like feature request than actual bug report, we do not handle that here. Further more, dev time for i18n aspect of the project is pretty much NULL currently, so… we’ll have to live with what we have for now.
Tue, Jul 10
Thank you so much Brecht. That cleared my doubts.
"While Held" means keyframes are propagated to next frames as long as ("while") they hold the same value as the current frame ("held").
Mon, Jul 9
Sun, Jul 8
Tue, Jun 26
Sun, Jun 24
I do not yet know the inside working of the translation code, so this idea is just a gabbled thought in my head. Maybe all the definitions of CONTEXT strings should be placed outside, in a text file, and allowing translators to add their own definitions to it. The coding will just follow the context to insert the appropriate translation beneath it. Would this make life much easier for the translation portion of the code? I personally think I could live with this - of course, this is relating to homophones (words with multiple meanings).
Jun 13 2018
Jun 3 2018
May 29 2018
Snap to Symmetry (bpy.ops.mesh.symmetry_snap)
- threshold: "Distance within which matching vertices are searched."
- factor: "Mix factor of the locations of the vertices."
- use_center: "Snap middle vertices to the axis center."
May 10 2018
May 4 2018
May 2 2018
Thanks for taking this task on. I won't mind the wait.
Ah, yes this would have to be run through the .py and all .po
I'll claim then and run by @Bastien Montagne (mont29) to set me up as a translator as well and discuss if this is worth the hassle.
I wouldn't mind but:
Seems like a reasonable change, do you want to commit yourself?
Apr 30 2018
@Hoang Duy Tran (hoangduytran) : thnx for finding all these instances.
I'll have a look together with the others (soonish) unless someone else wants to step in?
Thank you all! :)
Hi Bastien, not sure how to add someone to Translations?
Could you do?
Hi and thx for the help on translations!
Apr 28 2018
Apr 27 2018
Apr 23 2018
Apr 20 2018
Apr 19 2018
Actually, I include the latest .blend file to help you, the loaded UI should have both windows opened to let you see the effects, all you need to do is to drop the 'blender.mo' file and change the language to 'Vietnamese' (Tiếng Việt) :
I include the .blend file to save someone the process of rigging and setting up to see the mocap 'Fixes'
Apr 16 2018
Apr 15 2018
@Bastien Montagne (mont29) can you have a look here.
Apr 14 2018
Apr 13 2018
I'll make sure of that @blend-it (blend-it)! I've start tackling the job, but I feel a little bit unsure about how to properly translate the pages.
From a brief research I've found out this guidelines: https://wiki.blender.org/index.php/Meta:Guides/Translation_Guide. Are they the only source of wisdom on the topic?
Is there a better section to start with? My first attempt was on the "text" section, and to be honest is taking more time I expected. Are you suggesting to first working on the titles and only then on the body?
Also it's not quite clear to me if it is appropriate to translate the Blender UI words. While in the glossary they are useful to quickly understand the italian translation, in the other pages seems the least importan things to me. Take for instance the page about "Empties": is calling them "vuoti" really helping the reader/user? In my mind it seems more helpful to refer to them with the name they see in the UI. So I would have focus on the body, the instructions on how to use them, rather then the titles. But it's just my first thought, maybe it would took to much time to do everything this way. What's your opinion?
@Carlo Bergonzini (CarloB)
Hi and thanks to take care about manual.
Please make sure that the terms you will use in the manual are the same the Blender UI use.
I've translated the Glossary and a lot of titles (skipping the body of the text) for this reason, but the work is far to be completed, so, pay attention to the coherence and feel free to ask! ;)