Re: [Development] QLocale work

2012-01-18 Thread andrew.den-exter
> 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 > > explicitl

Re: [Development] QLocale work

2012-01-18 Thread Thiago Macieira
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 oth

Re: [Development] QLocale work

2012-01-18 Thread Shaw Andy
On 1/18/12 2:21 PM, "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 >>settings.

Re: [Development] QString::toHtmlEscaped()

2012-01-18 Thread Robin Burchell
Hi, Thanks for following this up from Gerrit! On Wed, Jan 18, 2012 at 9:52 PM, 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 metacharacters for examp

Re: [Development] What's the story for Qt5 on Harmattan?

2012-01-18 Thread Thiago Macieira
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, P&S or location, The > > backends are very large and complex and hardly (if at all) used by any

Re: [Development] What's the story for Qt5 on Harmattan?

2012-01-18 Thread Simon Hausmann
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

Re: [Development] What's the story for Qt5 on Harmattan?

2012-01-18 Thread alex.blasche
> -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 no plan to support Qt5 in Harmattan, > > I believe the Harmattan-specific co

Re: [Development] QLocale work

2012-01-18 Thread lars.knoll
On 1/18/12 12:35 PM, "ext Thiago Macieira" 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 (System) locale. Anyth

Re: [Development] QLocale work

2012-01-18 Thread lars.knoll
On 1/18/12 1:42 AM, "ext 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 X 10.6 shi

Re: [Development] QLocale work

2012-01-18 Thread lars.knoll
On 1/18/12 1:40 AM, "ext John Layt" 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 Qt

Re: [Development] QLocale work

2012-01-18 Thread Stephen Kelly
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.

Re: [Development] QLocale work

2012-01-18 Thread Thiago Macieira
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 (System) locale. Anything in QtCore, outside of QLocale, should default to the C lo