On Wednesday, 16 January 2019 11:56:20 PST Lars Knoll wrote:
> In particular, I want to
> take a look to see how it can integrate with a project my team is working
> on:
> https://clearlinux.org/documentation/clear-linux/concepts/telemetry-about
>
> Why should that project influence a telemetry
On Wednesday, 16 January 2019 13:16:39 PST Konstantin Tokarev wrote:
> 1. Code points may be encoded as surrogate pairs in UTF-16, e.g. this is the
> case for Emoji characters. QString ignores this fact, indexing 16-bit
> QChars. To make things worse, several QString methods like left(), right(),
15.01.2019, 23:13, "Alexander Akulich" :
> Cristian,
>
> the previous discussion is "Why can't QString use UTF-8 internally?"
> There is something wrong with our maillist, the best link I found is
> [1]. For some reason link to the thread head [2] is broken.
>
> [1]
>
On Tue, Jan 15, 2019 at 10:44:45PM +0100, Allan Sandfeld Jensen wrote:
> On Dienstag, 15. Januar 2019 19:43:57 CET Cristian Adam wrote:
> > Hi,
> >
> > With every Qt release we see how the new release improved over previous
> > releases in terms of speed, memory consumption, etc.
> >
> > Any
On 16 Jan 2019, at 19:54, Thiago Macieira
mailto:thiago.macie...@intel.com>> wrote:
On Wednesday, 16 January 2019 09:44:40 PST Aleksey Kontsevich wrote:
In Nov, there was long discussion in review:
https://codereview.qt-project.org/#/c/240347/ Request was initially for
both: plugin and library -
> Sent: Tuesday, January 15, 2019 at 4:44 PM
> From: "Allan Sandfeld Jensen"
> To: development@qt-project.org
> Subject: Re: [Development] Qt6: Adding UTF-8 storage support to QString
>
> On Dienstag, 15. Januar 2019 19:43:57 CET Cristian Adam wrote:
> > Hi,
> >
> > With every Qt release we see
On Wednesday, 16 January 2019 10:44:27 PST Konstantin Tokarev wrote:
> From QtWebKit perpective it would be great if Qt APIs which require QString
> now would also accept QLatin1String at least for ASCII-only data
Which ones? Currently, the only thing that takes QLatin1String in the API is
15.01.2019, 21:45, "Cristian Adam" :
> Hi,
>
> With every Qt release we see how the new release improved over previous
> releases in terms of speed, memory consumption, etc.
>
> Any chance of having UTF-8 storage support for QString?
>
> UTF-8 is native on Linux and other *NIX platforms, Qt
16.01.2019, 00:46, "Allan Sandfeld Jensen" :
> On Dienstag, 15. Januar 2019 19:43:57 CET Cristian Adam wrote:
>> Hi,
>>
>> With every Qt release we see how the new release improved over previous
>> releases in terms of speed, memory consumption, etc.
>>
>> Any chance of having UTF-8 storage
Marco Bubke (16 January 2019 10:59) reported:
>> https://utf8everywhere.org/ states "UTF-16 is the worst of both
>> worlds, being both variable length and too wide"
Konstantin Ritt (16 January 2019 17:50) replied
> https://utf8everywhere.org/ states bullshit. try reading an alternative
>
On Wednesday, 16 January 2019 09:44:40 PST Aleksey Kontsevich wrote:
> In Nov, there was long discussion in review:
> https://codereview.qt-project.org/#/c/240347/ Request was initially for
> both: plugin and library - latter was transformed to Qt module.
Given that this is a complete surprise, I
In Nov, there was long discussion in review:
https://codereview.qt-project.org/#/c/240347/ Request was initially for both:
plugin and library - latter was transformed to Qt module.
--
Best regards,
Aleksey
Linked in https://www.linkedin.com/in/alekseykontsevich
16.01.2019, 19:28, "Thiago
On Monday, 14 January 2019 09:50:23 PST Aleksey Kontsevich wrote:
> Whether Qt Telemetry module will be included:
> https://codereview.qt-project.org/gitweb?p=playground%2Ftelemetry.git;a=summ
> ary ?
When did this become a Qt module?
The only email with "telemetry" in the past 10 months was a
> https://utf8everywhere.org/ states *"UTF-16 is the worst of both worlds,
being both variable length and too wide"*
https://utf8everywhere.org/ *states bullshit. try reading an alternative
sources.*
Regards,
Konstantin
ср, 16 янв. 2019 г. в 13:20, Edward Welbourne :
> Marco Bubke (16
Hi,
The API is relatively simple, so reviewing and fixing the findings should not
be a problem. As this is a new module, would definitely be good to do an
initial API review now / before alpha. We probably anyway want to include it
first as a TP, so its API is not yet fixed/final even with Qt
> On 16 Jan 2019, at 10:08, Lars Knoll wrote:
>
>> On 16 Jan 2019, at 09:47, Alex Blasche wrote:
>>
>>> From: Development on behalf of Lars
>>> Knoll
>>> For now I’d like to limit this to qtbase, as that’s where pretty much all
>>> Qt 6 related work happens,
>>> and we need to do some
Marco Bubke (16 January 2019 10:59)
> You can use std::string which as small string optimization instead of
> QByteArray too. In many cases where you would use const String
> you can use std::string_view, so you are more flexible.
Note that we now have a QStringView, which can likewise replace
You can use std::string which as small string optimization instead of
QByteArray too. In many cases where you would use const String you can use
std::string_view, so you are more flexible.
From: Development on behalf of Allan
Sandfeld Jensen
Sent: Tuesday,
> On 16 Jan 2019, at 09:47, Alex Blasche wrote:
>
>> From: Development on behalf of Lars
>> Knoll
>> For now I’d like to limit this to qtbase, as that’s where pretty much all Qt
>> 6 related work happens,
>> and we need to do some work on the CI side to prepare the other modules for
>> Qt 6
19 matches
Mail list logo
