[wp-trac] [WordPress Trac] #47511: Add specific "default settings" for different locales
WordPress Trac
noreply at wordpress.org
Mon Jun 10 21:21:03 UTC 2019
#47511: Add specific "default settings" for different locales
-------------------------+-----------------------------
Reporter: azaozz | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Future Release
Component: I18N | Version:
Severity: normal | Resolution:
Keywords: needs-patch | Focuses:
-------------------------+-----------------------------
Comment (by azaozz):
> CLDR looks good implementation to me as default values for locale
settings.
Yeah, it looks like a really good starting point :)
The (main) intention here is to have WordPress specific per-locale
settings that are easy to define and maintain. Mainly things like excerpt
length, word-count method, etc. This would include a few of the "more
general" locale settings too, like default date and time format, decimal
separator, name display ordering, etc. (as long as they are needed/used in
the UI).
The "full" locale settings include a lot of other things, but don't think
we need most of them. They are targeted at operating system level support,
we get that "for free" through the web browsers :)
The next step is to define what these specific WP locale settings should
include. I've mentioned a few already but am pretty sure I'm missing some.
Then we can look at the best way to implement these settings. For now it
seems a (hard-coded) while list in core would be perfect. We can add a
default (en_US) map (array) with the specific settings, then generate the
initial per-locale changes/overrides to these default settings (perhaps
from CLDR), and finally each of the polyglots teams would be able to
adjust these settings if they wish.
Alternatively, especially if a white list becomes too big, we can think
about generating some sort of additional settings file from GlotPress
(again, can probably use CLDR for that) and distribute it with the main
wp-admin .po and .mo files. This will be significantly more difficult to
set-up and maintain. Frankly I don't think it will be needed, at least not
for now.
The good part is that once we add some API for the settings, we will be
able to switch from a white list to ...any other type we need or want.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/47511#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list