[wp-trac] [WordPress Trac] #28303: How to handle default/formal translations for automatic upgrades?
WordPress Trac
noreply at wordpress.org
Wed Jun 3 21:47:05 UTC 2015
#28303: How to handle default/formal translations for automatic upgrades?
-------------------------+------------------
Reporter: zodiac1978 | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: 4.3
Component: I18N | Version:
Severity: normal | Resolution:
Keywords: needs-patch | Focuses:
-------------------------+------------------
Changes (by ocean90):
* keywords: => needs-patch
* milestone: Awaiting Review => 4.3
Comment:
I'm inclined to add core support for this in 4.3. It requires some changes
on the API side too, but these can be done after a release too, if
necessary.
The current idea is to support locales like `abc_DE_variant` or
`abc_variant` which can be captured via
`/(?:(.+)-)?([a-z]{2,3}(?:_[A-Z]{2})?(?:_[a-z]+)?).po/`
--
Ticket URL: <https://core.trac.wordpress.org/ticket/28303#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list