{"name":"has-unicode","version":"1.0.1","description":"Try to guess if your terminal supports unicode","main":"index.js","scripts":{"test":"tap test/*.js"},"repository":{"type":"git","url":"https://github.com/iarna/has-unicode"},"keywords":["unicode","terminal"],"author":{"name":"Rebecca Turner","email":"me@re-becca.org"},"license":"ISC","bugs":{"url":"https://github.com/iarna/has-unicode/issues"},"homepage":"https://github.com/iarna/has-unicode","devDependencies":{"require-inject":"^1.1.1","tap":"^0.4.13"},"readme":"has-unicode\n===========\n\nTry to guess if your terminal supports unicode\n\n```javascript\nvar hasUnicode = require(\"has-unicode\")\n\nif (hasUnicode()) {\n  // the terminal probably has unicode support\n}\n```\n```javascript\nvar hasUnicode = require(\"has-unicode\").tryHarder\nhasUnicode(function(unicodeSupported) {\n  if (unicodeSupported) {\n    // the terminal probably has unicode support\n  }\n})\n```\n\n## Detecting Unicode\n\nWhat we actually detect is UTF-8 support, as that's what Node itself supports.\nIf you have a UTF-16 locale then you won't be detected as unicode capable.\n\n### Windows\n\nSince at least Windows 7, `cmd` and `powershell` have been unicode capable.\nAs such, we report any Windows installation as unicode capable.\n\n\n### Unix Like Operating Systems\n\nWe look at the environment variables `LC_ALL`, `LC_CTYPE`, and `LANG` in\nthat order.  For `LC_ALL` and `LANG`, it looks for `.UTF-8` in the value. \nFor `LC_CTYPE` it looks to see if the value is `UTF-8`.  This is sufficient\nfor most POSIX systems.  While locale data can be put in `/etc/locale.conf`\nas well, AFAIK it's always copied into the environment.\n\n","readmeFilename":"README.md","_id":"has-unicode@1.0.1","_shasum":"c46fceea053eb8ec789bffbba25fca52dfdcf38e","_from":"https://registry.npmjs.org/has-unicode/-/has-unicode-1.0.1.tgz","_resolved":"https://registry.npmjs.org/has-unicode/-/has-unicode-1.0.1.tgz"}