0.1.0-preview.9

The ninth preview fixes dictation into a note. There are no new texts for
reviewers.

Fixed

• Dictating into a note drawn as it is written no longer loses characters.
  Voice typing that delivers its words as fast keystrokes (Omarchy's Voxtype,
  a thousand a second) reached the note with about half of them missing;
  the editor had been redrawing the line and resetting the cursor after every
  key, which the system's keyboard handling could not keep up with. A line the
  browser types into is now left as it is, and the cursor is left where the
  browser put it. The Plain text editor was never affected.

Security

• proxy-addr, under Express in the example API server, is updated to 2.0.8
  for GHSA-jqcg-44mw-7w3h, and source-map-js, used while the reader is
  built, to 1.2.2 for GHSA-68fv-2mgg-jv7q. Neither is part of the reader as
  it is served. A third advisory, in sprintf-js under the test coverage
  tooling, has no fix short of a breaking downgrade and is left open.

0.1.0-preview.8

The eighth preview changes nothing you can see or hear. It brings the tools
the reader is built and tested with up to date, and closes the update
requests that were open for them. There are no new texts for reviewers.

Changed

• The tools the reader is built and tested with are updated: Vite to 8.3.2,
  tsx to 4.23.15, jest to 30.5.2, ts-jest to 29.4.14 and the Node type
  definitions to 24.19.1. Nothing in how the reader behaves changes.

0.1.0-preview.7

The seventh preview lets you select several verses and act on them as one:
quote a passage into a note as a single block under one reference, mark it,
link it, or put it on the board.

For reviewers, new texts in every language: the row of verse actions when
several verses are selected (its summary, its Select button and the names a
screen reader says), a new paragraph in Help under Marks, and the changed
Keyboard line about Enter. They are listed in
docs/plans/reader-i18n/README.md.

Added

• Several verses can be selected and acted on as one. Press a verse to add it
  and press it again to take it out; the one row of actions applies to all of
  them, and says which in words. Quote writes them into a note as one
  passage under one reference, with a verse number before each verse, and
  Link writes one link for a run of verses. The verses need not be next to
  each other: John 1:1 and 1:14 are cited as "John 1:1, 14", with a link for
  each.
• A long passage without a press per verse: press the first verse and the
  last, then Select 3-18 in the row. Holding Shift while pressing a verse
  does the same.
• From the keyboard, Enter on a verse number adds or removes that verse and
  Shift+Enter takes in every verse up to it. A screen reader hears each number
  as a toggle, and hears what is selected when it changes.
• A colour pressed for several verses marks them all, or clears them when all
  already have it. The verses stay selected, and the same colour pressed again
  puts each one back as it was, in the collection it came from if it had one.
• Canvas puts a passage on the board as one card that holds the range.
• Following a link to a range of verses points out the whole range, not only
  its first verse.

Changed

• Pressing a second verse adds it to the selection. It used to move the
  actions to that verse; to act on a different verse, press the first again
  to take it out, or close the row.
• A selected verse is shown by an outline and a filled verse number as well as
  a tint, so it does not depend on colour, and is visible in Windows high
  contrast, where it was not before.
• A verse number is named "Select John 1:2" to a screen reader. It was "Mark
  John 1:2".

Fixed

• A character could go missing from a note's title, a board's name or a long
  passage in a note when it was typed faster than the page could settle
  between keys, as a script, a dictation burst or a slow device can. A part
  of the page that had nothing to do with the field asked to be drawn again
  after every keystroke, and after fifty of those in a row the next keystroke
  was thrown away. Present since preview.6; found by the tests on a Mac.
• In Windows high contrast, the focus ring on the delete button of a
  confirmation takes the system's highlight colour. It kept the style's own
  colour there.

Security

• Three packages used while the reader is built and tested are updated for
  published advisories: brace-expansion (to 2.1.7 and 5.0.12),
  serialize-javascript (to 7.1.2) and fast-uri (to 3.1.8). None of them is
  part of the reader as it is served.

0.1.0-preview.6

The sixth preview makes room on a small phone, upright and on its side: the
menus step aside while you read, write or arrange a board. It also adds a
fourth column width, Full, and fixes the text moving when Tab is pressed
along the reading bar.

For reviewers, new texts in every language: the fourth column width in
Settings; the three buttons that show and hide a pane's menus, which a screen
reader says and the screen does not show; the switch for them in Settings;
and one sentence in Help, under Finding a passage. They are listed in
docs/plans/reader-i18n/README.md.

Added

• On a small screen the menus step aside while you read. Scrolling on through
  a chapter sends the reading bar and the search box away and leaves the
  chapter title; scrolling back a little, reaching the top, or the button at
  the end of the title brings them back. A note does the same with its picker
  row and the Notes/Canvas tabs, and a board with its bar and the tabs when
  you start to pan, drag a card or pinch. On an iPhone SE held on its side,
  scripture goes from 164 to 286 px of the screen's 375, a note's text from
  about 30 to 126, and a board from 130 to 240; upright, of 667, from 406 to
  578, about 175 to 346, and 348 to 509. The menus are never removed: they
  stay reachable by keyboard and by a screen reader, and moving focus into
  them shows them.
• On a small screen, hide the menus while reading in Settings, on by
  default. Off, the menus move only when their button is pressed.
• A fourth column width in Settings: Full. The chapter fills its pane
  instead of keeping to a centred column, which shows most when the Bible is
  maximized on a wide screen. Narrow, Normal and Wide are unchanged, and Normal
  is still the default. Under Full, a verse's actions open at the start of the
  verse rather than in the middle of the pane.

Changed

• On a phone the storage notice sits at the top of the Bible pane and scrolls
  away with the chapter, instead of staying pinned above it.
• On a phone a board's name and its zoom buttons are in a strip of their own
  under the board's bar, where they stay while the bar is away.

Fixed

• Pressing Tab along the reading bar moved the text back by most of a screen
  each time, until the chapter was at its top. The text now stays where it is.
• A verse reached with the Tab key could come to rest under the pinned chapter
  title, 37px of it covered. The title's height now counts in where focus
  comes to rest.
• On a short board, a card's Move and Size panel could leave the board's frame
  when its card was reached by keyboard or by a screen reader, which scroll
  the frame. Such a scroll now moves the view instead, and the panel is never
  taller than the board.

0.1.0-preview.5

The fifth preview adds two reading switches, so a chapter can be read as
running prose without verse numbers.

For reviewers, three new texts in every language: the two switches in
Settings and one sentence about them in Help, under Marks. They are listed in
docs/plans/reader-i18n/README.md.

Added

• Two reading switches in Settings: Start each verse on a new line and
  Show verse numbers. Off, a chapter reads as running prose without
  numbers, closer to how it was first written. They change only how the
  chapter looks: pressing a sentence still picks the verse it belongs to, and
  highlighting, quoting, linking and the canvas work as before. Japanese and
  Chinese run their verses together without a space; a comparison keeps its
  rows and numbers.

v0.1.0-preview.4 — eight styles, and fixes found by using it

The fourth preview.

Try it: https://alanroman117.github.io/Scriptura/

Eight styles, light and dark

Settings → Reading & display offers a style, chosen from tiles that each show that style, and, separately, light or dark (or follow the device).

• Five new styles:
  • Vellum: rubric-red verse numbers and small-capital titles.
  • Emerald: deep green on a jade-tinted page.
  • Slate: cool and flat.
  • Nocturne: ink-blue with gold.
  • Ember: amber on true black.
• Sepia gains a dark version, Classic is refreshed, and High contrast gains 2px edges.
• A theme chosen before carries over.

Every colour pair is measured at AAA in every style (944 pairs). Every style is tested in every appearance, under axe and on the phone's layout checks.

Fixed, from using it

• A tapped link in a note opens its passage on a phone or tablet. Found on an iPad: a tap only placed the cursor and raised the keyboard.
• A long note title or board name is shown whole. The field wraps and grows, and typing a long board name no longer pushes the buttons beside it.
• The chapter title's book name carries its Bible's language, so a screen reader uses that voice, and Japanese or Chinese names keep their own spacing in Vellum and Nocturne.

Also

• A shorter canvas bar beside the Bible: the less-used actions fold behind More.
• App icons for phones: an iPhone home-screen icon, and a maskable icon for Android.
• For developers: npm run dev:api runs from sources and needs no build.

For reviewers

New words in every language: Style and the style names, Light or dark, and the canvas bar's More. They're listed in docs/plans/reader-i18n/README.md.

Still open

• Native review of every non-English language.
• Checks by hand on real phones and with screen readers.

v0.1.0-preview.3 — notes that take shape as you write, and the canvas beside the Bible

The third preview. Notes take shape as they are written, and the canvas moves beside the Bible, sharing a pane with the notes.

Try it: https://alanroman117.github.io/Scriptura/

Notes that take shape as they are written

Markdown is drawn as it is typed, the way Obsidian's live preview works: ## becomes a heading, **word** turns bold, a quote gets its rule, and an embedded board is drawn in place. A line's symbols come back, dimmed, while the cursor is on it. Ctrl or ⌘ + click follows a [[link]].

• Japanese and Chinese typed through an input method are left undisturbed while a word is composed.
• A screen reader still hears the Markdown (##, **) on every line, so a heading is known to be one.
• Each line takes its direction from its own text, so a quoted Hebrew word runs right to left.
• Settings → Note editor → Plain text keeps the Markdown source in a plain text box. Preview now lives there only; in the live editor the note is already drawn.

The canvas beside the Bible

The pane beside the text now holds the notes or the canvas, chosen by two tabs, and either can fill the window. Building a diagram no longer means leaving the Bible, and a note and a board are one click apart. Following a card's verse brings the Bible back beside the board. On a phone the tabs sit in the notes sheet.

Every search result also has a Canvas button beside its +, which puts the verse on the open board.

Fixed

• The focus ring covered the cursor at the start of a line in the note and its title.
• With the notes or the board maximized, the page had no main landmark and no level-1 heading.
• Undo after a formatting button now undoes the formatting.

For reviewers

A few new words in every language: the note editor setting, the Notes and Canvas tabs, and the Canvas button on search results. They are listed in docs/plans/reader-i18n/README.md's checklist.

Also

• @types/node 24.13.3 → 24.13.4 (Dependabot, #12).

Still open

• A real phone keyboard (GBoard, iOS) and a screen reader on the live editor: checks by hand.
• Native review of every non-English language.

v0.1.0-preview.2 — Portuguese, Chinese, and three more Bibles

The second preview. It adds three Bibles and the three interface languages that go with them, so the reader again speaks every language it holds a Bible in.

Try it: https://alanroman117.github.io/Scriptura/

Three more Bibles

• 新标点和合本 / 新標點和合本 — the Chinese Union Version of 1919, in both scripts (cuvs, cuvt). Public domain.
• Bíblia Livre (blivre) — Brazilian Portuguese, from the Almeida line. CC BY 4.0, the first text here under that licence, and it shows its attribution beside the text.

Chinese scripture gets its own font stacks, one per script: Han characters are shared with Japanese and drawn differently in each, so a page declaring only Japanese faces would set Chinese in Japanese forms.

Three more interface languages

Português (Brasil), 中文（简体） and 中文（繁體）. The browser chooses, or Settings → Language does.

Chinese is chosen by script, not by region: a browser reporting Taiwan, Hong Kong or Macau gets Traditional, and a bare zh gets Simplified. The two Chinese catalogs are separate texts rather than a character conversion — Taiwan writes 搜尋, 設定, 儲存, 匯出, 說明 and 助理 where the mainland writes 搜索, 设置, 保存, 导出, 帮助 and 助手, and quotes with 「」 rather than “ ”.

A reader in Chinese is offered both Bibles, their own script first.

For reviewers

Each new language has its own correction form, written in it, reachable from the notice at the top of the page and from Help → "About this preview". It fills in the language and this build.

No Korean

The texts offered as "Korean Bible 1910" by eBible and CrossWire are the 개역한글판 of 1952/1961: public domain in Korea since 2012, and restored in the United States by the URAA until 2056 — the same trap as the Japanese Kougo text. docs/translations-status.md shows the verse-by-verse check, and the validator now refuses it.

Still open

Native review of every non-English catalog — that is what this preview is for — plus the checks by hand on real phones, with screen readers, and in Windows high-contrast mode.

Full changelog: https://github.com/AlanRoman117/Scriptura/blob/main/CHANGELOG.md

0.1.0-preview.1 — a preview for the translation reviewers

The first release. It is a preview for the people reviewing the reader's
interface in Spanish, French and Japanese.

Try it: https://alanroman117.github.io/Scriptura/

Added

• Eleven Bible translations in one canonical JSON format, each with a verified licence:

  • English: King James Version, World English Bible, Berean Standard Bible, American Standard Version and Young's Literal Translation.
  • Spanish: Reina Valera 1909 and Versión Biblia Libre.
  • French: Louis Segond 1910, Bible Ostervald and Bible Martin.
  • Japanese: 文語訳聖書 (Classical).

  All are in the public domain except Versión Biblia Libre (CC BY-SA 4.0).

• TypeScript packages:

  • @scriptura/core loads translations and resolves book names in any of their languages.
  • @scriptura/search and @scriptura/compare search and compare them.
  • @scriptura/validate checks the data.
  • @scriptura/api is a REST router with no framework.

  A static build of the same API gives identical JSON.

• The reader, a web app that keeps everything on the device and works offline:

  • reading, searching and comparing translations, each downloaded when wanted;
  • notes in Markdown, with quotes of and links to passages;
  • colour collections of marked verses;
  • boards that lay verses and notes out as cards;
  • export to a zip of Markdown files;
  • optional tools for AI assistants (WebMCP), which can only propose changes.

• Four interface languages: English (United States), Spanish (Mexico), French (France) and Japanese. The reader follows the browser's language, and Settings can change it.

• Accessibility. The reader's interface aims at WCAG 2.2 Level AAA. Automated checks cover it on every change.

• Asking before deleting. Deleting a note or board, and removing a card, mark or translation, first asks in a dialog that names what will go.

• The preview site on GitHub Pages. It shows a link for reporting a translation correction, and each language has its own issue form.

Not yet done

• Native review of the Spanish, French and Japanese interface text. This preview exists for it.
• Checks by hand on real phones, with screen readers, and in Windows high-contrast mode.
• Planned, not built: GraphQL, the hosted JSON API and the AWS deployment.

Reviewing the translations

1. Open https://alanroman117.github.io/Scriptura/. It follows your browser's language, or choose one in Settings → Language.
2. To report a word that is wrong or unclear, use Report a correction at the top of the page, or the same link in Help → About this preview. It opens a short form in your language, with the version filled in. The form needs a free GitHub account.

Nothing you do on the site is sent anywhere. Notes and marks stay in your browser.