[Dustin-Kelley]

Why

Readers of the native Bible see a Selah pause (qs) in italic on the left of the poetry line. The pause should sit on its own italic line at the end of the line, which is the right edge in a left-to-right Bible. A pause that is already inside qr stays as it is.

What changed

• A line that contains qs keeps the poetry before the pause, and puts the pause on its own end-aligned line.
• That line reads the pause, then an attached footnote marker, then trailing punctuation. With notes on, that is Selah, the marker, then the period. With notes off, it is Selah and the period.
• Share text and footnote html still come from the verse before that split, so punctuation does not gain a space.

Scope

This covers qs in any poetry line, including q and q4. It leaves qr lines alone. It does not change the web reader.

Tradeoffs

End alignment puts the pause on the right in left-to-right text and on the left in right-to-left text. qr stays on the physical right in both directions, which is the existing rule.

Blast Radius

Native chapter text that contains a qs span. Share text still reads as one sentence, and a mark after the pause does not gain a space in front of it.

Verification

• Jest on the scripture parser and the native reader. The new pause cases failed before the fix (the period and the exclamation mark were their own lines) and pass after it. 122 tests.
• No Platform app key, so the HTML is the Bible.com verse API for Habakkuk 3:3 (https://nodejs.bible.com/api/bible/verses/3.3?id={version}&references[]=HAB.3.3). Swift pull request 297 lists these three Habakkuk 3:3 examples and does not list 3:9 or 3:13. Before is dk/native-text-poc. After is this branch.
• Bible.com calls a footnote note f and a verse number label. Those two class names were renamed to yv-n f and yv-vlbl so this reader draws a marker and a verse number. The poetry classes and the words are the Bible.com markup. Brand fonts returned 401 and fell back.

Example	Before	After
Orthodox Jewish Bible (130), Habakkuk 3:3. iOS simulator.
Orthodox Jewish Bible (130), Habakkuk 3:9 and 3:13. iOS simulator.
Orthodox Jewish Bible (130), Habakkuk 3:9 and 3:13. Android emulator.
The Passion Translation (1849), Habakkuk 3:3. iOS simulator. Before and after match because the pause line was already right-aligned.

Footnote marker

A footnote marker immediately after a Selah pause stays on the pause line, before any trailing punctuation. That is the expected behavior.

NVI Bible version was not tested — no license available for that version.

  

Confidence Score: 5/5

The PR appears safe to merge, with one previously reported, non-blocking quote-placement issue remaining.

Findings

1.  Opening quote leaves its sentence ▶

Fix with agent prompt

### Issue 1
packages/ui/src/native/scripture/parse-passage.ts:217-224
For `<span class="qs">Selah</span> "Next words"`, the new split moves the opening quote onto the Selah line. `opensFollowingWords` misses it because the following words are inside the same inline, not the next one. The uppercase check then accepts the split. Readers see `Selah"` followed by `Next words"` on another line.

Please check for opening quotes within the shared text before moving its punctuation.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Moves qs pauses onto their own end-aligned lines in the native reader.

• Selah pauses sit on their own trailing-edge line.

_{Reviews (12) · Last reviewed commit: "docs(ui): add OJB Habakkuk 3:9–3:13 Andr..." · Reviewed by Greptile}

[bmanquen]

issue (blocking): The acceptance criteria call for a visual check of Habakkuk 3:3, 3:9 and 3:13 in versions 130, 4360 and 1849. The PR shows only 3:3 in 130 and 1849. The Portuguese NVI (4360) shots were dropped in 67a2efb, and 3:9 and 3:13 are not covered. Please add those captures, or note why they are out of scope, before merging.

[bmanquen]

Three things to fix before merge, inline below. The verification gap has no code line, so here it is:

todo (blocking): YPE-6405 asks for a visual check of Habakkuk 3:3, 3:9 and 3:13 in 130, 4360 and 1849. The PR shows only 3:3, in 130 and 1849, on iOS. NVI (4360) has no license, so that gap is fine. Please add 3:9 and 3:13 in 130 and 1849, and one Android capture. The Android shot matters most, because of the RTL alignment noted inline on passage.tsx.

[bmanquen]

issue (blocking): The trailing punctuation stays on the pause line only when it is a whole text node by itself. Habakkuk 3:3 passes because its period sits alone after the qs span. When the punctuation shares a node with the words after it, the period moves to the start of the next line:

<span class="qs">Selah</span>. God shall send forth his mercy

The lines come out as ["Selah"] and [". God shall send forth his mercy"]. That breaks the ticket rule "the period after Selah [is] unchanged". A Selah in the middle of a verse, followed by more words, is common (Psalm 57:3, for example).

Suggest splitting the leading punctuation off the next text node. Put the punctuation on the pause line and leave the rest as prose. Please add a test for this shape.

[bmanquen]

issue (blocking): This now collapses and trims every verse's html, not only the Selah verses. It used to be htmls.join(' '). The change affects share and footnote HTML everywhere, and the changeset doesn't mention it.

The split doesn't need this, because collectVerses already reads the blocks before the split. Suggest keeping html: htmls.join(' ') and using joinVerseParts only for text. If the change is intended, give it a line in the changeset.

[bmanquen]

question (blocking): In RTL, end becomes a physical textAlign: 'left' next to writingDirection: 'rtl'. The comment removed here said iOS keeps an explicit left in RTL. On Android, left and right may be read as start and end under RTL, and the pause could land on the wrong edge. Has this been checked on Android with an RTL Bible? If it hasn't, this needs a capture before merge (see the summary comment).

[greptile-apps]

Opening quote leaves its sentence

For <span class="qs">Selah</span> "Next words", the new split moves the opening quote onto the Selah line. opensFollowingWords misses it because the following words are inside the same inline, not the next one. The uppercase check then accepts the split. Readers see Selah" followed by Next words" on another line.

Please check for opening quotes within the shared text before moving its punctuation.

Prompt To Fix With AI

This is a comment left during a code review.
Path: packages/ui/src/native/scripture/parse-passage.ts
Line: 217-224

Comment:
**Opening quote leaves its sentence**

For `<span class="qs">Selah</span> "Next words"`, the new split moves the opening quote onto the Selah line. `opensFollowingWords` misses it because the following words are inside the same inline, not the next one. The uppercase check then accepts the split. Readers see `Selah"` followed by `Next words"` on another line.

Please check for opening quotes within the shared text before moving its punctuation.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.