On Wednesday, 22 March 2023 09:48:05 HST Volker Hilsheimer via Development
wrote:
> Even if one Qt 5 application and one Qt 6 application exchange data over a
> local socket, unwisely using to/fromLocal8Bit for the purpose - if the Qt 5
> application continues to run with the system code page, the
Am 22.03.2023 um 20:48 schrieb Volker Hilsheimer:
Indeed, the many hits in the sql code are mostly from warning output, thanks
for checking.
But that Postgres supports UTF-8 doesn’t mean that an existing server is also
configured to use it. If a server is configured to work with e.g. ISO_8859_
> On 22 Mar 2023, at 18:58, Christian Ehrlicher wrote:
>
> Am 22.03.2023 um 17:35 schrieb Volker Hilsheimer via Development:
>> But we use toLocal8Bit in plenty of cases as well. For instance in our Qt
>> SQL APIs.
>
> The only plugin which really uses toLocal8Bit() is the IBase - Plugin.
>
Am 22.03.2023 um 18:58 schrieb Christian Ehrlicher:
Am 22.03.2023 um 17:35 schrieb Volker Hilsheimer via Development:
But we use toLocal8Bit in plenty of cases as well. For instance in
our Qt SQL APIs.
The only plugin which really uses toLocal8Bit() is the IBase - Plugin.
Correction: it's
Am 22.03.2023 um 17:35 schrieb Volker Hilsheimer via Development:
But we use toLocal8Bit in plenty of cases as well. For instance in our Qt SQL
APIs.
The only plugin which really uses toLocal8Bit() is the IBase - Plugin.
Postgres is using it as fallback but according the docs the utf-8
encod
On Wednesday, 22 March 2023 01:07:12 HST Alvin Wong via Development wrote:
> In reality, most of the debug messages are ASCII, so this issue rarely
> affects anything and I consider it just "a mild annoyance".
And also a Not Out Bug issue.
First, the debuggers should opt in to UTF-16 support, if
> On 22 Mar 2023, at 12:07, Alvin Wong via Development
> wrote:
> On 22/3/2023 17:58, Lars Knoll wrote:
>> Hi,
>>
>>
>>> On 21 Mar 2023, at 17:46, Alvin Wong via Development
>>> wrote:
>>>
>>> Hi,
>>>
>>> Yes, embedding the manifest with activeCodePage set to UTF-8 is the only
>>> thing ne
Hi,
I’ve looked into that one when we did the work for Qt 6. The console has its
own code page that can be set independently from the app, and I believe also
independently from the system code page. qDebug() should be mostly fine, as
we’re using OutputDebugStringW() internally and let Windows
Hi,
> On 21 Mar 2023, at 17:46, Alvin Wong via Development
> wrote:
>
> Hi,
>
> Yes, embedding the manifest with activeCodePage set to UTF-8 is the only
> thing need to enable UTF-8 as the ANSI code page (ACP) for the process.
>
> Qt itself should work fine after the bug in QStringConverter
