Fennec can ship with mutliple locales. We need a list of locale codes corresponding to the locales Android ships. Then we need to use that list to make multi-locale fennec builds for fennec.
tracking-fennec: --- → 2.0b2+
locale list from nexus one: ar cs cs_CZ da da_DK de de_AT de_BE de_CH de_DE de_LI de_LU el el_GR en en_AU en_BE en_BW en_BZ en_CA en_GB en_HK en_IE en_IN en_JM en_MH en_MT en_NA en_NZ en_PH en_PK en_SG en_TT en_US en_US_POSIX en_VI en_ZA en_ZW es es_ES es_US fi fr fr_BE fr_CA fr_CH fr_FR fr_LU fr_MC iw hr hu in it it_CH it_IT ja ja_JP ko ko_KR nb nb_NO nl nl_BE nl_NL pl pl_PL pt pt_BR pt_PT ro ru ru_RU sk sr sv sv_SE th tr tr_TR uk zh zh_CN zh_HANS zh_HANS_CN zh_HANT zh_HANT_TW zh_TW The Samsung i9000 has the same list except for zh_HANS, zh_HANS_CH, zh HANT and zh_HANT_TN
bug 563382 comment 6 says that we're not doing single-locale builds for Android? Do we have an idea on how the non-multi locales get on a device? Or should the android multi builds have all locales?
what do we need here to close this out?
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
I'm guessing a set of locales in a mobile-browser/locales/android-locales file that we want to go into the android multilocale apk. For now we're just using maemo-locales; if that's the desired set of locales, we don't need to do anything other than potentially rename that file.
You need to log in before you can comment on or make changes to this bug.