Remove fuzzy tags in translations from Qt to TQt conversion. #6

Open
opened 5 years ago by Chris · 6 comments
Chris commented 5 years ago
Collaborator

Just to track this.

While looking for branding in tdevelop, I found at least in German many, many TQt original (English) strings, which were renamed from Qt to TQt, as well in the translation (German for example). So original strings, as well as translated strings are in pair and good, but the translated strings are marked as fuzzy in the specific translation files.

For German I removed all fuzzy marks manually now, but for other languages someone need to do that too. Most likely with some script. In German 100% of the fuzzy marked strings (Qt to TQt specific) were fine and without any problems. Most likely that is for other languages too.

Just to track this. While looking for branding in tdevelop, I found at least in German many, many TQt original (English) strings, which were renamed from Qt to TQt, as well in the translation (German for example). So original strings, as well as translated strings are in pair and good, but the translated strings are marked as fuzzy in the specific translation files. For German I removed all fuzzy marks manually now, but for other languages someone need to do that too. Most likely with some script. In German 100% of the fuzzy marked strings (Qt to TQt specific) were fine and without any problems. Most likely that is for other languages too.
Owner

Chris, can you post the commit number related to this? It will be useful as a reference if we come around to remove the fuzzy marking by script.

Chris, can you post the commit number related to this? It will be useful as a reference if we come around to remove the fuzzy marking by script.
Chris commented 5 years ago
Poster
Collaborator

Michele, sadly I don't have any commit number about that changes. Most likely they were made in 2014 or so. Maybe I can find the commit later. We will see.

Michele, sadly I don't have any commit number about that changes. Most likely they were made in 2014 or so. Maybe I can find the commit later. We will see.
Owner

ah, I see. no worries.

ah, I see. no worries.
Chris commented 5 years ago
Poster
Collaborator

I took a look and found these two commits. From what I have seen, there were not any further commits related to that:

fae7d9ab5a
037beaf5ca

Seems the template file was not already changed to that time, what triggered some fuzzy markings. I might be wrong. Also sometimes the original string was changed, but no the strings in translations, from what I have seen in the German translation.

I took a look and found these two commits. From what I have seen, there were not any further commits related to that: https://mirror.git.trinitydesktop.org/gitea/TDE/tde-i18n/commit/fae7d9ab5a17fa4d2a6cecf6bd036f68d38dfb18 https://mirror.git.trinitydesktop.org/gitea/TDE/tde-i18n/commit/037beaf5cab4fda4ea0996e6ad44eb2a68f49197 Seems the template file was not already changed to that time, what triggered some fuzzy markings. I might be wrong. Also sometimes the original string was changed, but no the strings in translations, from what I have seen in the German translation.
Owner

Those commits don't affect translations, they are related to code only. But it's ok, don't worry looking for it

Those commits don't affect translations, they are related to code only. But it's ok, don't worry looking for it
Chris commented 5 years ago
Poster
Collaborator

Okay, just have seen this commits. Didn't check for that exactly. They were the only one. But you know what I mean.

Okay, just have seen this commits. Didn't check for that exactly. They were the only one. But you know what I mean.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: TDE/tdevelop#6
Loading…
There is no content yet.