Aug 17 2018
Aug 5 2018
I will see your changes. I also wait for 2.80 version because remove game engine and blender internal render.
Don't worry about it. I've learned how to create and compile for Vietnamese. Just needed to know how to check changes into the svn repository, that's all.
Just like to inform that I had completed all the verifications as of today and stop updating the GitHub repository of mine. Chau, you can check them in when you can. Would appreciate bits of help on how to start on the reference manual properly: ie. procedures for creating a branch for VI, compiling and updating changes. I had managed downloaded the source, including dependencies, and compiled locally for English.
Aug 3 2018
74. "Surface falloff (New)" -> "Surface" 75. "Every Point (New)" -> "Every Point"
Aug 2 2018
Jul 30 2018
Just need to update po files, didn’t do that since months… :/
But really, no point making a report for that. ;)
Jul 29 2018
UV Editor > Select menu > Select Split
Jul 28 2018
Fine with me. I don't mind. Let me know if I could be of help. By the way, I'm still updating to that repository of mine daily. So Chau will need to keep up with changes over there. God bless you all.
Jul 27 2018
Jul 24 2018
Thank you very much for the answer, Brecht. Appreciated. Cheers!
Did you mean 'to select' the part that has been 'Picked' by the mouse action, and they are 'linked', or what?
Jul 17 2018
Jul 12 2018
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.
Jul 10 2018
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").
Jul 9 2018
Jul 8 2018
Jun 26 2018
Jun 24 2018
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!