HEADS UP: Thanks to all who voted in the 1st round. We got a feature implemented! You should now have 3 more votes again. Please use them on the remaining features below. Thank you!
FreeCAD uses a 3rd party translation service called Crowdin to crowd-source translation work for the project.
Currently there is a feature requests the community can vote on to that give the crowdin devs a sense of what is popular and in demand. If we vote as a community on a specific feature we could influence the crowdin devs to implement said feature. So...here are some features IMO think would be helpful making translating FC more efficient:
Many people on our crowdin project complain that they cant find where a certain string is located in the code... Our .ts files contain the file & line number, but this is apparently not used on crowdin, but i didn't find that issue in the list.
In any case, most complaints i get is from people who don't understand the exact meaning of a sentence. This is normal I think, many of the sentences that appear in the FreeCAD UI only make sense in a CAD context, and when they are pulled out of it, it's hard to make sure of what they mean.
Maybe that could be more an effort from our part, to go to crowdin and write better explanations where people are asking (there is always a comments section where additional info can be written)
Many people on our crowdin project complain that they cant find where a certain string is located in the code... Our .ts files contain the file & line number, but this is apparently not used on crowdin, but i didn't find that issue in the list.
I wonder if people will really understand better if they knew the exact line or file. Besides this they can use the context string and search with that in the source code. It's maybe not very convenient but this way you can find everything you need.
In any case, most complaints i get is from people who don't understand the exact meaning of a sentence. This is normal I think, many of the sentences that appear in the FreeCAD UI only make sense in a CAD context, and when they are pulled out of it, it's hard to make sure of what they mean.
yorik wrote:Many people on our crowdin project complain that they cant find where a certain string is located in the code... Our .ts files contain the file & line number, but this is apparently not used on crowdin, but i didn't find that issue in the list.
Actually, they do have that feature. I don't think we are creating our .ts files correctly. Example in the code
We shouldn't be adding + or - to line numbers like: line="+97"
yorik wrote:In any case, most complaints i get is from people who don't understand the exact meaning of a sentence. This is normal I think, many of the sentences that appear in the FreeCAD UI only make sense in a CAD context, and when they are pulled out of it, it's hard to make sure of what they mean.
Maybe that could be more an effort from our part, to go to crowdin and write better explanations where people are asking (there is always a comments section where additional info can be written)
yorik wrote:In any case, most complaints i get is from people who don't understand the exact meaning of a sentence. This is normal I think, many of the sentences that appear in the FreeCAD UI only make sense in a CAD context, and when they are pulled out of it, it's hard to make sure of what they mean.
Actually, they do have that feature. I don't think we are creating our .ts files correctly.
We don't create these files manually but use Qt stuff for it. And no, it's correct this way because the + indicates that the line numbers are relative. Sometimes there are also negative line numbers.
Kunda1 wrote:Actually, they do have that feature. I don't think we are creating our .ts files correctly.
We don't create these files manually but use Qt stuff for it. And no, it's correct this way because the + indicates that the line numbers are relative. Sometimes there are also negative line numbers.
EDIT: My mistake. I am somewhat used to Transifex who's interface and functionality is more sophisticated then Crowdin's. At this time Crowdin does not have the feature of displaying filename and line number. We need to vote for this feature exactly for the above reasons: Add to context source file info for .ts files
I'm still under the impression that using relative line numbers is not future friendly. Can we reconsider this?
Last edited by Kunda1 on Fri Feb 10, 2017 4:22 pm, edited 2 times in total.
Actually, they do have that feature. I don't think we are creating our .ts files correctly.
We don't create these files manually but use Qt stuff for it. And no, it's correct this way because the + indicates that the line numbers are relative. Sometimes there are also negative line numbers.
Sorry for reposting, I wanted to make sure this is seen since I wanted to own up to my mistake. I am somewhat used to Transifex who's interface and functionality is more sophisticated then Crowdin's. At this time Crowdin does not have the feature of displaying filename and line number. We need to vote for this feature exactly for the above reasons: Add to context source file info for .ts files
I'm still under the impression that using relative line numbers iin translations are not future friendly. Can we reconsider this?
wmayer wrote:Qt allows it to add a special remark to the source code which will be picked up by lupdate: http://doc.qt.io/qt-5/i18n-source-trans ... r-comments
The next question is if crowdin supports this method.
I don't think so, but this is useful to know anyway.. Maybe in the future they will.
Kunda1 wrote:Can we reconsider this?
As Werner said, we don't do that manually nor intentionally. It's generated automatically by Qt. If Qt has a way to do it another way, certainly we can use that instead.