FEM translation strings that need inspection before 0.18 release

[Kunda1]

Hey bernd,
In the FEM translation section of crowdin: https://crowdin.com/translate/freecad/559/en-en (note this is english to english and I'm using it to review strings and monitor open crowdin issues about certain strings)

...there are several strings that need your inspection, orientation, and approval.

We want to have FEM at 100% approved translations

FEM-Crowdin-Progress.png (2.75 KiB) Viewed 2037 times

So, I've created a quick explanation of the UI for you JIC you need it

Explanation of the Crowdin translation web-UI

crowdin-translation-ui.png (237.5 KiB) Viewed 2037 times

What is needed is to review all the strings that have yet to be translated or that have been translated but need approval.
Some of the issues are grammatical like
'Solver CalculiX' (https://crowdin.com/translate/freecad/559/en-en#6500068) is there a reason you prefer 'Solver' before the solver name ?
There are a few issue like that.
Some issues like https://crowdin.com/translate/freecad/559/en-en#6500073 are issues with Crowdin itself that I have yet to solve (obsolete strings showing up as legit strings).

So would you mind logging in and approving what you can approve, explain what needs to be explained to translator discussions etc... ? Thanks in advance

[Kunda1]

@bernd care to respond ?

[bernd]

@bernd care to respond ?

sure, but just have very limited time ATM ...

https://t-ec.bstatic.com/images/hotel/m ... 093978.jpg
https://www.landalskilife.de/-/media/Im ... _69348.jpg

[Kunda1]

Hey mate, glad you're back. Care to take a look again?

[bernd]

ok started to have a look at this.

But change from "solver CalculiX" to "CalculiX solver" would have to be in source code not crowedin? Am I on the right track?

bernd

[Kunda1]

But change from "solver CalculiX" to "CalculiX solver" would have to be in source code not crowedin? Am I on the right track?

Yes, for changes to reflect in crowdin they need to be modified in the source code

[bernd]

means I should either change in source code or accept in crowedin?

[Kunda1]

means I should either change in source code or accept in crowedin?

Change is source code.
Crowdin: just notate in the crowdin UI discussion that it was changed. Please don't alter the incorrect strings in crowdin. Let them instead be imported in the next translation push from the source code.

[bernd]

Is it possible to recreate all context informations of crowdin? They are totally wrong in lots of cases. Sometimes there are four strings for just one string.

For example:
https://crowdin.com/translate/freecad/559/en-en#6499365
https://crowdin.com/translate/freecad/559/en-en#6499364
https://crowdin.com/translate/freecad/559/en-en#6500096
https://crowdin.com/translate/freecad/559/en-en#6500095

and all source code files the string refers to do no exist anymore since version 0.17 development cycle, means since a year.

bernd

[Kunda1]

Is it possible to recreate all context informations of crowdin? They are totally wrong in lots of cases. Sometimes there are four strings for just one string.

For example:
https://crowdin.com/translate/freecad/559/en-en#6499365
https://crowdin.com/translate/freecad/559/en-en#6499364
https://crowdin.com/translate/freecad/559/en-en#6500096
https://crowdin.com/translate/freecad/559/en-en#6500095

and all source code files the string refers to do no exist anymore since version 0.17 development cycle, means since a year.

bernd

2 issues here:

1) obsolete strings are still present in crowdin. Yorik and i have been tackling this but we're not quote finished yet.
2) changing the context information. I'm not 100% certain I understand. So I'll answer in a few ways:
A) You can change the context field to let users know more details about this string. You can even add a screenshot.

Crowdin-Edit-Context.png (53.94 KiB) Viewed 1706 times

B) Re: Sometimes there are four strings for just one string.
The way we have Crowdin setup now is if the translation strings are identical they get translated in bulk (this only works if the strings are identical). If there is a slight variation, they Crowdin will separate the string in to separate string to be translated. The examples you gave above vary therefore they are 4 different strings to translate. ( I may have misunderstood you, so I apologize if this answer is redundant or not relevant)