Fri, Apr 20
Thu, Apr 19
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'
Mon, Apr 16
Sun, Apr 15
@Bastien Montagne (mont29) can you have a look here.
Sat, Apr 14
Fri, Apr 13
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! ;)
Tue, Apr 10
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.
Sat, Apr 7
Fri, Apr 6
Thu, Apr 5
Mon, Apr 2
Mar 22 2018
I will make sure to check.
Thanks for the reply @Aaron Carlisle (Blendify). I'll do my best.
I hope you'll have time to check if I'm committing the version files in the right way and not messing things up for at least the first commit.
Mar 21 2018
Hi @Carlo Bergonzini (CarloB), sorry for the late reply I have been sick/busy. Becuase there is not really a large number of people working on this having people review translations is not really possible.
Mar 18 2018
I'm an italian blender user and in my free time I would be happy to help in translating the manual.
It's first time I approach the subversions management problem, so I followed the steps descripted in the guide until I was able to get a copy of the translation on my pc and now I would like to have a feedback before taking any step further. As far as I understood I need to edit and save the .po and then commit them for administrator check, right? Am I missing something? How many files do you usually edit before committing?
Jan 31 2018
@blend-it (blend-it) thanks, done.
both a file type (I suppose, never found .iris filetype, 1 and 2) and eye part (3)
WipeSequence.transition_type:'IRIS' (3) must be separated, or filetype (1 and 2) removed from translated strings (a .jpg is a .jpg, an .iris is an .iris!).
Jan 18 2018
Color Balance Node
For the Lift/Gamma/Gain formula, Lift tooltip is the "Correction for Shadows" it’s OK.
But if switch to the Offset/Power/Slope formula, Offset tooltip is still the "Correction for Shadows", this is wrong.
Must be something like "Correction for entire tonal range".
Jan 11 2018
Jan 4 2018
Dec 7 2017
Please check on Blender French translation, a lot of those strings here are 'UI messages' (property names as they appear in the UI), those should reuse same translations as in the French UI. ;)
Dec 6 2017
@Bastien Montagne (mont29), can you check this patch? Thanks! :)
Nov 29 2017
Besides a few typos, main issue here is that you have to follow as close as possible UI translation in the Manual. ;)
Nov 22 2017
Nov 7 2017
Oct 2 2017
@Bastien Montagne (mont29) maybe you can shine some light on this?
Sep 28 2017
Sep 26 2017
Sep 19 2017
Sep 7 2017
Aug 29 2017
The further I'm working down the PO file, the more instances of 'Homonyms' I find. The word 'track' for instance, in case of Motion Tracking, it is already confusing in terms of mixing the meaning of the tracking markers (noun) and tracking action (verb), and then, on top of this, it also means differently as an NLA track in NLA editor. These translations are different in Vietnamese, at least. A typical example is here:
Jul 30 2017
Jul 29 2017
@Sv. Lockal (lockal) is our Russian translation maintainer afaik, so would rather let you guys get in touch to organize the work here?