That’s more a UI code design issue than a Translations one really…

In T68588#752075, @Bastien Montagne (mont29) wrote:

Note that you cannot really get rid of the svn repo for Blender UI translations, as those stored in GIT are fully stripped to be as small as possible, they are essentially useless as working translation material...

What is the reason for this? Is this to reduce the size of the generated Machine Object files? If so cant this be consider a part of the build process?

Again people using new syntax in py strings... sigh

Hi @Jens Arnold (j.a-b) I added you to the Documentation project so you now have commit access. Please commit this changes and any others directly to SVN. The user name and password are synced with this website.

Hi @Jens Arnold (j.a-b) I added you to the Documentation project so you now have commit access. Please commit this changes and any others directly to SVN. The user name and password are synced with this website.

Cut: divide on 2 parts (sequencer)/ delete and copy (text)

user registration - possible to use phabricator user database? Or some other way to keep these in sync?

I'm closing all these translation reviews, which I believe have been committed.

This one appears to have been committed, so closing.

In T68588#752509, @Aaron Carlisle (Blendify) wrote:

[..] translation review [..]

In my opinion, there are three requirements for new translators:

In a discussion with @zdy (NGENNGT) in #docs on blender.chat one issue with the manual translations is the lack of quality of translations due to translators need to know proper RST formatting to translate po files.
Because moving to such a system that is online, translators will not be building docs locally and there is concern that the amount of formatting errors would increase.

@Gabriel Gazzán (gab3d) Thank you for the response, part of my goal here is to get feedback from current translators.

Note that you cannot really get rid of the svn repo for Blender UI translations, as those stored in GIT are fully stripped to be as small as possible, they are essentially useless as working translation material...

What's the scope of this? Everything on the blender.org domain (store, cloud, dev wiki, ect...), something in between or just the Blender UI and Manual (for now)?

Hi @Aaron Carlisle (Blendify) ,
I'm the translator of the UI into Spanish (one of the few languages that has been consistently maintained throughout these years), I've handed it alone since 2011, and a couple of times people tried to jump onboard to help, but unfortunately they ultimately never did any significant contribution, for different reasons I think.
I understand what you are looking for with these changes, and it could be a good thing, if done properly.

And there is another point. This operator info-bar already translated as tooltips:

In T68407#748501, @Philipp Oeser (lichtwerk) wrote:

In blender, these dont count as tooltips [these are the ones showing when hovering over tools, properties...]

Yes, i know that is tooltips mean in blender, but in terms of meaning, these are also tooltips. The division of interface/tooltips is very old, maybe it's time to review this?

In blender, these dont count as tooltips [these are the ones showing when hovering over tools, properties...]

Downloaded latest daily build cdeda1fa6cea. Tools at Toolbar remains English.

SInce I've committed alll changes in rBMT3790, so I'll abandon it to close it.

Volume meaning either: 'volume of some 3D entity' or 'volumetrics, in general' (or 'sound volume' which I know is already independent).

translate "build" to "编译".

I have patched the updated revision. All the warnings are fixed now. Further review will be finished later.
I know you probably don't want to join us. But since we're working on the translation at the same time, we still need to be aligned to avoid overlapping and conflicts.
I think we need a talk. QQ or blender.chat?

I am sorry to let you do what I should do.

I've patched you revision locally, and built again. Let alone some inconsistent words with the user interface. There are 100 warning after building, screenshot as below:

@Yizhong Zhang (bee) Thank you for your translation and correction.
We have gathered a translation team to deal with the manual translation. I think we need your help now to help translate and improve the manual.
A QQ group will make communication more effectively, and our group number is 620831153.
Or how can I get touch with you?

@zdy (NGENNGT) it's not yet committed, you'd need to apply the patch and build yourself.

@Bastien Montagne (mont29) Thank you. Can I test this change in today's daily build?

Ah, that makes sense. I was unable to actually find a place outside of the thread where that would be done. LOL. I'm sure to learn something from the eventual solution.

Translation was disabled from non-main threads at some point last year iirc, because on some systems (think it was mainly OSX), that could lead to crashes…

Since you're given commit access, so I'll abandon this. You can commit it yourself.

Since you're given commit access, so I'll abandon this. You can commit it yourself.

Since you're given commit access, so I'll abandon this. You can commit it yourself.

Since you're given commit access, so I'll abandon this. You can commit it yourself.

Since you're given commit access, so I'll abandon this. You can commit it yourself.

Since you're given commit access, so I'll abandon this. You can commit it yourself.

Since you're given commit access, so I'll abandon this. You can commit it yourself.

Just checked this with 2.80RC3, but has the same problem, never showing translated preview font text.

Yes, there definitely will. I'm just not the best person to say exactly how or when. I do see your error and I understand why it is happening. But I am not familiar with the issues around this "thread safety" issue regarding our font library.

Will it be possible to find a balanced way to deal with these two needs?

And to follow up, I definitely don't get a translated font preview for the Japanese language currently:

So, this was an an unintentional positive outcome?
But it has been and will be a handy feature for us users. It will be great for us to have it back.
Would it be possible to find it back?

Those strings are all meant to be translated. I see them marked as such:

Reviewed and accepted

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.

@Bastien Montagne (mont29)
I've found the "Cycles" string used for the render engine name is still used as the name of the Cycles F-Modifier, displayed in the UI when you add one of those.

@zdy (NGENNGT) what would be the point/usage for such a setting?

I'm fine with this being added on the UI module page.

Will Text object language support be possible?

I know that this is not a high-priority task, but still think we should consider it at some point. It would also be nice to be able to refer to it when closing related bug reports we keep getting (like lastest one, T67438: Error Font), and as a basis if someone volunteers to work on it. Might even make a nice GSoC project?

Good. Reviewed and accepted.

这回应该没问题了

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.

Hello everybody,