globalize-rpk 1.7.0

package/doc/blog-post/2017-07-xx-1.3.0-announcement.md

@@ -0,0 +1,177 @@
+# Globalize 1.3.0 announcement
+
+On July 3rd, we released Globalize 1.3.0. It is a special release, because it includes some very useful feature enhancements to support advanced date, time, timezone manipulation, and other long due fixes. We wanted to share more details on these improvements.
+
+## IANA/Olson Time Zone Support
+
+> This change was contributed by Kandaswamy Manikandan @rajavelmani (PayPal) and Rafael Xavier @rxaviers in #687 and #701.
+
+In previous versions, Globalize had some partial time zone support for a user's runtime time zone. However specific CLDR patterns (`z`, `v`, and `V`) that display strings such as `PDT`,  `Pacific Daylight Time`, `Pacific Time`, and `Los Angeles Time` could not be displayed. The challenge [we had](https://github.com/globalizejs/globalize/pull/202) to determine how costly a solution would be to provide full IANA/Olson time zone support due to the additional manipulation code and data (i.e., IANA database). Therefore, in the past, we encouraged users that needed to manipulate date in arbitrary time zones to use a separate library, like *moment-timezone*. Nevertheless, this solution never closed the gap between internationalization (i18n) implementations leveraging CLDR and having full maneuverability of time zones.
+
+With the latest release 1.3.0, Globalize fully supports time zone. Simply put, by using Globalize 1.3.0, you now have full IANA support with the strength of CLDR for i18n!
+
+```js
+Globalize.locale("en");
+let date = new Date();
+
+Globalize.formatDate(date, {datetime: "short", timeZone: "America/Los_Angeles"});
+// > '3/19/17, 3:19 PM'
+Globalize.formatDate(date, {datetime: "short", timeZone: "America/New_York"});
+// > '3/19/17, 6:19 PM'
+Globalize.formatDate(date, {datetime: "short", timeZone: "America/Sao_Paulo"});
+// > '3/19/17, 7:19 PM'
+Globalize.formatDate(date, {datetime: "short", timeZone: "Europe/Berlin"});
+// > '3/19/17, 11:19 PM'
+
+Globalize.formatDate(date, {datetime: "full", timeZone: "America/Los_Angeles"});
+// > 'Sunday, March 19, 2017 at 3:19:22 PM Pacific Daylight Time'
+Globalize.formatDate(date, {datetime: "full", timeZone: "America/New_York"});
+// > 'Sunday, March 19, 2017 at 6:19:22 PM Eastern Daylight Time'
+Globalize.formatDate(date, {datetime: "full", timeZone: "America/Sao_Paulo"});
+// > 'Sunday, March 19, 2017 at 7:19:22 PM Brasilia Standard Time'
+Globalize.formatDate(date, {datetime: "full", timeZone: "Europe/Berlin"});
+// > 'Sunday, March 19, 2017 at 11:19:22 PM Central European Standard Time'
+
+Globalize("pt").formatDate(date, {datetime: "full", timeZone: "America/Sao_Paulo"});
+// > 'domingo, 19 de março de 2017 19:19:22 Horário Padrão de Brasília'
+Globalize("de").formatDate(date, {datetime: "full", timeZone: "Europe/Berlin"});
+// > 'Sonntag, 19. März 2017 um 23:19:22 Mitteleuropäische Normalzeit'
+Globalize("zh").formatDate(date, {datetime: "full", timeZone: "Asia/Shanghai"});
+// > '2017年3月20日星期一 中国标准时间 上午6:19:22'
+Globalize("ar").formatDate(date, {datetime: "full", timeZone: "Africa/Cairo"});
+// > 'الاثنين، ٢٠ مارس، ٢٠١٧ ١٢:١٩:٢٢ ص توقيت شرق أوروبا الرسمي'
+```
+
+We have solved this in a low footprint, high performance implementation using [zoned-date-time](https://github.com/rxaviers/zoned-date-time) under the hoods, which is a 0.6KB library for the time zone manipulations. We have leveraged the Globalize Compiler for precompling the IANA data base for production. For example, let's say you are serving content in English (e.g. locale en-US) for America/Los_Angeles time using the following formatter:
+
+```js
+var dateWithTimeZoneFormatter = Globalize.dateFormatter({
+  datetime: "full",
+  timeZone: "America/Los_Angeles"
+});
+```
+
+The final size (for production) of this code will be:
+
+| filename                                 | minified+gzipped size |
+| ---------------------------------------- | --------------------- |
+| i18n/en.js (includes CLDR and IANA data) | 1.7KB                 |
+| core, number, and date globalize runtime lib + zoned-date-time | 7.0KB                 |
+
+See globalize [compiler example](https://github.com/globalizejs/globalize/tree/master/examples/globalize-compiler) or [app-npm-webpack example](https://github.com/globalizejs/globalize/tree/master/examples/app-npm-webpack) for details.
+
+## Format Date To Parts
+
+> This change was contributed by Reza Payami @rpayami (PayPal) and Rafael Xavier @rxaviers in #697 and #700.
+
+Modern user interfaces often need to manipulate the date format output, which is impossible via the existing format function that returns an opaque string. Making any attempt to do this can break internationalization support. [Ecma-402](https://github.com/tc39/ecma402/) has recently added [`Intl.DateTimeFormat.prototype.formatToParts`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/DateTimeFormat/formatToParts) to fulfill that purpose, which at the time of this post, is at stage 4 and is implemented by latest Firefox and Chrome.
+
+In Globalize, we introduced [`.dateToPartsFormatter`](https://github.com/globalizejs/globalize/blob/master/doc/api/date/date-to-parts-formatter.md) and [`.formatDateToParts`](https://github.com/globalizejs/globalize/blob/master/doc/api/date/date-to-parts-formatter.md).
+
+```js
+Globalize.locale( "en" );
+Globalize.formatDateToParts(new Date(2010, 10, 30));
+// > [
+//   { "type": "month", "value": "11" },
+//   { "type": "literal", "value": "/" },
+//   { "type": "day", "value": "30" },
+//   { "type": "literal", "value": "/" },
+//   { "type": "year", "value": "2010" }
+// ]
+```
+
+The data is available separately and it can be formatted and concatenated again in a customized way. For example by using [`Array.prototype.map()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/map), [arrow functions](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions), a [switch statement](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/switch), [template literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals), and [`Array.prototype.reduce()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/reduce).
+
+```js
+let formatter;
+
+Globalize.locale( "en" );
+formatter = Globalize.dateToPartsFormatter({datetime: "short"});
+
+formatter( new Date( 2010, 10, 30, 17, 55 ) ).map(({type, value}) => {
+  switch ( type ) {
+    case "year": return `<strong>${value}</strong>`;
+    default: return value;
+  }
+}).join( "" );
+// > "11/30/<strong>10</strong>, 5:55 PM"
+```
+
+See [React Date Input](https://github.com/rxaviers/react-date-input) as a demo of a UI component for React optimized for i18n and a11y.
+
+| Localized and smart date input           | Feb 28 in `en`, `es`, `pt`, `de`, `zh`, `ko`, and `ar` |
+| ---------------------------------------- | ---------------------------------------- |
+| ![en](https://media.giphy.com/media/xUA7aZAUNINGP2jI4M/giphy.gif) | ![en-es-pt-de-zh-ko-ar](https://media.giphy.com/media/3og0ILQu0KxLRewJnW/giphy.gif) |
+
+## Dynamically Augmented Date Skeletons
+
+> This change was contributed by Marat Dyatko @vectart and Artur Eshenbrener @Strate in #462 and #604.
+
+The style used to display a date format often varies depending on the application. CLDR offers data for certain presets like short (e.g., short date `"7/1/17"`), medium (e.g., medium date `"Jul 1, 2017"`), long (e.g., long date `"July 1, 2017"`), and full (e.g., full date `"Saturday, July 1, 2017"`). Although, we may want something different such as `"Jul 1"`. For that CLDR offers data for individual [date fields](http://www.unicode.org/reports/tr35/tr35-dates.html#Date_Field_Symbol_Table) and their combinations, which are used by Globalize to synthesize an open-ended list of custom formats (called skeletons). But, what's interesting is that it would be prohibitively large if CLDR provided data for every single possible combination. So, there's an algorithm specified by [UTS#35](http://www.unicode.org/reports/tr35/tr35-dates.html#availableFormats_appendItems) to deduce missing data from the requested format.
+
+For the `"Jul 1"` example, we should use `{skeleton: "MMMd"}`. Internally, Globalize finds a direct match in CLDR for the requested skeleton. This works fine in previous Globalize versions.
+
+For that next example, let's assume we want `"July 1"`, i.e., `{skeleton: "MMMMd"}`. Internally, Globalize doesn't find a direct match in CLDR. For this skeleton, Globalize needs to use the data for `MMMd`, which maps to `"MMM d"` in the English case, and then it needs to replace `MMM` with `MMMM` dynamically generating `"MMMM d"`. This doesn't work in previous versions of Globalize, but it works now on latest v1.3.0.
+
+If we wanted `"07/01"` instead, we should use `{skeleton: "MMdd"}`. Internally, Globalize doesn't find a direct match in CLDR for this skeleton and, therefore, it fais in globalize v1.2.3. Globalize needs to use the data for `Md`, which in the case of English maps to `"M/d"`, and then replace `M` wtih `MM` and `d` with `dd` dynamically generating `"MM/dd"`.
+
+To make a long story short, the algorithm in globalize v1.3.0 has been significantly improved and it allows using virtually any skeletons.
+
+```js
+// A skeleton not directly found in CLDR and that needs to be deduced by globalize.
+// In English, globalize needs to use the data for GyMMMEd, and adjust MMM with MMMM,
+// and E with EEEE. Then, it needs to find the data for hms and glue them together
+// using the appropriate format.
+// On globalize v1.2.3, an error is thrown saying this skeleton wasn't found.
+let skeleton = "GyMMMMEEEEdhms";
+Globalize("en").formatDate(new Date(), {skeleton});
+// > 'Saturday, July 1, 2017 AD at 4:58:27 PM'
+Globalize("pt").formatDate(new Date(), {skeleton});
+// > 'sábado, 1 de julho de 2017 d.C. 5:01:20 PM'
+Globalize("de").formatDate(new Date(), {skeleton});
+// > 'Samstag, 1. Juli 2017 n. Chr. um 5:01:33 nachm.'
+Globalize("zh").formatDate(new Date(), {skeleton});
+// > '公元2017年七月月1日星期六 下午5:01:35'
+Globalize("ko").formatDate(new Date(), {skeleton});
+// > 'AD 2017년 7월 1일 토요일 오후 5:01:38'
+Globalize("ar").formatDate(new Date(), {skeleton});
+// > 'السبت، ١ يوليو، ٢٠١٧ م ٥:٠١:٤٠ م'
+Globalize("ar-MA").formatDate(new Date(), {skeleton});
+// > 'السبت، 1 يوليوز، 2017 م 5:04:29 م'
+Globalize("it").formatDate(new Date(), {skeleton});
+// > 'sabato 1 luglio 2017 d.C. 5:01:52 PM'
+```
+
+Read our [getting started](https://github.com/globalizejs/globalize/#getting-started) and play with it yourself.
+
+## Other Enhancements and Bug Fixes
+
+🎉 Enhancements
+
+- Date: Show timezone offset optional minutes for O pattern (e.g., GMT-6:30 note the :30) [#339](https://github.com/globalizejs/globalize/pull/339) (via PR [#729](https://github.com/globalizejs/globalize/pull/729)) (Rafael Xavier)
+- Date: Show timezone offset optional minutes and seconds for x and X patterns (e.g., -06:30 note the :30) [#339](https://github.com/globalizejs/globalize/pull/339) (via PR [#729](https://github.com/globalizejs/globalize/pull/729)) (Rafael Xavier)
+- Date: Assert options.skeleton (PR [#726](https://github.com/globalizejs/globalize/pull/726)) (Rafael Xavier)
+- Date parser: Make runtime phase lighter [#735](https://github.com/globalizejs/globalize/pull/735) (Rafael Xavier)
+- Date parser: Loose Matching PR [#730](https://github.com/globalizejs/globalize/pull/730) (Rafael Xavier)
+  - Allows, among others, parsing arabic dates as user types them (i.e., without control characters)
+- Number formatter: Amend integer and fraction formatter for small numbers like 1e-7 [#750](https://github.com/globalizejs/globalize/pull/750) (Rafael Xavier)
+- Number parser: Lenient about trailing decimal separator [#744](https://github.com/globalizejs/globalize/pull/744) (Rafael Xavier)
+- Runtime: Use strict [#676](https://github.com/globalizejs/globalize/pull/676) (Zack Birkenbuel)
+
+🐛 Fixes
+
+- Date parser: invalid output by mixing numbering systems [#696](https://github.com/globalizejs/globalize/pull/696) (via PR [#733](https://github.com/globalizejs/globalize/pull/733)) (Rafael Xavier)
+- Date parser: fails on Turkish full datetime with Monday or Saturday [#690](https://github.com/globalizejs/globalize/pull/690) (via PR [#732](https://github.com/globalizejs/globalize/pull/732)) (Rafael Xavier)
+
+⚙️ Others
+
+- Compiler tests! [#721](https://github.com/globalizejs/globalize/pull/721) (via PR [#727](https://github.com/globalizejs/globalize/pull/727)) (Nikola Kovacs)
+- Documentation style refactor [#737](https://github.com/globalizejs/globalize/pull/737) (Rafael Xavier)
+
+## Last but not least
+
+Special thanks to other PayPal internationalization team members including Daniel Bruhn, Lucas Welti, Alolita Sharma, Mike McKenna for testing and helping integrate Globalize for PayPal products.
+
+Special thanks to James Bellenger and Nicolas Gallagher for the React and Webpack integration enhancements for Twitter products, which certainly deserves its own blog post.
+
+Many thanks to all of you who participated in this release by testing, reporting bugs, or submitting patches, including Jörn Zaefferer, Frédéric Miserey, Nova Patch, and whole Globalize team.

package/doc/cldr.md

@@ -0,0 +1,114 @@
+# Unicode CLDR usage
+
+## How do I get CLDR data?
+
+*By downloading the JSON packages individually...*
+
+Unicode CLDR is available as JSON at https://github.com/unicode-cldr/ (after this [json-packaging proposal][] took place). Please, read https://github.com/unicode-cldr/cldr-json for more information about package organization.
+
+[json-packaging proposal]: http://cldr.unicode.org/development/development-process/design-proposals/json-packaging
+
+*By using a package manager...*
+
+`cldr-data` can be used for convenience. It always downloads from the correct source.
+
+Use bower `bower install cldr-data` ([detailed instructions][]) or npm `npm install cldr-data`. For more information, see:
+
+- https://github.com/rxaviers/cldr-data-npm
+- https://github.com/rxaviers/cldr-data-bower
+
+[detailed instructions]: https://github.com/rxaviers/cldr-data-bower
+
+## How do I load CLDR data into Globalize?
+
+The short answer is by using `Globalize.load()` and passing the JSON data as the first argument. Below, follow several examples on how this could be accomplished.
+
+Example of embedding CLDR JSON data:
+
+```html
+<script>
+Globalize.load({
+  main: {
+    en: {
+      ...
+    }
+  },
+  supplemental: {
+    likelySubtags: {
+      ...
+    },
+    timeDate: {
+      ...
+    },
+    weekData: {
+      ...
+    }
+  }
+});
+</script>
+```
+
+Example of loading it dynamically:
+
+```html
+<script src="jquery.js"></script>
+<script>
+
+// Use $.getJSON instead of $.get if your server is not configured to return the
+// right MIME type for .json files.
+$.when(
+  $.get( "cldr/main/en/ca-gregorian.json" ),
+  $.get( "cldr/supplemental/likelySubtags.json" ),
+  $.get( "cldr/supplemental/timeData.json" ),
+  $.get( "cldr/supplemental/weekData.json" )
+).then(function() {
+
+  // Normalize $.get results, we only need the JSON, not the request statuses.
+  return [].slice.apply( arguments, [ 0 ] ).map(function( result ) {
+      return result[ 0 ];
+  });
+
+}).then( Globalize.load ).then(function() {
+
+  // Your code goes here.
+
+});
+
+</script>
+```
+
+Example using AMD (also see our [functional tests](../../test/functional.js)):
+```javascript
+define([
+  "globalize",
+  "json!cldr-data/main/en/ca-gregorian.json",
+  "json!cldr-data/supplemental/likelySubtags.json",
+  "json!cldr-data/supplemental/timeData.json",
+  "json!cldr-data/supplemental/weekData.json",
+  "globalize/date"
+], function( Globalize, enCaGregorian, likelySubtags, timeData, weekData ) {
+
+  Globalize.load(
+    enCaGregorian,
+    likelySubtags,
+    timeData,
+    weekData
+  );
+
+  // Your code goes here.
+
+});
+```
+
+Example using Node.js:
+
+```javascript
+var Globalize = require( "globalize" );
+
+Globalize.load(
+  require( "cldr-data/main/en/ca-gregorian" ),
+  require( "cldr-data/supplemental/likelySubtags" ),
+  require( "cldr-data/supplemental/timeData" ),
+  require( "cldr-data/supplemental/weekData" )
+);
+```

package/doc/error/e-default-locale-not-defined.md

@@ -0,0 +1,9 @@
+## E_DEFAULT_LOCALE_NOT_DEFINED
+
+Thrown when any static method, eg. `Globalize.formatNumber()` is used prior to setting the Global locale with `Globalize.locale( <locale> )`.
+
+Error object:
+
+| Attribute | Value |
+| --- | --- |
+| code | `E_DEFAULT_LOCALE_NOT_DEFINED` |

package/doc/error/e-invalid-cldr.md

@@ -0,0 +1,14 @@
+## E_INVALID_CLDR
+
+Thrown when a CLDR item has an invalid or unexpected value.
+
+Error object:
+
+| Attribute | Value |
+| --- | --- |
+| code | `E_INVALID_CLDR` |
+| description | Reason why the data was considered invalid |
+
+- description "Missing rules to deduce plural form of \`{value}\`"
+ 
+ Thrown when the plural form (also known as plural group) is not found for the given value. This error is very unlikely to occur and is related to incomplete or invalid CLDR `supplemental/plurals-type-cardinal/{language}` data.

package/doc/error/e-invalid-par-type.md

@@ -0,0 +1,12 @@
+## E_INVALID_PAR_TYPE
+
+Thrown when a parameter has an invalid type on any static or instance methods.
+
+Error object:
+
+| Attribute | Value |
+| --- | --- |
+| code | `E_INVALID_PAR_TYPE` |
+| name | Name of the invalid parameter |
+| value | Invalid value |
+| expected | Expected type |

package/doc/error/e-invalid-par-value.md

@@ -0,0 +1,11 @@
+## E_INVALID_PAR_VALUE
+
+Thrown for certain parameters when the type is correct, but the value is invalid. Currently, the only parameter with such validation is the date format (for either format and parse). Format allows [certain variants](../api/date/date-formatter.md#parameters), if it's none of them, error is thrown.
+
+Error object:
+
+| Attribute | Value |
+| --- | --- |
+| code | `E_INVALID_PAR_VALUE` |
+| name | Name of the invalid parameter |
+| value | Invalid value |

package/doc/error/e-missing-cldr.md

@@ -0,0 +1,11 @@
+## E_MISSING_CLDR
+
+Thrown when any required CLDR item is NOT found.
+
+Error object:
+
+| Attribute | Value |
+| --- | --- |
+| code | `E_MISSING_CLDR` |
+| path | Missing CLDR item path |
+

package/doc/error/e-missing-parameter.md

@@ -0,0 +1,10 @@
+## E_MISSING_PARAMETER
+
+Thrown when a required parameter is missing on any static or instance methods.
+
+Error object:
+
+| Attribute | Value |
+| --- | --- |
+| code | `E_MISSING_PARAMETER` |
+| name | Name of the missing parameter |

package/doc/error/e-missing-plural-module.md

@@ -0,0 +1,9 @@
+## E_MISSING_PLURAL_MODULE
+
+Thrown when plural module is needed, but not loaded, eg. formatting currencies using plural messages.
+
+Error object:
+
+| Attribute | Value |
+| --- | --- |
+| code | `E_MISSING_PLURAL_MODULE` |

package/doc/error/e-par-missing-key.md

@@ -0,0 +1,11 @@
+## E_PAR_MISSING_KEY
+
+Thrown when a parameter misses a required key.
+
+Error object:
+
+| Attribute | Value |
+| --- | --- |
+| code | `E_PAR_MISSING_KEY` |
+| key | Name of the missing parameter's key |
+| name | Name of the missing parameter |

package/doc/error/e-par-out-of-range.md

@@ -0,0 +1,13 @@
+## E_PAR_OUT_OF_RANGE
+
+Thrown when a parameter is not within a valid range of values.
+
+Error object:
+
+| Attribute | Value |
+| --- | --- |
+| code | `E_PAR_OUT_OF_RANGE` |
+| name | Name of the invalid parameter |
+| value | Invalid value |
+| minimum | Minimum value of the valid range |
+| maximum | Maximum value of the valid range |

package/doc/error/e-unsupported.md

@@ -0,0 +1,10 @@
+## E_UNSUPPORTED
+
+Thrown for unsupported features, eg. to format unsupported date patterns.
+
+Error object:
+
+| Attribute | Value |
+| --- | --- |
+| code | `E_UNSUPPORTED` |
+| feature | Description of the unsupported feature |

package/doc/migrating-from-0.x.md

@@ -0,0 +1,64 @@
+# Migrating from Globalize 0.x
+
+Globalize 0.x came with a bundled locale for US English, and optional files for various other locales. Globalize 1.x uses CLDR for the locale data, and it doesn't bundle any locale data. Check out the documentation for loading CLDR data in 1.x to learn more about that. If you were only using the bundle locale, you only need to load CLDR data for US English. If you were loading other locales, make sure you load those from CLDR as well.
+
+On the API side, things have also changed, to simplify usage, remove ambiguity and add features. The rest of this document provides a brief function-by-function list.
+
+If you still need help with migration, let us know. We may extend this guide later as necessary.
+
+## Globalize.addCultureInfo()
+
+This method is replaced by `Globalize.loadMessages( json )`. If you were using it for anything except message translations, you may also need to use `Globalize.load`.
+
+## Globalize.cultures
+
+This property is gone. You can use Cldrjs to traverse CLDR directly.
+
+## Globalize.culture( [locale] )
+
+This method is replaced by the `Globalize.locale( [locale|cldr] )` method. Call it without arguments to retrieve the default locale, call it with a string argument to set the default locale.
+
+## Globalize.findClosestCulture
+
+This method is gone, there is no replacement. If you still need this method, create an issue with your usecase.
+
+## Globalize.format
+
+Replaced by three separate methods:
+
+* `.formatNumber( value [, options] )`
+* `.formatCurrency( value, currency [, options] )`
+* `.formatDate( value, pattern )`
+
+See their respective documentation for usage details. Note that the number and date formats are now based on CLDR, using the options and patterns standardized by Unicode. We don't currently have documentation for migrating these formats.
+
+## Globalize.localize
+
+Replaced by `.formatMessage( path [, variables ] )`. The new API is quite different and provides much more than just value-lookup. See their respective documentation for usage details.
+
+## Globalize.parseInt/parseFloat
+
+Replaced by `.parseNumber( value [, options] )`.  So where you might have previously executed:
+
+```js
+Globalize( "en" ).parseFloat( "123,456.789" )
+// > 123456.789
+```
+
+You could now execute:
+
+```js
+Globalize( "en" ).parseNumber( "123,456.789" )
+// > 123456.789
+```
+
+`parseNumber` is an alias for [`.numberParser( [options] )( value )`](api/number/number-parser.md).  So you could also do this:
+
+```js
+Globalize( "en" ).numberParser()( "123,456.789" )
+// > 123456.789
+```
+
+## Globalize.parseDate
+
+This method still exists, and the signature is almost the same: `.parseDate( value, pattern )`. Note that `pattern` indicates just a single "format", where Globalize 0.x supported multiple of those "formats".

package/examples/amd-bower/.bowerrc

@@ -0,0 +1,7 @@
+{
+  "directory": "bower_components",
+  "scripts": {
+    "preinstall": "npm install cldr-data-downloader",
+    "postinstall": "node ./node_modules/cldr-data-downloader/bin/download.js -i bower_components/cldr-data/index.json -o bower_components/cldr-data/"
+  }
+}

package/examples/amd-bower/README.md

@@ -0,0 +1,65 @@
+# Hello World (AMD + bower)
+
+We assume you know what [AMD](https://github.com/amdjs/amdjs-api/wiki/AMD) and
+[bower](http://bower.io/) is.
+
+The demo is composed of the following files:
+
+```
+.
+├── index.html
+└── main.js
+```
+
+Before running it, execute the requirements below.
+
+
+## Requirements
+
+**1. Install Globalize**
+
+Let's use bower to download Globalize. For more information on regard of
+installation, please read [Getting Started](../../README.md#installation).
+
+```
+bower install
+```
+
+Note bower will also fetch some other dependencies of this demo, eg. require.js
+and its json plugin.
+
+You'll get this:
+
+```
+.
+├── bower_components/
+│   ├── globalize/ 
+│   │   └── dist/
+│   │       ├── globalize
+│   │       │   ├── date.js
+│   │       │   └── ...
+│   │       └── globalize.js
+│   └── ...
+├── index.html
+└── main.js
+```
+
+**2. Install Dependencies**
+
+No action needed, because bower has already handled that for us.
+
+**3. CLDR content**
+
+No action needed, because bower has already handled that for us. Note `.bowerrc`
+has postinstall hook that populates bower's cldr-data skeleton. For more
+information, see [bower's cldr-data](https://github.com/rxaviers/cldr-data-bower).
+
+
+## Running the demo
+
+Once you've completed the requirements above:
+
+1. Start a server by running `python -m SimpleHTTPServer` or other alternative servers such as [http-server](https://github.com/nodeapps/http-server), [nginx](http://nginx.org/en/docs/), [apache](http://httpd.apache.org/docs/trunk/).
+1. Point your browser at `http://localhost:8000/`.
+1. Understand the demo by reading the source code (both index.html and main.js).
+We have comments there for you.

package/examples/amd-bower/bower.json

@@ -0,0 +1,13 @@
+{
+  "name": "globalize-hello-world-amd-bower",
+  "dependencies": {
+    "cldr-data": "*",
+    "globalize": "^1.3.0",
+    "iana-tz-data": "*"
+  },
+  "devDependencies": {
+    "requirejs": "2.1.14",
+    "requirejs-plugins": "1.0.2" ,
+    "requirejs-text": "2.0.12"
+  }
+}

package/examples/amd-bower/index.html

@@ -0,0 +1,46 @@
+<!doctype html>
+<head>
+    <meta charset="utf-8">
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+    <title>Globalize Hello World (AMD + bower)</title>
+</head>
+<body>
+    <h1>Globalize Hello World (AMD + bower)</h1>
+
+    <div id="requirements">
+        <h2>Requirements</h2>
+        <ul>
+            <li>Run `bower install` (you must have bower installed first).</li>
+            <li>Start a server, e.g., by running `python -m SimpleHTTPServer`.</li>
+            <li>Point your browser at `http://localhost:8000/`.</li>
+            <li>Please, read README.md for more information on any of the above.</li>
+        </ul>
+    </div>
+
+    <div id="demo" style="display: none">
+        <h2>Demo output</h2>
+        <p>Now: <span id="date"></span></p>
+        <p>Now: <span id="dateToParts"></span> (note the highlighted month, the markup was added using formatDateToParts)</p>
+        <p>Now (in America/Sao_Paulo): <span id="zonedDate"></span></p>
+        <p>A number: <span id="number"></span></p>
+        <p>A number (compact form): <span id="number-compact"></span></p>
+        <p>A currency: <span id="currency"></span></p>
+        <p>Plural form of <span id="plural-number"></span> is <span id="plural-form"></span></p>
+        <p>Messages:</p>
+        <ul>
+            <li><span id="message-0"></span></li>
+            <li><span id="message-1"></span></li>
+            <li><span id="message-2"></span></li>
+            <li><span id="message-3"></span></li>
+        </ul>
+        <p>Something happened: <span id="relative-time"></span></p>
+        <p>Speed limit: <span id="unit"></span></p>
+    </div>
+
+    <!--
+    Load require.js and let it execute main.js
+    -->
+    <script data-main="main.js" src="bower_components/requirejs/require.js"></script>
+
+</body>
+</html>