While translating the new strings for 2.81 I've found that the string "Parents" (used for "main" particles) is now also wrongly used for one of the new "Affect Only" options (Origins/Locations/Parents) of the transform tools toolbar.
Please, that should remain as a separate string.

The only reason is to help do the changes I described but if you would like to stay on top of things instead that works too.

Spaces: Space (keyboard key, character) / Space (area, workspace)

@Artyom Sobolev (Woolpit) , I've added you to transifex, welcome!

Thank you, Michael!

Hello, @Artyom Sobolev (Woolpit) ! We now use transifex for translations

I’d rather stay in charge of translation project, including which languages we keep or not… If es and es_ES are identical, then indeed the later should have been removed for a long time.

es and es_ES are identical, I propose we remove es_ES

Somethings I noticed while testing UI translations:

@Bastien Montagne (mont29) Can I get added to Translations ?

I created two patches; one for the blender source and the other for the add-on to remove mo files from the translations repository.

Because we want the git repo (which has to be checked out by everybody that wants to build Blender) to be as small as possible. And a tremendous amount of changes in PO files, from week to week, are actually in the 'source' comments (line number changes). those info are mandatory for translation work, but useless if you only want to generate the MOs binaries...

After my previous edit the /about/-files seem to have disappeared. I uploaded them again:

Added translation to DE of "editing.po" , "index.po" and "patch_commit.po" in blender_docs\locale\de\LC_MESSAGES\about\contribute.

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' name 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:

@ZYZ (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