summaryrefslogtreecommitdiffhomepage
path: root/README.md
diff options
context:
space:
mode:
authorRalph Amissah <ralph.amissah@gmail.com>2026-09-25 20:49:49 -0400
committerRalph Amissah <ralph.amissah@gmail.com>2026-09-25 20:49:49 -0400
commitead2f79ee41db99a292d763fe41f0613a74ef7b3 (patch)
treef8ee798e50161aa30b650db7a531f174672d08cb /README.md
parent--validate, and a second reader, in Gleam (diff)
a blank first text line was being lost
An object whose first text line is blank lost it. The parser decided whether to start a new line by asking whether the accumulated text was empty, which is not the same question as whether a text line has been seen: for an object opening on a blank line the first line left the text empty and the second overwrote it rather than appending. Seven documents of the markup document samples have verse opening on a blank line, and in every one of them the blank was dropped, so the html, the plain text and the JSONL chunks all began the verse a line early. Spine's own text output has the blank line; this now matches. Found by loading one document as .ssp and as .ocda.db and comparing the two models object by object, which is what sisudoc-ocda-lib exists to do. The comparison between the two .ssp readers had not caught it, being on section counts, which the defect does not disturb. Also: the repository is named sisudoc-ssp-reader, prefixed as every repository of this project's own is (binary, package and module names are unchanged), and the sources follow the specification directory's name, sisudoc-abstraction-format. And the /+ ↓ +/ comment arrows in ssp_parser.d, double-encoded by the in-place edit that applied the fix, are restored; comment text only. (assisted by Claude-Code)
Diffstat (limited to 'README.md')
-rw-r--r--README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/README.md b/README.md
index eba8c42..34a2dc6 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-# ssp-reader
+# sisudoc-ssp-reader
Readers for the **`.ssp`** document abstraction, the object-centric
document abstraction written as text, which `sisudoc-spine` emits and
@@ -18,7 +18,7 @@ These are not three tools that happen to share a name. They are **the same
specification implemented more than once**, and the interesting thing about
them is that they agree.
-Each was written from the format specification, `doc-abstraction-format`,
+Each was written from the format specification, `sisudoc-abstraction-format`,
rather than from spine's emitter or from each other. Run over the 36
document reference collection, **the D and Gleam readers agree on the
section counts of all 36**.
@@ -54,7 +54,7 @@ README. Neither depends on the other.
## The format
-Specified in **doc-abstraction-format**: `ocda-model.md` for the model both
+Specified in **sisudoc-abstraction-format**: `ocda-model.md` for the model both
serialisations share, `ssp-format-specification.md` for this one, and
`ocda-db-format-specification.md` for the sqlite form.