edf2csv 0.6.84 → 0.6.86

package/docs/CHANGELOG.md

@@ -3,6 +3,37 @@
 Notable changes to edf2csv. Versions follow [semantic versioning](https://semver.org); while the
 major version is 0, a minor bump may contain breaking changes.
 
+## 0.6.86
+
+### the contents list omitted every diagnostic code on the page about them
+
+The on-page contents list showed h2s only. That is right for a page whose subheadings subdivide an
+argument, and wrong for the reference pages, where the subheading is the entry: warnings-and-errors
+is 13,000 words holding 42 of them, one per diagnostic code, and a reader who has just seen
+INPUT_CHANGED in their terminal was handed a list of eleven section titles, not one of which is
+what they came to look up. They could search the page, which is what people did, or scroll 13,000
+words. The ids were already there and already permanent.
+
+Subheadings are now listed, indented under their section and set a step smaller, so 53 entries read
+as a structure rather than a wall. The box scrolls at 60% of the viewport rather than pushing the
+first paragraph off the screen on the pages that need it most.
+
+## 0.6.85
+
+### printing a reference page spent the first sheet on navigation
+
+Reference documentation gets printed and saved next to the recordings it describes, and this site
+had no print styles at all. A printed CLI reference spent its first sheet on a sticky header, an
+eleven-item sidebar and a contents list of links that cannot be clicked on paper, then asked the
+printer for a near-black background across every page, which obliging printers supply.
+
+The navigation, the contents list, the skip link, the heading permalinks and the footer are the
+parts that only work on a screen, so they are dropped. Colours are forced to black on white.
+Headings avoid breaking away from the text they introduce, and code blocks are allowed to break
+across pages rather than being pushed whole onto the next sheet, since a forty-line transcript
+would otherwise leave half a sheet blank. External links have their destination written out after
+them, because a link on paper is otherwise a word with nowhere to go.
+
 ## 0.6.84
 
 ### every heading was addressable and none of them said so

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edf2csv",
-  "version": "0.6.84",
+  "version": "0.6.86",
   "description": "Convert EDF, EDF+ and BDF biosignal recordings (European Data Format) to CSV from the command line. Local, streaming, and never resamples or alters units.",
   "keywords": [
     "edf",