edfcore 0.4.264 → 0.4.265

package/dist/constants.d.ts

@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
     readonly reserved: 224;
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export declare const VERSION = "0.4.264";
+export declare const VERSION = "0.4.265";
 //# sourceMappingURL=constants.d.ts.map

package/dist/constants.js

@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
     reserved: 224,
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.4.264';
+export const VERSION = '0.4.265';
 //# sourceMappingURL=constants.js.map

package/dist/text/printable.d.ts

@@ -21,6 +21,15 @@
  * Only C0 and DEL are replaced. Latin-1 letters above 0x7f are ordinary characters in an
  * electrode label written on a European system, and 0x80-0x9f are left alone because edfcore
  * decodes headers as ISO-8859-1, where that range is not control characters.
+ *
+ * That argument covers header text, which is Latin-1 and therefore stops at U+00FF. It is not the
+ * only thing printed through here: ANNOTATION text is UTF-8, so `U+2028 LINE SEPARATOR` and
+ * anything else above U+00FF can arrive from a file — `cli-run.ts` prints it for `events` and
+ * `format-annotations.ts` for the hypnogram. Those pass through unchanged, deliberately. No
+ * terminal and no HTML renderer breaks a line on U+2028, so it is not structure in any output
+ * edfcore produces, and replacing it would be replacing a character an annotation legitimately
+ * contains. The rule is about what the OUTPUT treats as structure, not about what a language
+ * specification calls a line terminator.
  */
 /** Every C0 control character and DEL becomes `.`; everything else is returned unchanged. */
 export declare function printable(text: string): string;

package/dist/text/printable.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"printable.d.ts","sourceRoot":"","sources":["../../src/text/printable.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AAEH,6FAA6F;AAC7F,wBAAgB,SAAS,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,CAO9C"}
+{"version":3,"file":"printable.d.ts","sourceRoot":"","sources":["../../src/text/printable.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgCG;AAEH,6FAA6F;AAC7F,wBAAgB,SAAS,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,CAO9C"}

package/dist/text/printable.js

@@ -21,6 +21,15 @@
  * Only C0 and DEL are replaced. Latin-1 letters above 0x7f are ordinary characters in an
  * electrode label written on a European system, and 0x80-0x9f are left alone because edfcore
  * decodes headers as ISO-8859-1, where that range is not control characters.
+ *
+ * That argument covers header text, which is Latin-1 and therefore stops at U+00FF. It is not the
+ * only thing printed through here: ANNOTATION text is UTF-8, so `U+2028 LINE SEPARATOR` and
+ * anything else above U+00FF can arrive from a file — `cli-run.ts` prints it for `events` and
+ * `format-annotations.ts` for the hypnogram. Those pass through unchanged, deliberately. No
+ * terminal and no HTML renderer breaks a line on U+2028, so it is not structure in any output
+ * edfcore produces, and replacing it would be replacing a character an annotation legitimately
+ * contains. The rule is about what the OUTPUT treats as structure, not about what a language
+ * specification calls a line terminator.
  */
 /** Every C0 control character and DEL becomes `.`; everything else is returned unchanged. */
 export function printable(text) {

package/dist/text/printable.js.map

@@ -1 +1 @@
-{"version":3,"file":"printable.js","sourceRoot":"","sources":["../../src/text/printable.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AAEH,6FAA6F;AAC7F,MAAM,UAAU,SAAS,CAAC,IAAY;IACpC,IAAI,GAAG,GAAG,EAAE,CAAC;IACb,KAAK,MAAM,SAAS,IAAI,IAAI,EAAE,CAAC;QAC7B,MAAM,IAAI,GAAG,SAAS,CAAC,WAAW,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC;QAC3C,GAAG,IAAI,IAAI,GAAG,IAAI,IAAI,IAAI,KAAK,IAAI,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,SAAS,CAAC;IACxD,CAAC;IACD,OAAO,GAAG,CAAC;AACb,CAAC"}
+{"version":3,"file":"printable.js","sourceRoot":"","sources":["../../src/text/printable.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgCG;AAEH,6FAA6F;AAC7F,MAAM,UAAU,SAAS,CAAC,IAAY;IACpC,IAAI,GAAG,GAAG,EAAE,CAAC;IACb,KAAK,MAAM,SAAS,IAAI,IAAI,EAAE,CAAC;QAC7B,MAAM,IAAI,GAAG,SAAS,CAAC,WAAW,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC;QAC3C,GAAG,IAAI,IAAI,GAAG,IAAI,IAAI,IAAI,KAAK,IAAI,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,SAAS,CAAC;IACxD,CAAC;IACD,OAAO,GAAG,CAAC;AACb,CAAC"}

package/docs/CHANGELOG.md

@@ -6,6 +6,22 @@ alone does not tell you whether you were affected.
 edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
 defect; those are called out below.
 
+## 0.4.265
+
+- **Added** the unit test `printable` never had. It is the smallest module in the package and its
+  whole content is one rule — replace the C0 controls and DEL, leave everything else — and four
+  test files mentioned it while testing something else. Nothing pinned which code points it acts
+  on, in either direction: replacing too little lets a tab invent a column in the CLI's
+  tab-separated output, and replacing too much mangles an electrode label written on a European
+  system, where `0xB5` for micro is ordinary text.
+- **Completed** the module's own argument for that rule. It justified leaving `0x80`-`0xFF` alone
+  by pointing at ISO-8859-1 header decoding, which stops at `U+00FF` — and header text is not the
+  only thing printed through it. Annotation text is UTF-8, so `U+2028 LINE SEPARATOR` really can
+  arrive from a file and reach `edfcore events`. It passes through, which is right and now says
+  why: no terminal and no HTML renderer breaks a line on it, so it is not structure in any output
+  edfcore produces. The rule is about what the output treats as structure, not about what a
+  language specification calls a line terminator.
+
 ## 0.4.264
 
 - **Widened** the guard added in 0.4.239, which enforced the narrower half of its own rule. It

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.264",
+  "version": "0.4.265",
   "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
   "keywords": [
     "edf",

package/src/constants.ts

@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
 } as const;
 
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.4.264';
+export const VERSION = '0.4.265';

package/src/text/printable.ts

@@ -21,6 +21,15 @@
  * Only C0 and DEL are replaced. Latin-1 letters above 0x7f are ordinary characters in an
  * electrode label written on a European system, and 0x80-0x9f are left alone because edfcore
  * decodes headers as ISO-8859-1, where that range is not control characters.
+ *
+ * That argument covers header text, which is Latin-1 and therefore stops at U+00FF. It is not the
+ * only thing printed through here: ANNOTATION text is UTF-8, so `U+2028 LINE SEPARATOR` and
+ * anything else above U+00FF can arrive from a file — `cli-run.ts` prints it for `events` and
+ * `format-annotations.ts` for the hypnogram. Those pass through unchanged, deliberately. No
+ * terminal and no HTML renderer breaks a line on U+2028, so it is not structure in any output
+ * edfcore produces, and replacing it would be replacing a character an annotation legitimately
+ * contains. The rule is about what the OUTPUT treats as structure, not about what a language
+ * specification calls a line terminator.
  */
 
 /** Every C0 control character and DEL becomes `.`; everything else is returned unchanged. */