I think all of this really belongs in core, along with date formats, currency etc. But meanwhile, I'd like to propose that this module simply adds support for default settings for decimal separators etc. housed in it's translation files. These values should then pre-populate the site default fields according to what the site default language is and the user field according to what the user language is.

Taking it further would be to break out the UI part as an optional sub-module, wich could be done when the major languages has been amended with the above "translations", as most site builders will be happy with these defaults and won't necessarily care about letting users choose anyway.

Comments

liquidcms’s picture

liquidcms commented

if you add this to your settings.php:

  $conf = array(
    'i18n_variables' => array(
      'format_number_decimal_point',
      'format_number_thousands_sep',
    ),
  );

then the Number Format admin settings become i18n configurable.. not sure how well known this Drupal i18n feature is.

so (for a FR/EN for example) if you go to en/admin/settings/format_number and set the values and then go to fr/admin/settings/format_number and set the values; these will be stored and used as the site lang changes.

pretty cool.. :)

now if only the field widget settings had the same control so we could have the $ before number in one lang and after in another lang.

torotil’s picture

torotil commented
Version: 6.x-1.x-dev » 7.x-1.x-dev
Issue summary: View changes
Status: Active » Postponed

Yes, this is a good idea. I’m not sure it will happen until Drupal7’s EOL though.