grunt-extract-cldr-data

grunt-extract-cldr-data

Extract CLDR data and transform it for use in JavaScript.

Getting Started

This plugin requires Grunt.

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-extract-cldr-data --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-extract-cldr-data');

The "extract_cldr_data" task

Overview

In your project's Gruntfile, add a section named extract_cldr_data to the data object passed into grunt.initConfig().

grunt.initConfig({
  extract_cldr_data: {
    options: {
      // Task-specific options go here.
    },
    your_target: {
      // Target-specific file lists and/or options go here.
    },
  },
})

dest

Each target must supply a dest property for the file path where the generated files should be outputted to. If dest is a directory, then a file will be generated per locale. If dest is a .js file, then only one file will be generated and it will contain the data for all options.locales.

Options

options.locales

Type: Array Default value: CLDR root locales; e.g., ['en', 'fr', ...]

An array of strings for the root locales to extract data for.

options.plurals

Type: Boolean Default value: false

Whether or not the pluralRuleFunction CLDR data should be extracted for each of the given locales.

options.fields

Type: Boolean|Array Default value: false

Whether or not the fields CLDR data should be extracted for each of the given locales. An array of string field names can be specified to only extract data for those fields; e.g., ['year', 'month', 'day', 'hour', 'minute', 'second'].

options.prelude

Type: String Default value: ""

A string that will be prepended to each of the generated files. This can be a code comment, or actual JavaScript code.

options.wrapEntry

Type: Function Default value: undefined

A function that will be passed a string of serialized data for each each option.locales. This function must return a string. This is useful for wrapping the locale data with JavaScript code; e.g., assigning it to a var.

Usage Examples

Extract Plural Functions

In this example, the CLDR plural functions for all of the root locales will be extracted and output into a single file which wraps each locale's data in a function call:

grunt.initConfig({
  extract_cldr_data: {
    all: {
      dest: 'locale-data/locales.js',
      options: {
        plurals: true,

        prelude: [
          '// GENERATED FILE',
          'var IntlMessageFormat = require("intl-messageformat");\n\n'
        ].join('\n'),

        wrapEntry: function (serialized) {
          return 'IntlMessageFormat.__addLocaleData(' + serialized + ');';
        }
      }
    },
  },
})

Extract Fields and Plural Functions

In this example, the field CLDR fields and plural functions for just English and French will be extracted and output into a one file per locale. Both of the locale's data is also wrapped in a function call:

grunt.initConfig({
  extract_cldr_data: {
    en_and_fr: {
      dest: 'locale-data/',
      options: {
        locales: ['en', 'fr'],
        fields : ['year', 'month', 'day', 'hour', 'minute', 'second'],
        plurals: true,

        wrapEntry: function (serialized) {
          return 'IntlRelativeFormat.__addLocaleData(' + serialized + ');';
        }
      }
    },
  },
})

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

• 1.0.0: Initial release.

License

This software is free to use under the Yahoo! Inc. BSD license. See the LICENSE file for license text and copyright information.