iso-8859-5
Advanced tools
Comparing version 3.0.1 to 3.0.2
{ | ||
"name": "iso-8859-5", | ||
"version": "3.0.1", | ||
"version": "3.0.2", | ||
"description": "A robust iso-8859-5 encoder/decoder written in JavaScript.", | ||
@@ -5,0 +5,0 @@ "homepage": "https://mths.be/iso-8859-5", |
@@ -37,3 +37,3 @@ # iso-8859-5 [![Build status](https://github.com/mathiasbynens/iso-8859-5/workflows/run-checks/badge.svg)](https://github.com/mathiasbynens/iso-8859-5/actions?query=workflow%3Arun-checks) [![iso-8859-5 on npm](https://img.shields.io/npm/v/iso-8859-5)](https://www.npmjs.com/package/iso-8859-5) | ||
The optional `options` object and its `mode` property can be used to set the error mode. The two available error modes are `'fatal'` (the default) or `'replacement'`. (Note: This differs from [the spec](https://encoding.spec.whatwg.org/#error-mode), which recognizes `'fatal`' and `html` modes for encoders. The reason behind this difference is that the spec algorithm is aimed at producing HTML, whereas this library encodes into an environment-agnostic `Uint16Array` of bytes.) | ||
The optional `options` object and its `mode` property can be used to set the error mode. The two available error modes are `'fatal'` (the default) or `'replacement'`. (Note: This differs from [the spec](https://encoding.spec.whatwg.org/#error-mode), which recognizes “fatal” and HTML” modes for encoders. The reason behind this difference is that the spec algorithm is aimed at producing HTML, whereas this library encodes into an environment-agnostic `Uint16Array` of bytes.) | ||
@@ -40,0 +40,0 @@ ```js |
Sorry, the diff of this file is not supported yet
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
12400
363