[Translator] Potential locale inheritance improvements #12319
Labels
Comments
|
I've ended up using a compiler pass to mimic this (misd-service-development/phone-number-bundle#33). |
fabpot
added a commit
that referenced
this issue
Aug 28, 2018
…s (thewilkybarkid) This PR was squashed before being merged into the 4.2-dev branch (closes #28070). Discussion ---------- [Translator] Use ICU parent locales as fallback locales | Q | A | ------------- | --- | Branch? | master | Bug fix? | no | New feature? | yes | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #12319 | License | MIT | Doc PR | symfony/symfony-docs#10122 Currently the `Translator` fall backs based on the locale separator (eg `es_AR` to `es`), but the ICU data contains parent locales (eg `es_AR` is a child of `es_419`, as is `es_BO`, `es_EC` etc). This makes use of the ICU data to add add in these fallbacks. This means the specific locales can be used, but the translations can stored in these groupings (eg `es_419` for Latin American Spanish), as well as adding other sensible fallbacks (eg Cape Verdean Portuguese to `pt_PT`). Commits ------- e0f402f [Translator] Use ICU parent locales as fallback locales
This was referenced Nov 24, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The translator currently (when not setting one) falls back to the locale one level higher (eg
en_JEtoen). ICU contains data where the parent should be different (egen_JE>en_GB>en_001toen). Has using this data to produce a fall-back map been considered?This relates to misd-service-development/phone-number-bundle#22, where I'd like to be able to use
es_419(Latin American Spanish) to save having to have separate translations for each of the 20 sub-locales (according to the ICU data).The text was updated successfully, but these errors were encountered: