[wp-trac] [WordPress Trac] #28197: Fallback Languages
WordPress Trac
noreply at wordpress.org
Tue Aug 11 14:58:08 UTC 2015
#28197: Fallback Languages
---------------------------+-------------------------
Reporter: downstairsdev | Owner:
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: I18N | Version: 4.0
Severity: normal | Resolution: maybelater
Keywords: | Focuses:
---------------------------+-------------------------
Comment (by swissspidy):
> A proper mapping of language codes that can be fallen back to could help
a bit with both this and performance.
Why not create a new translatable string for a fallback chain. For
example, in de_CH_formal we'd say we want to fall back to de_CH,
de_DE_formal, de_DE — and of course to en_US in the end. This information
could be translated on translate.wordpress.org by each locale.
The translation contributors know best which fallback works for their
locale. We shouldn't force a specific fallback.
Summary:
* Core solution with minimal overhead (just 1 translatable string, no UI
needed)
* Locales know best which fallbacks work for them
* Also works for cases like ug_CN -> zh_CN
--
Ticket URL: <https://core.trac.wordpress.org/ticket/28197#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list