WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #47511, comment 10


Ignore:
Timestamp:
06/10/2019 09:30:23 PM (17 months ago)
Author:
azaozz
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #47511, comment 10

    initial v1  
    33Yeah, it looks like a really good starting point :)
    44
    5 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).
     5The (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, person's name display order, etc. (as long as they are needed/used in the UI).
    66
    77The "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 :)
     
    1111Then 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.
    1212
    13 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.
     13Alternatively, especially if a white list becomes too big, we can think about generating some sort of locale 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.
    1414
    1515The 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.