[Development] PSA: Merging changes to qtqa and info about submodule integration license checking

2024-10-25 Thread Alexandru Croitor via Development
Hi, For a while now we had a slightly weird branching situation in qtqa, where we had a master and a dev branch, and it was a bit unclear what is used where. Here's a summary of latest changes regarding that situation. 1) Since a few months, qt submodule integrations (qtbase, qtsvg, etc) in t

Re: [Development] format-like tr()

2024-10-25 Thread Edward Welbourne via Development
David C. Partridge (25 October 2024 10:03) wrote: > While I applaud the thought of using std::format where appropriate, I > can't see what converting the existing tr() mechanism to that will > gain Qt Development or Qt Users This needn't be about Qt converting its translations to use std::format;

Re: [Development] format-like tr()

2024-10-25 Thread Ivan Solovev via Development
> Here's another one: formatting of floating point types. > > That's a hard pass on the Standard Library implementations. We already carry > code for this in the form of libdoubleconversion, so unless we can ditch that > in favour of the Standard Library content, we shouldn't use both, which would

Re: [Development] format-like tr()

2024-10-25 Thread Giuseppe D'Angelo via Development
Il 25/10/24 10:03, David C. Partridge ha scritto: While I applaud the thought of using std::format where appropriate, I can't see what converting the existing tr() mechanism to that will gain Qt Development or Qt Users One would be the compile-time check on the format strings and its replaceme

Re: [Development] format-like tr()

2024-10-25 Thread Giuseppe D'Angelo via Development
Il 24/10/24 19:04, Edward Welbourne ha scritto: Given that that does also substitute the relevant number into the string, I offer: tr("The apple(s) you bought cost %L1", n).arg(price); where the number controlling the singular/plural choice isn't inserted into the result, but something else

Re: [Development] format-like tr()

2024-10-25 Thread Ivan Solovev via Development
>> As for me, the standard really misses the customization points for standard >> formatters. But I still think that we should try to use what it provides, >> instead of inventing a completely custom implementation. > > Can you elaborate on what it misses? For example, for QBA(V) work I'd really l

Re: [Development] format-like tr()

2024-10-25 Thread Giuseppe D'Angelo via Development
Il 24/10/24 18:23, Thiago Macieira ha scritto: On Thursday 24 October 2024 05:19:45 Pacific Daylight Time Giuseppe D'Angelo via Development wrote: Btw, where does the “tr” go? Is it going to be tr(std::format(…)) or std::vformat(tr(…))? In the former, we’d have to pass the value twice (once for

Re: [Development] format-like tr()

2024-10-25 Thread David C. Partridge
While I applaud the thought of using std::format where appropriate, I can't see what converting the existing tr() mechanism to that will gain Qt Development or Qt Users David -Original Message- From: Development On Behalf Of Thiago Macieira Sent: 24 October 2024 18:13 To: development@

[Development] Deprecated vs deprecated-to-be-removed APIs in Qt

2024-10-25 Thread Ivan Solovev via Development
Hi, following up on the Deprecation vs Compatibility discussion from the Qt Contributor Summit [0], I implemented a macro that allows to mark the APIs as deprecated and to-be-removed in the Next Major Release [1]. [0]: https://wiki.qt.io/QtCS2024_Deprecate [1]: https://codereview.qt-project.org/

Re: [Development] format-like tr()

2024-10-25 Thread Thiago Macieira
On Thursday 24 October 2024 09:54:43 Pacific Daylight Time Giuseppe D'Angelo via Development wrote: > > This is what I'm more worried about: telling the string-extraction tools > > that don't really understand C++ that this is a string with plurals. I > > don't know if they need to: is it acceptab