On sábado, 7 de setembro de 2013 20:34:20, Kurt Pattyn wrote:
> to my (limited) knowledge, I only know of the existence of
> qtbase/src/corelib/codecs/qutfcodec.cpp. Could you indicate where the other
> copies are?
qurlrecode.cpp
qjsonparser.cpp
qxmlstream.cpp
--
Thiago Macieira - thiago.macieir
A bug or not a bug, that's the question
> Date: 5 Sep 2013 17:35:49 GMT+02:00
> To: development@qt-project.org
>
>
> On quinta-feira, 5 de setembro de 2013 13:46:19, Kurt Pattyn wrote:
>> Is it OK then to remove the check in QUtf8Codec, or do we need a check on
>> t
On quinta-feira, 5 de setembro de 2013 13:46:19, Kurt Pattyn wrote:
> Is it OK then to remove the check in QUtf8Codec, or do we need a check on
> the DBus version (which is not relevant for other platforms than Linux),
> and depending on the version include/exclude the check?
Yes, it's ok to remov
05.09.2013, 15:46, "Kurt Pattyn" :
>> From: Thiago Macieira
>> Subject: Re: [Development] A bug or not a bug, that's the question
>> Date: 26 Aug 2013 17:16:19 GMT+02:00
>> To: development@qt-project.org
>> On segunda-feira, 26 de agosto de 20
> From: Thiago Macieira
> Subject: Re: [Development] A bug or not a bug, that's the question
> Date: 26 Aug 2013 17:16:19 GMT+02:00
> To: development@qt-project.org
> On segunda-feira, 26 de agosto de 2013 13:53:38, Kurt Pattyn wrote:
> We should remove the check. It was
On segunda-feira, 26 de agosto de 2013 13:53:38, Kurt Pattyn wrote:
> So, my question is now: should we consider this as a bug, and thus file a
> bug request in Jira, or can we live with it? Note that solving this issue
> could have an effect an QString as well, as it needs to handle those
> non-ch
On Monday 26 August 2013 14:39:50 Kurt Pattyn wrote:
> On 26 Aug 2013, at 14:26, Christoph Feck
wrote:
> > What do you mean with "maintained as is"? The document you cite
> > does not mention anything related to invalid UTF-8.
>
> Unicode strictly requires no loss of information when going betwe
On 26 Aug 2013, at 14:26, Christoph Feck wrote:
> What do you mean with "maintained as is"? The document you cite does
> not mention anything related to invalid UTF-8.
Unicode strictly requires no loss of information when going between the
different representations.
Currently the QTextCodec c
On Monday 26 August 2013 13:53:38 Kurt Pattyn wrote:
> QTextCodec *codec = QTextCodec::codecForName("UTF-8")
> codec->toUnicode(someUtf8StringContainingNonCharacters, …);
>
> When toUnicode is called with a string containing Unicode
> non-character codes, QTextCodec returns a conversion error.
> [
Hi,
when implementing web sockets, I encountered a problem with the QTextCodec
class.
This is a code snippet:
QTextCodec *codec = QTextCodec::codecForName("UTF-8")
codec->toUnicode(someUtf8StringContainingNonCharacters, …);
When toUnicode is called with a string containing Unicode non-character
10 matches
Mail list logo