PyQt6 and SIP v6 Snapshots Available

[Detlev Offenbach]

Hello Phil,

thanks for fulfilling all my wishes with respect to pylupdate6.

Regards,
Detlev

Am 16.12.20 um 17:06 schrieb Phil Thompson:
> On 27/10/2020 19:04, Detlev Offenbach wrote:
>> Am 27.10.20 um 18:30 schrieb Phil Thompson:
>>> On 27/10/2020 17:08, Detlev Offenbach wrote:
>>>> Hello Phil,
>>>>
>>>> now that pylupdate6 supports reading of .ui files I looked at the code
>>>> again and got a question. Will pylupdate6 keep obsolete translations
>>>> in the .ts file or will it throw them away. Optimally there will be a
>>>> command line switch allowing it to keep obsolete translations or
>>>> delete them (like the pylupdate5 -noobsolete). Obsolete, untranslated
>>>> messages should always be deleted (like pylupdate5 does it).
>>>
>>> At the moment it doesn't throw anything away because an existing .ts 
>>> is updated rather than re-created.
>>>
>>> As a monoglot, I've never used pylupdate so I don't have an 
>>> understanding of how it is really used. Let me know the specific 
>>> behaviour you want and I'll implement it.
>>
>> I am using pylupdate on a regular basis for the eric-ide development.
>> Here is my wishlist.
>>
>> Default behavior should be to not throw away any messages. However, no
>> longer used messages should be marked as obsolete. I think the .ts XML
>> schema contains an attribute for this.
>> <translation type="obsolete">...</translation>
>>
>> If called with a '--no-obsolete' flag, it should delete all messages
>> no longer needed, i.e. marked with the  "obsolete" marker.
>> Note: --no-obsolete is the modified command line flag used in lupdate 
>> of Qt6.
>>
>> In both cases obsolete, untranslated messages should be removed.
>
> Done.
>
>>>> Will pylupdate6 eventually contain some heuristics like pylupdate5 to
>>>> already provide translations for identical strings but different
>>>> contexts?
>>>
>>> So when it sees a string in a new context it automatically gives it 
>>> an existing translation it if finds one?
>> Correct. This saves the translator some time. These should be marked 
>> with
>> <translation type="unfinished">...</translation>
>
> Done.
>
>>>> It would be great as well, if pylupdate6 would give a summary when
>>>> done like pylupdate5 (e.g. total no. of messages, no. of new messages,
>>>> no. of already translated messages, no. of messages provided by
>>>> heuristic, no. of obsolete messages).
>>>
>>> Ok - when used with the --verbose flag.
>> That would be ok. However, I would like to have a '--no-progress'
>> switch available to disable all the progress messages contained in the
>> code right now.
>
> The progress messages are only displayed with --verbose.
>
> The summary is displayed by default and may be suppressed by using 
> --no-summary.
>
> These will all be in the next snapshot.
>
> Phil

-- 
Detlev Offenbach
detlev at die-offenbachs.de