Skip to content

Main content

Marker Term Capitalization Preservation

Compare exact and Unicode-default-lowercased supplied critical terms without normalizing the returned source text.

Loading tool…

Description

Compare source and proposed tokens exactly and after JavaScript lowercasing.

Critical annotations distinguish source voices, editorial insertions, omission markers, edition locators and caller-assigned interpretations. Case preservation and half-open text offsets describe representation rather than meaning. A bracketed token or source-role label does not verify faithful quotation, authority, an argument or its historical context.

Compare source and proposed tokens exactly and after JavaScript lowercasing.

When to use this tool

Use Marker Term Capitalization Preservation when you already have sourceToken, proposedToken and need to compare source and proposed tokens exactly and after JavaScript lowercasing.

How to use the tool and how it works

  1. Enter sourceToken, proposedToken. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read exactMatch, sameIgnoringCase. Inspect exactMatch, sameIgnoringCase before interpreting the associated values.

Return sourceToken===proposedToken and sourceToken.toLowerCase()===proposedToken.toLowerCase().1

Input fieldMeaning and unitsAccepted input
sourceTokenSource TokenRequired. Text; maximum UTF-16 length 8192.
proposedTokenProposed TokenRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
exactMatchExact MatchRequired. Boolean.
sameIgnoringCaseJavaScript lowercase-string equality, not full Unicode case folding or normalization.Required. Boolean.
json
{
  "input": {
    "sourceToken": "Other",
    "proposedToken": "other"
  },
  "output": {
    "exactMatch": false,
    "sameIgnoringCase": true
  }
}

Limitations and assumptions

  • Empty tokens are accepted. This is not Unicode normalization or full case folding, locale collation, editorial approval or semantic equivalence.
  • 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.

Alternative or Complementary methods

Read the original passage and relevant edition with the stated interpretive and editorial conventions. Verify source context and attribution before reuse; local span labels and interpretation-objection pair keys organize records without evaluating the argument or granting quotation rights.

References

  1. Calculation and input contract: critical-theory/marker-term-capitalization-preservation — tool.io

Similar or alternative tools