Porting KLocale::formatMoney()/readMoney() to Qt5/KF5, best practise?

Friedrich W. H. Kossebau kossebau at kde.org
Sun Jan 31 21:25:28 GMT 2016


Hi John,

Am Donnerstag, 7. Januar 2016, 05:18:42 schrieb Friedrich W. H. Kossebau:
> Am Mittwoch, 6. Januar 2016, 10:07:55 schrieb John Layt:
> > To save you some work, I do have an old draft implementation of the new
> > QNumberFormatter class at [2], it works on ICU and Mac but the api is a
> > bit
> > outdated now. If you're happy to wait a week or two I'll have a new
> > version
> > of the draft api and test ICU implementation completed which now includes
> > a
> > proper QCurrencyFormatter class which you could copy.
> 
> I personally only care about Linux & similar platforms, so ICU is a fine
> dependency for me :) Perhaps in a few months Android as well, seems ICU
> might be doable there as well. If Windows & OSX are supported by ICU as
> well, even better, if some want to have Plan & Sheets over there.
> So using ICU seems a good option, as it solves the currency database problem
> for what I understood.
> 
> Additional bonus, if the drafts of the QNumberFormatter classes can be used
> decoupled from the real QLocale, their API can already get some real-world
> testing in our apps. And once they are official part of Qt our code does not
> need bigger changes.
> 
> So looking forward to those QCurrencyFormatter classes you are working on.
> 1-2 weeks waiting is fine, in the meantime we could look closer at the
> exact needs we have (e.g. with parsing) and compile some relevant unit test
> data.

Did you manage to get some time to work on a new version of the draft API, or 
should we better start off with the old version for now?
If the latter, in which parts should we expect changes in a new version you 
would come up with?

Cheers
Friedrich




More information about the calligra-devel mailing list