Latin Elision Marker

Find mechanical Latin vowel-contact candidates; poetic elision still requires scansion.

Description

Latin poetic elision may occur at word boundaries with vowel contact, but scansion determines its actual realization.

Latin poetic elision may occur at word boundaries with vowel contact, but scansion determines its actual realization.1

Find mechanical Latin vowel-contact candidates; poetic elision still requires scansion.

When to use Latin Elision Marker

Use this tool to find mechanical Latin vowel-contact candidates; poetic elision still requires scansion.

Prepare the text or observed classification indicators requested. Select explicit transcription options where applicable.

How to use Latin Elision Marker and understand its results

  1. Prepare the text or observed classification indicators requested. Select explicit transcription options where applicable.
  2. Enter text using the field table and calculation rules, then run the tool.
  3. Read elisionPairs, candidateCount. The explanation below defines the units, signs, ordering and any flags or placeholder values.
  4. If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
Input fieldMeaningValue type; see rules belowRequirement
textLatin verse textstringRequired

Paste nonblank text. Split trimmed whitespace words and find case-insensitive matching adjacent pairs; return original pairs and count.

candidate=word ends [aeiouy]m? and next starts h?[aeiouy]

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output fieldMeaningValue type
elisionPairsCandidate word pairslist of string
candidateCountCandidate countinteger; minimum: 0
json
{
  "input": {
    "text": "multum ille et terris"
  },
  "output": {
    "elisionPairs": [
      "multum ille",
      "ille et"
    ],
    "candidateCount": 2
  }
}

Limitations and assumptions

Punctuation, macrons and meter are not normalized. The pattern does not prove elision or perform scansion.

Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Greek Diacritic Analyzer: Count Greek accent and breathing marks after canonical Unicode decomposition. For a complementary task, use Inscription Letter Normalizer: Apply caller-selected mechanical V/U and I/J transcription mappings.

References

  1. Latin Elision Marker — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies