Hi Justin, I encountered this during my work on the mavenizer. What I found even more strange is that the rb files come from us and the playerglobal from adobe so there is no chance the playerglobal would actually rely on them. Having a look at the rb files, it seemed to me that they are all empty. So I settled with simply ignoring them ;-)
Chris -----Ursprüngliche Nachricht----- Von: Justin Mclean [mailto:jus...@classsoftware.com] Gesendet: Freitag, 23. Januar 2015 00:03 An: dev@flex.apache.org Betreff: locales and player global Hi, Just noticed something odd in an installed SDK we have: ./frameworks/locale/de_DE/playerglobal_rb.swc ./frameworks/locale/en_US/playerglobal_rb.swc ./frameworks/locale/fr_FR/playerglobal_rb.swc ./frameworks/locale/ja_JP/playerglobal_rb.swc ./frameworks/locale/ru_RU/playerglobal_rb.swc ./frameworks/locale/zh_CN/playerglobal_rb.swc But we have more that 6 supported locales: da_DK el_GR en_GB fi_FI it_IT nb_NO pt_PT zh_CN de_CH en_AU en_US fr_CH ja_JP nl_NL ru_RU zh_TW de_DE en_CA es_ES fr_FR ko_KR pt_BR sv_SE Anyone know what's going on here and why that file is missing form the other locales? Thanks, Justin
