@Campbell Barton (campbellbarton) I have a .blend file in this issue that make it really easy to reproduce: T58849

Can't redo, 234c1129715a022b5ff95ed3dcd8e275e3661f8c

Archiving then.

I will leave open for a bit longer.

hmmm, it's easiest to monitoring only this task for new posts, instead of checking always all if there are question about this translation...
I will prefer if this one can stay open.

bpy.types.MocapConstraint.s_frame Comes from an addon so not much we can do here. We can make color_saturation into its own context, but you will have to get the add-on developer to change bpy.types.MocapConstraint.s_frame

I am going to close this, if there are questions on translations these can be on a new task.

Jesus, this has been totally lost… @Kee Hoon Seong (Cyrus3DJ) still interested? ;)

I'm not sure what the solution is here. The socket names will be the layer names written into multilayer images. If we change the actual layer names to the file, then some external software will not be able to read it. If we only translate them for the UI, it's misleading.

Ok, added you to the project, please also read doc linked on Translations , and check coordination with @Cheng Chia Tseng (zerng07), who has been working on it already.

I want to translate Blender's UI to Chinese (Taiwan).

Need at least a few lines about what you want to translate, in which language, etc…

@Yi-Jyun Pan (pan93412) : I guess you want to join?, afaik, only Administrators can make you a member.
Would kindly ask @Bastien Montagne (mont29) to have a look...

No response, closing

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.

source/blender/makesrna/intern/rna_object_force.c

74.  "Surface falloff (New)" -> "Surface"
75.  "Every Point (New)" -> "Every Point"

Just need to update po files, didn’t do that since months… :/
But really, no point making a report for that. ;)

UV Editor > Select menu > Select Split

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.

Thanks @Hoang Duy Tran (hoangduytran), @Chau (BlenderNavi) is maintainer of Vietnamese translation, let’s him handle that. :)

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?

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.

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").

@Yevgeny Makarov (jenkm) committed rBecb56eac57e66c1c925860e05438c9f245bff505

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).

Checker Deselect

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."

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?

@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! :)

Done :)

Hi Bastien, not sure how to add someone to Translations?
Could you do?

Hi and thx for the help on translations!

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'

@andrea franco (andrea96) I added you to the Documentation project so you can commit these changes if you want.
We currently don't review changes for translations (takes to much effort).

@Nicolas (Seregone) I added you to the Documentation project so you can commit these changes if you want.
We currently don't review changes for translations (takes to much effort).

@Bastien Montagne (mont29) can you have a look here.

In T42765#493414, @Carlo Bergonzini (CarloB) wrote:

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?

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! ;)

Your MO (or PO) file must be broken somehow, you have to check on messages from gettext tools when you build it. But am afraid we cannot help further here, that is not a blender bug.

This is something that should be done by the addon's author (@Campbell Barton (campbellbarton) ;) ). Not a bug at all though, mere TODO, but will let him handle the report fro; here.