Archived

Use the original gem

nu-delocalize

delocalize provides parsing localized date/time and numbers, back into a standard format (i.e. the inverse of localization). This functionality is tightly integrated into Rails.

This fork preserves the pre-1.0 delocalize behaviour of Rails model delocalizing logic. It also includes logic to prevent writing nils to your database when failing to delocalize model attributes, raising a validation error instead.

Compatibility

This gem requires the following versions:

• Ruby >= 2.1.10 (Ruby >= 1.9.2 should work but isn't officially supported)
• Rails >= 4.1 (earlier versions should work but aren't officially supported)

Check the Travis configuration in order to see which configurations we are testing.

Installation

You can use delocalize as a gem from GitHub

Rails 4 and above

To use delocalize, put the following gem requirement in your Gemfile:

gem "delocalize", git: "https://github.com/nulogy/nu-delocalize.git"

What does it do? And how do I use it?

Delocalize, just as the name suggest, does pretty much the opposite of localize.

In the grey past, if you want your users to be able to input localized data, such as dates and numbers, you had to manually override attribute accessors:

def price=(price)
  write_attribute(:price, price.gsub(',', '.'))
end

You also had to take care of proper formatting in forms on the frontend so people would see localized values in their forms.

Delocalize does most of this under the covers.

Models

Overwrites ActiveRecord writer methods to pass certain column types (dates, times, and numbers) through the delocalization parsers, to convert localized values back into North American number ("1.2" instead of "1,2"), or UTC, formats.

Specifically, it patches the following:

• adds date? and time? query methods to abstract database column class (ActiveRecord::ConnectionAdapters::Column)
• delocalizes number strings while typecasting (ActiveRecord::AttributeMethods::Write .type_cast_attribute_for_write)
• delocalizes when writing attributes of Rails Models (ActiveRecord::Base#write_attribute_with_localization)
• delocalizes when setting time attributes with time zones (ActiveRecord::Base.define_method_attribute=)

Views

Extends text fields (ActionView::Helpers::Tags::TextField) to render values in a localized format.

Locale setup

In addition to your controller setup, you also need to configure your locale file(s). If you intend to use delocalize, you probably have a working locale file anyways. In this case, you only need to add two extra keys: date.input.formats and time.input.formats.

Assuming you want to use all of delocalize's parsers (date, time, number), the required keys are:

• number.format.delimiter
• number.format.separator
• date.input.formats
• time.input.formats
• date.formats.SOME_FORMAT for all formats specified in date.input.formats
• time.formats.SOME_FORMAT for all formats specified in time.input.formats

de:
  number:
    format:
      separator: ','
      delimiter: '.'
  date:
    input:
      formats: [:default, :long, :short] # <- this and ...

    formats:
      default: "%d.%m.%Y"
      short: "%e. %b"
      long: "%e. %B %Y"
      only_day: "%e"

    day_names: [Sonntag, Montag, Dienstag, Mittwoch, Donnerstag, Freitag, Samstag]
    abbr_day_names: [So, Mo, Di, Mi, Do, Fr, Sa]
    month_names: [~, Januar, Februar, März, April, Mai, Juni, Juli, August, September, Oktober, November, Dezember]
    abbr_month_names: [~, Jan, Feb, Mär, Apr, Mai, Jun, Jul, Aug, Sep, Okt, Nov, Dez]
    order: [ :day, :month, :year ]

  time:
    input:
      formats: [:long, :medium, :short, :default, :time] # <- ... this are the only non-standard keys
    formats:
      default: "%A, %e. %B %Y, %H:%M Uhr"
      short: "%e. %B, %H:%M Uhr"
      long: "%A, %e. %B %Y, %H:%M Uhr"
      time: "%H:%M"

    am: "vormittags"
    pm: "nachmittags"

For dates and times, you have to define input formats which are taken from the actual formats. The important thing here is to define input formats sorted by descending complexity; in other words: the format which contains the most (preferably non-numeric) information should be first in the list because it can produce the most reliable match. Exception: If you think there most complex format is not the one that most users will input, you can put the most-used in front so you save unnecessary iterations.

Be careful with formats containing only numbers: It's very hard to produce reliable matches if you provide multiple strictly numeric formats!

Releases

Updates are provided on GitHub through tags. Here's how to "cut a release":

$ git tag <version>
$ git push --tags

They can be required in a Gemfile as:

gem "delocalize", git: "https://github.com/nulogy/nu-delocalize.git", tag: "v2.0.1"

Contributors and Copyright

Here is a list of all people who ever contributed to nu-delocalize.

Copyright (c) 2017 Nulogy Corporation https://nulogy.com Copyright (c) 2009-2015 Clemens Kofler clemens@railway.at http://www.railway.at/ Released under the MIT license