[Localization] Unfinished strings with translations

[scootergrisen]

Den 04-07-2018 kl. 17:17 skrev Oswald Buddenhagen:
> On Wed, Jul 04, 2018 at 12:05:03AM +0200, scootergrisen wrote:
>> It seems each time i update Qt translations to new version there are
>> lots of strings with type unfinished containing translations.
>>
>> Like i guess the strings have just been move in the source code but i
>> think the source string and the translation string should be just the
>> same as before so i use time on approving strings that i dont think
>> should be nessasary.
>>
>> I'm i right in this or not?
>>
> dunno, you'd have to pick a specific example to verify.
> i suspect they moved to a different context. in most cases such a change
> is indeed trivial.
> _______________________________________________
> Localization mailing list
> Localization at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/localization
> 

One example when updating Qt Creator 4.6 to 4.7:

<context>
     <name>QmlProfiler::QmlProfilerModelManager</name>
     <message>
         <source>Saving Trace Data</source>
         <translation type="vanished">Gemmer spordata</translation>
     </message>

<context>
     <name>QmlProfiler::Internal::QmlProfilerTool</name>
     <message>
         <location line="+161"/>
         <source>Saving Trace Data</source>
         <translation type="unfinished">Gemmer spordata</translation>
     </message>

It just seems like the string have been moved but remains the same.
So i would not think adding type="unfinished" could be nessasary.
It just makes translators have to check something that they have already 
checked.