Zend_Locale does not honor parentLocale configuration

[barbazul]

This has become obvious after the update to CLDR 25 in which currency symbol position changed for es.xml but not for es_419.xml

All Latin American locales should inherit from es_419.xml as specified in supplementalData.xml line 409

<parentLocale parent="es_419" locales="es_AR es_BO es_CL es_CO es_CR es_CU es_DO es_EC es_GT es_HN es_MX es_NI es_PA es_PE es_PR es_PY es_SV es_US es_UY es_VE"/>

Try the following script:

$locale = new Zend_Locale('es_AR');
$curr = new Zend_Currency(null, $locale);
echo $curr->toCurrency(10);

Expected result $10

Actual result 10 $

[barbazul]

For completion, here's the ticket I opened about this issue in CLDR http://unicode.org/cldr/trac/ticket/8194

[froschdesign]

"parentLocales" is not supported in the current implementation of Zend_Locale.

(Note to me: Another reason to mark Zend_Locale as deprecated.)

[froschdesign]

Workaround:

$fmt = new NumberFormatter('es_AR', NumberFormatter::CURRENCY);
echo $fmt->formatCurrency(10, 'ARS');

Output:

$10,00

[barbazul]

Unfortunately, this workaround is not good for me as I am working in the
Magento e-commerce application and to apply this patch I would need to
modify (or override) core libraries that would render the aplication
unupgradeable.

The best fix in this scenario was to simply modify the XML files.

Proper support would be preferrable I suppose, but this simple fix worked
for me without issues so I stopped complaining.
El 18/05/2015 06:17, "Frank Brückner" notifications@github.com escribió:

Workaround:

$fmt = new NumberFormatter('es_AR', NumberFormatter::CURRENCY);echo $fmt->formatCurrency(10, 'ARS');

Output:

$10,00

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

[froschdesign]

I am working in the Magento e-commerce

Good to know.

The best fix in this scenario was to simply modify the XML files.

Bad idea, because all XML files come from an external library (CLDR) and we can not change this library.

[barbazul]

Yes, I am aware. That is the reason why propper support would be
preferrable.

However, simply changing the symbol position in the XML files was the fix
with the lowest impact in the application and the one that was the easiest
to track in case of an upgrade.
El 18/05/2015 08:05, "Frank Brückner" notifications@github.com escribió:

I am working in the Magento e-commerce

Good to know.

The best fix in this scenario was to simply modify the XML files.

Bad idea, because all XML files come from an external library (CLDR
http://cldr.unicode.org/) and we can not change this library.

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

[barbazul]

Thank you for your fix. I tried it in a Magento application and it works perfectly