[Development] ICU decision?

[guillaume.belz at free.fr]

Hello,
Since Qt 5, a criticism that I often see is the number of libs to deploy and its size. ICU is 26.4 Mb (windows mingw) while basic Qt libs are much less (core+gui+widgets+qml+quick = 19.6 Mb for example). On embedded, the extra cost will be even more critical (and criticable)
I think the third solution (with "fake" light ICU) is a solution for the size of the libs. A third-bis solution would be to have a fake-light-ICU included statically in Qt Core if necessary, to the problem of many libs.
Thank
Guillaume Belz

----- Mail original -----
> De: "Knoll Lars" <Lars.Knoll at digia.com>
> À: "Thiago Macieira" <thiago.macieira at intel.com>, development at qt-project.org
> Envoyé: Mercredi 7 Août 2013 10:00:27
> Objet: Re: [Development] ICU decision?
> 
> On 07.08.13 01:37, "Thiago Macieira" <thiago.macieira at intel.com>
> wrote:
> 
> >On quarta-feira, 7 de agosto de 2013 00:22:59, John Layt wrote:
> >> The  question really then is how to expose the advanced features
> >> from
> >>an
> >> optional ICU:
> >> * Separate module
> >
> >That's fallback.
> >
> >> * In QtCore, but classes only available on Win32 if ICU used
> >
> >That's out of the question.
> 
> Yes, that's no good solution.
> >
> >> * In QtCore, but with a Win32 backend that has a degraded
> >> experience if
> >>ICU
> >> not used
> >
> >The only "degraded experience" I would accept is "full functionality
> >for
> >C and
> >system locales". It would be acceptable for the classes to not have
> >any
> >support for other locales, like trying to get number formatting for
> >Azerbaijani on a German Windows.
> 
> That would be acceptable for now IMO.
> 
> The third option we discussed:
> 
> * Require ICU, but have a 'fake' ICU lib available to deploy with Qt
> on
> Windows/Android for those who want to ship with minimal i18n support.
> Add
> some support to our packaging to choose which ICU lib to take.
> 
> Long term, I think I'd prefer the 3rd option.
> 
> Cheers,
> Lars
> 
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>