qvdjs 2.2.3 → 2.2.4

package/README.md

@@ -42,28 +42,31 @@ thing worth reading:
 
 ## Checked against Qlik Sense
 
-qvdjs is compared with Qlik Sense itself, not only with its own reading of the format. 36 fields in
-7 datasets - integers, doubles, text (non-ASCII, empty and number-like included), booleans, dates,
-timestamps and NULLs - are defined twice, as Qlik load-script expressions and as the JavaScript
-values a caller would write. Qlik Sense and qvdjs each write them to a QVD, and three things are
-checked:
+qvdjs is compared with Qlik Sense itself, not only with its own reading of the format. 48 fields in
+8 datasets - integers, doubles, text (non-ASCII, empty and number-like included), booleans, dates,
+timestamps, and NULLs beside numbers, text, dates and timestamps - are defined twice, as Qlik
+load-script expressions and as the JavaScript values a caller would write. Qlik Sense and qvdjs each
+write them to a QVD, and three things are checked:
 
 - **qvdjs writes the content Qlik writes** - the same symbols, of the same types, with the same text,
   on the same rows.
-- **Given Qlik's tags and number formats, qvdjs writes them unchanged** - the bit layout, below, is
-  the only part of a field's header left to differ.
+- **Given Qlik's tags and number formats, qvdjs writes them unchanged** - the bit layout and a tag the
+  values contradict, below, are the only parts of a field's header left to differ.
 - **Qlik reads qvdjs's file as it reads its own** - loaded into Qlik and stored again, with `Text()`,
   `Num()`, `IsNum()`, `IsText()`, `IsNull()` and `Year()` the same on every row.
 
 The live comparison runs on demand against a Qlik Sense server; its last run, against Qlik Sense
-Enterprise on Windows build 50699, passed for all 36 fields. Qlik's files from that run are kept in
+Enterprise on Windows build 50699, passed for all 48 fields. Qlik's files from that run are kept in
 the test suite, so **every CI run compares qvdjs's output with them again** - on Linux, Windows and
 macOS, under Node 22, 24 and 26 - along with reference files Qlik wrote for booleans, dates and
 timestamps.
 
-Two differences are by design: Qlik often gives a field more bits in the index than its values need,
-where qvdjs uses the fewest, and qvdjs adds no tags or number formats of its own - Qlik works tags out
-when it loads a file. QVD is also QlikView's format, but QlikView is not part of the comparison.
+Three differences are by design. Qlik often gives a field more bits in the index than its values need,
+where qvdjs uses the fewest. qvdjs adds no tags or number formats of its own - Qlik works tags out when
+it loads a file, and keeps any the file carries. And qvdjs drops a tag the values contradict, even one
+Qlik wrote: Qlik tags dates outside 1980 to 2080 as text when their field has no date format, although
+its own `IsNum()` reads every one as a number. QVD is also QlikView's format, but QlikView is not part
+of the comparison.
 
 → [Checked against Qlik Sense](https://qvdjs.ptarmiganlabs.com/v2.0/overview/checked-against-qlik-sense/)