Text Integrity Across Unicode, Subtitles, and Morse Conversion

Characters, code points, and graphemes are different

One emoji may contain several code points, while an accented letter may combine a base and a mark. Reversing JavaScript code units can split what users see as one character. Intl.Segmenter grapheme boundaries better preserve perceived characters.

A code-point table exposes invisible spaces, controls, combining marks, and UTF-8 bytes. It cannot prove malicious intent behind a lookalike; interpret it with provenance, context, and normalization policy.

• Use grapheme boundaries for visible-text transforms.
• Inspect bytes separately for protocols.
• Document normalization before applying it.

Shift SRT with signed, bounded time

An SRT timing line carries start and end with millisecond precision. Apply the same signed offset to both, clamp below zero, preserve text lines, and show an error when no valid timing line exists.

A constant shift fixes only a start offset. Frame-rate mismatch or progressive drift requires measurements at the beginning, middle, and end, and may require linear time scaling.

Disclose loss in alphabet conversions

International Morse supports Latin letters, digits, and limited punctuation. Unsupported Turkish, German, or Chinese characters should be marked rather than silently dropped. Explicit letter and word separators enable round-trip checks.

Decode the result again in the target environment. For emergency, accessibility, or safety-critical use, a browser converter is educational pre-checking; follow the authoritative procedure.