META: Provide locale (regional) formats framework for automated translation of non textual data

That's a great idea @jigaurus! I suggested in another (duplicate?) issue, to move it from Display page to the Field settings page, as en extra option:

Perhaps move the "Thousand marker" and "Decimal marker" settings from the "Manage display" page (/admin/structure/types/manage/article/display) to the field settings page? (/admin/structure/types/manage/article/fields/node.article.field_number), and live together with similar setting options, such as prefix and suffix ?

It could be an option the user can select, where either a global character is used, or a language specific. The current select options could be updated to this:

Thousand marker

• - None -
• Decimal point
• Comma
• Space
• Thin space
• Default for display language <<< Add this option

Decimal marker

• Decimal point
• Comma
• Default for display language <<< Add this option

Actually, the best location for locations goes in the Regional settings page:

/admin/config/regional/settings

…inside the Locale fieldset.

At this point, the site is already set up and, even if the site is in English, regional localization can be applied.

USA - English - Imperial measurements
Canada - English - Metric measurements.

So language settings != localization settings.

See the macOS screenshot attached for inspiration.

Finally, detaching language from localization givers more flexibility to the site owner. He may want to use a different set of number separators than what we would expect for his region.

re #61 ✨ META: Provide locale (regional) formats framework for automated translation of non textual data Active i agree, that adding an option for following the defaults for the display language for the thousand and decimal marker is a good idea. the only thing i might object is moving that setting into the field settings (if i understand the proposed resolution correctly). the fields settings is mainly about storage in the database, but those settings are about how thousand markers and decimal markers are presented in the frontend to the user. that way i guess the better choice would be to keep those two select fields where they currently are on the manage display page and simply add those options to the select lists (and set them as default)?

re #62 ✨ META: Provide locale (regional) formats framework for automated translation of non textual data Active i completely agree and i wonder if aside adding those localization setting to /admin/config/regional/settings it would make sense or even be necessary to consider adding those settings to the user profile page as well. so a user is able to override the global localization settings.

Thanks for the feedback @xmacinfo and @rkoller. Placing the settings on the Regional settings page does sound like a better idea. The reason I suggested under Fields settings, is because prefix and suffix are also placed there, and they are all about presentation, right?

(Perhaps prefix and suffix ought to be moved to the Display tab? :) ... That's for another issue.)

I am still just a casual user of languages in Drupal, and don't know the details about language/locale, and don't have the larger picture of how it all ties together. But as long as I -- as a site builder -- can easily for each language, select from a drop-down settings, which results in for example thousand separator being dot (".") for Danish and (",") for English, and set a field display to use these localized separators depending on display language, that would work for me.

And thanks for the image, a possible inspiration for format/number/localization set up for each language in Drupal, that would work well. And having the option of not using the normal defaults for a language would be a nice feature, and the ideal set up.

So, it seems like these could be changes in the interface:

• Set custom separators for each installed language (da, en, fr, etc.) as in the image from #62 (I do only see the default language on that page ...)
• Allow setting which separator to use under Display (as it is currently) having the options "Decimal point", "Comma", etc. and then add >> "Default for display language"

I updated the Issue Summary ✨ Allow localizing of formatting on decimal fields Active , trying to summarize the latest comments here. Feel free to correct if anything is wrong, or unclear :)

And great suggestion @rkoller about adding support for user profile page as well, which I included in the Issue Summary.

.... or should parts of the Issue Summary from #2757111 (mainly "Proposed resolution", I guess) be moved to this issue, to keep it all in one place?