So, I think I should abandon this change!
@qiancheng lin (lqc) Thank you for your participation. I'm happy to have another contributor for Chinese manual since we have been calling for more volunteers to help deal with the translation.
But, you're contributing in the wrong way. We translated the extracted .po files, not the original .rst files。More detail at this page, and another summarized version here.
And we have gathered a translation team for manual translation,(QQ group number: 620831153). Please consider to join us.
Thu, Jul 18
Mon, Jul 15
Sun, Jul 14
Sat, Jul 13
Please do not remove BF Blender from i18n tasks, this is part of it! ;)
Volume at Sidebar --> Adjust --> Sound panel Should be displayed as 音量 in Chinese, but it is 体积 (the amount of space that some entity contains or occupies).
I know there is a separate item for the loudness of sound in the .po file.
So I guess this "Volume" is just not in the right context. Could someone fix this?
Fri, Jul 12
Wed, Jul 10
All these was fixed on commit rBTS4963, so it could be closed.
Tue, Jul 9
Hi @shad (kennex), it sure is possible. :)
Thu, Jul 4
Wed, Jul 3
Issue happens because that info is often generated by worker threads (instead of main one used by UI code), and boost i18n code does not work well from threads (here it just return unstranslated string it'd seem).
A guideline for making a good bug report can be found here: https://wiki.blender.org/wiki/Process/Bug_Reports
Please use the bug submission form when reporting bugs, do not create custom tasks.
Sat, Jun 29
Thank you @Aaron Carlisle (Blendify), I found it.
You are not using a clip (clips are loaded from the movie clip editor)
Thu, Jun 27
You are already part of the project, so you can commit already, please coordinate with @Cheng Chia Tseng (zerng07) first though.
Tue, Jun 25
Am gonna do that for now, I really do not see how to make fstrings work nicely with translations currently…
We could avoid f-strings for text which needs to be translated if this complicates things too much.
Mon, Jun 24
@Campbell Barton (campbellbarton) this will generate an ast.JoinedStr (containing a list of regular ast.Str and ast.FormattedValue objects). Thing is, I don’t think we can properly translate this in any way, since bpy API will only get the already processed string, which obviously does not exist in translations…
We could try invoking explicitly the pgettext function there, but am pretty sure that would break the fstring too (as this has to be parsed together with the whole py code at load time)? And in any case, it would be super-ugly…
More like a missing update, we did not use those f-strings before… Guess I'll have to dust off my AST again to add support for those.
Jun 17 2019
@Bastien Montagne (mont29) Delete this patch,Please! and delete my account.Now,thanks you!
Jun 16 2019
@liveasx Stop removing people following the patch, that is another kind of useless rudeness. That is also your final warning, next time I’ll have to disable your account. We do not have time to deal further with that kind of behavior.