locale
locale copied to clipboard
Browser locale negotiation for node.js
I could not use it at all because of one of my compilation options So I made it myself. I hope others don't have the same issues as me. ```typescript...
Through [writing typescript definitions](https://github.com/DefinitelyTyped/DefinitelyTyped/pull/42968), I discovered that ~langauge~ language is misspelled in the readme docs (it's correctly spelled in the code).
Bumps [express](https://github.com/expressjs/express) from 3.0.6 to 4.17.1. Release notes *Sourced from [express's releases](https://github.com/expressjs/express/releases).* > ## 4.17.1 > * Revert "Improve error message for `null`/`undefined` to `res.status`" > > ## 4.17.0 >...
## Overview This PR is bundling a bunch of things that I wanted to apply on the repo to make it a little more up-to-date, and hopefully easier to work...
When the browser sends a preference for `'en_US.UTF-8'` and the provided locale list has `'en'`, I would expect the locale to be set to `'en'`, not the full string. Is...
Using locale version 0.1.0. Take this example: ```javascript // classic string from a browser with both en-us and en-gb var locs = new Locale.Locales('it-it, it;q=0.9, en-us;q=0.8, en-gb;q=0.7, en;q=0.6') var best...
I was just wondering is there is an option for mapping en_US to en-US the browsers ask for locales using a "-" instead of an "_" and thanks for the...
The current API instantiates a new object for locales. It would be awesome if the system could work without instantiation of any kind (neither arrays: `.split`) nor instances of locales.
My supported locales are: `["en", "fr", "de", "zh-hant", "zh-hans"]` In Chrome my language settings are:  My current accept-language header is: `zh-CN,zh;q=0.8,zh-TW;q=0.6,en;q=0.4,en-US;q=0.2` After...
When I build locale with the current stable version of NodeJS (4.1.0), I get a warning message: ``` npm WARN engine [email protected]: wanted: {"node":">0.8.x