Description
Split a supplied poetic line at a code-point boundary.
Comparative literary records preserve editions, translations, source lines, rhyme classes and editorial omissions. A code-point count differs from a grapheme count, while an aligned token span depends on the supplied text and indexing convention. A source-qualified label does not establish faithful translation, authorship or an interpretation.
Split a supplied poetic line at a code-point boundary.
When to use this tool
Use Poetic Caesura Line Position when you already have lineText, boundaryCodePoints and need to split a supplied poetic line at a code-point boundary.
How to use the tool and how it works
- Enter lineText, boundaryCodePoints. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read before, after. Use the output convention below.
Require safe boundary in [0,Array.from(lineText).length]; split and rejoin the two code-point slices.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| lineText | Line Text | Required. Text; maximum UTF-16 length 8192. |
| boundaryCodePoints | Whole boundary into Array.from(lineText); counts code points rather than graphemes or UTF-16 code units. | Required. Safe integer; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| before | Before | Required. Text; maximum UTF-16 length 8192. |
| after | After | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"lineText": "Sing | muse",
"boundaryCodePoints": 5
},
"output": {
"before": "Sing ",
"after": "| muse"
}
}Limitations and assumptions
- The operation can split a grapheme cluster. No caesura, meter, word boundary, UTF-8 offset or editorially appropriate position is inferred.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Read the original passage, translation and relevant editions alongside the stated editorial conventions. Verify context, source locators and attribution when preparing quotations or comparative arguments; local string operations do not make those scholarly judgments.
References
Similar or alternative tools
- Translation Omission Span Length
Count a supplied half-open translation omission token span.
- Verse Rhyme Label Normalizer
Relabel supplied rhyme classes in first-occurrence order.