Intl
Intl copied to clipboard
This WG was dechartered, replaced by https://github.com/nodejs/i18n
Collection of pain points when internationalising a nodejs CLI tool: - IME input can interfere with user input - Double width characters break ASCII layouting - Lack of standardized negotiation...
As per https://github.com/nodejs/Intl/issues/14 - make a writeup/sample app around working with locale … and codepage negociation… of the end user over http.
I threw [perf-nf.js](https://gist.github.com/srl295/72a8a2d88c8f45218d63) together to gather the numbers I posted [here](https://github.com/nodejs/node/issues/2917#issuecomment-146380131) We should do some more consistent testing… compare to other scaffolding/polyfill/jQuery.
Document overall Intl test plan incluing ICU version bumps, and how to do a version bump. related to #15
What are the pain points with using Node? - Example: What’s the pain level around lack of localized error messages? - #10 - #14 - #13
E.g.: https://github.com/andyearnshaw/Intl.js/blob/master/Gruntfile.js#L107-L113
## Invalid checksum in isomorphic apps One of the most common issue filled against Intl.js and Format.JS is about invalid checksum, which will happen when the server (nodejs, iojs) formats...