grapheme-conformance 0.1.0 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -7
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -141,13 +141,7 @@ Each failure carries a best-effort `rule`: `GB9c` (Indic conjunct), `GB11`
|
|
|
141
141
|
It inspects the input for characteristic code points; it does not implement
|
|
142
142
|
UAX #29 and does not prove which rule an implementation actually got wrong.
|
|
143
143
|
|
|
144
|
-
##
|
|
145
|
-
|
|
146
|
-
The scoreboard states counts. It does not rank or grade, and a lower number is
|
|
147
|
-
not automatically a reason to switch libraries — segmenters trade conformance
|
|
148
|
-
against size and speed, and which cases matter depends on the text you handle.
|
|
149
|
-
What the numbers do show is that the disagreements are not exotic: they land on
|
|
150
|
-
ordinary Devanagari.
|
|
144
|
+
## Intl.Segmenter and the host ICU
|
|
151
145
|
|
|
152
146
|
`Intl.Segmenter` is scored against whatever ICU the host Node ships, so its row
|
|
153
147
|
moves with the runtime, and not monotonically: Node 18.20.8 scores higher than
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "grapheme-conformance",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.2",
|
|
4
4
|
"description": "Score any JavaScript grapheme segmenter against Unicode's official GraphemeBreakTest.txt. Find out which string splitters are wrong, and about what.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"unicode",
|