Description
Compare one aligned manuscript token pair.
Comparative-literature annotations connect editions, passages, speakers, structural frames and count units. Literal keys and normalized lengths can support consistent records while textual meaning, translation fidelity and bibliographic authority remain matters for source-aware editorial analysis.
Compare one aligned manuscript token pair.
When to use this tool
Use Manuscript Variant Single Token Alignment when checking a supplied literary annotation, cross-edition offset or count convention.
How to use the tool and how it works
- Enter base, variant, index. Keep parallel arrays aligned. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read baseToken, variantToken, equal. Inspect equal before interpreting the associated values.
Compare one aligned manuscript token pair. Require equal-length base/variant arrays and a valid zero-based index; return both tokens and literal equality.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| base | Base | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| variant | Variant | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| index | Position under the explicit indexing convention; inspect any missing-value sentinel. | Required. Safe integer; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| baseToken | Base Token | Required. Text; maximum UTF-16 length 8192. |
| variantToken | Variant Token | Required. Text; maximum UTF-16 length 8192. |
| equal | Equal | Required. Boolean. |
{
"input": {
"base": [
"the",
"red",
"rose"
],
"variant": [
"the",
"white",
"rose"
],
"index": 1
},
"output": {
"baseToken": "red",
"variantToken": "white",
"equal": false
}
}Limitations and assumptions
- Alignment is supplied rather than inferred; spelling normalization, gaps and textual significance are not evaluated.
- 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
Inspect the source editions and their annotation/counting policy for substantive literary, translation or provenance conclusions.
References
Similar or alternative tools
- Rhyme Variant Source Tag
Create a literal rhyme-variant provenance key.
- Metrical Foot Symbol Count
Count metrical symbols recognized by a supplied vocabulary.