# A Unicode boundary test for classical cipher exercises

A twenty-six-letter Caesar alphabet describes a rule for A–Z. It does not by itself define what should happen to accented letters, emoji or text from another writing system. A good exercise states that boundary before learners compare results from different tools.

# Build a small test set

Use the input A Z a z é 中 🙂 with a key of one. Under an explicitly ASCII-only convention that preserves letter case and leaves other characters alone, the expected output is B A b a é 中 🙂. Spaces remain spaces. The accented e is outside the declared alphabet even though it looks related to an English letter.

This is a specification for a test, not a claim about every online converter. If a tool changes the accented character, inspect its documented normalization rule before calling the result incorrect.

# Look beyond appearance

An accented character can sometimes be stored as one code point or as a base letter followed by a combining mark. The two versions may look alike but pass through a letter-by-letter implementation differently. Copy a sample into a code-point inspector when the discrepancy matters, and record the exact representation.

Do not assume a visible symbol occupies one byte. An English ASCII letter uses one UTF-8 byte, whereas many other characters use several. Counting bytes is a different exercise from counting code points or user-perceived characters.

# Compare one assumption at a time

Keep the same key and alphabet while testing punctuation, then case, then accents. Avoid changing all three at once: otherwise a mismatch has too many possible explanations. Save both the literal input and a written policy such as “shift only ASCII letters; preserve everything else.”

For an extension, ask whether the composed and decomposed versions of an accented letter should produce equivalent results. There is no single classroom answer until the intended normalization policy is stated. The important outcome is an explicit, reproducible contract rather than an undocumented guess.

# Continue the exercise

Compare your recorded assumptions with our classical cipher tools and learning guides. Keep the exact input and expected output beside the result.

Published on behalf of Caesar Cipher with AI assistance. Contact: contact@caesarcipher.org.