On Wednesday, January 18, 2012 00:42:26 John Layt wrote:
Splitting up some related issues into separate emails to make it easier for
people to address.
Which ICU version to use?
The latest ICU version is 4.8. See See http://site.icu-project.org/download
for detailed release notes.
OS
On 1/18/12 1:40 AM, ext John Layt jl...@kde.org wrote:
On Monday 16 Jan 2012 23:13:39 Thiago Macieira wrote:
I'd say that QLocale should return the information you need. If you
need to
display that, why shouldn't QLocale provide that info?
*Setting* the info is, however, out-of-scope for
On 1/18/12 1:42 AM, ext John Layt jl...@kde.org wrote:
Splitting up some related issues into separate emails to make it easier
for
people to address.
Which ICU version to use?
The latest ICU version is 4.8. See See
http://site.icu-project.org/download
for detailed release notes.
OS X 10.6
On 1/18/12 12:35 PM, ext Thiago Macieira thiago.macie...@intel.com
wrote:
On Wednesday, 18 de January de 2012 00.47.31, John Layt wrote:
* QString will need a decision on the behaviour of toInt() / toLong() /
etc
using the Default Locale.
They should use the C locale, not the Default
On Wednesday, January 18, 2012 01:41:57 PM ext alex.blas...@nokia.com wrote:
-Original Message-
From: development-bounces+alex.blasche=nokia@qt-project.org
On Thursday, January 12, 2012 06:50:58 AM ext xizhi@nokia.com wrote:
Hi,
Practically, since Qt Project has
On Wednesday, 18 de January de 2012 14.52.40, Simon Hausmann wrote:
I believe this is a view colored by qtbase/qtdeclarative/webkit only. The
picture is very different for networking, systeminfo, PS or location, The
backends are very large and complex and hardly (if at all) used by any
Hi,
Thanks for following this up from Gerrit!
On Wed, Jan 18, 2012 at 9:52 PM, kranthi.kumar-kunt...@nokia.com wrote:
I was looking at toHtmlEscaped() method in QString class which converts
metacharacters , , , and replaced by HTML entities.
is there any other method which can replace other
On 1/18/12 2:21 PM, lars.kn...@nokia.com lars.kn...@nokia.com wrote:
We need to avoid the problem of printf / scanf that use different decimal
conventions depending on the user locale. That means the naive
implementation
will be unable to parse the data it generated under a different locale
On Wednesday, 18 de January de 2012 21.24.36, Shaw Andy wrote:
For what it is worth I also agree that it should be changed, having
recently having to deal with the QDoubleValidator problem when it came to
this became a right pain so making it only use the C locale unless
explicitly told
On Wednesday, 18 de January de 2012 21.24.36, Shaw Andy wrote:
For what it is worth I also agree that it should be changed, having
recently having to deal with the QDoubleValidator problem when it came
to this became a right pain so making it only use the C locale unless
explicitly told
10 matches
Mail list logo
