Korean won is displayed "3300,000 원" about django-prices HOT 5 CLOSED

It looks like you're using prices_i18n which in turn depends on Babel. Are you sure this bug is in django-prices?

from django-prices.

oh..

It might be a bug of babel.

babel takes parameters (such as format) django-prices won't pass.
So It might be configurable by setting correct parameters though.

2016-02-16 20:10 GMT+09:00 Patryk Zawadzki [email protected]:

It looks like you're using prices_i18n which in turn depend on Babel
http://babel.pocoo.org/en/latest/. Are you sure this bug is in
django-prices?

—
Reply to this email directly or view it on GitHub
#33 (comment)
.

from django-prices.

actually it is the babeldjango that doesn't accept the whole parameter
set..

2016-02-16 20:12 GMT+09:00 eugene kim [email protected]:

oh..

It might be a bug of babel.

babel takes parameters (such as format) django-prices won't pass.
So It might be configurable by setting correct parameters though.

2016-02-16 20:10 GMT+09:00 Patryk Zawadzki [email protected]:

It looks like you're using prices_i18n which in turn depend on Babel
http://babel.pocoo.org/en/latest/. Are you sure this bug is in
django-prices?

—
Reply to this email directly or view it on GitHub
#33 (comment)
.

from django-prices.

We pass the current locale to Babel's format_currency. For me that's what it returns:

from babel.numbers import format_currency
print(format_currency(3300000, 'KRW', locale='ko_KR'))
# ₩3,300,000

from django-prices.

oh..

That looks ok.

although we koreans are more accustomed to see
3,300,000 원

I'm closing this is minor issue.
(it is better to get the 3,300,000 원 but I guess It is better to talk to babel people)

from django-prices.