Typing Unicode Esperanto

Modern Esperanto should be displayed with its real letters: ĉ, ĝ, ĥ, ĵ, ŝ, ŭ and their uppercase forms Ĉ, Ĝ, Ĥ, Ĵ, Ŝ, Ŭ. Unicode gives each of these letters a standard digital representation, so they work across ordinary websites, documents, messages, and databases. You may use an input aid to produce them, but the finished text should contain the actual letters.

For a system-specific setup after learning the principles here, use keyboard layouts on major platforms. The exact menu names can change; the characters you need do not.

This matters grammatically as well as visually. The diacritic is part of the letter, not optional decoration: caro means “tsar,” while ĉaro means “cart.” Replacing ĉ with c changes the spelling and potentially the word.

The six letters to type

Five letters carry a circumflex; ŭ carries a breve, the small curved mark. Each has both lowercase and uppercase forms.

You do not need to memorize the code points for everyday writing. They are useful when diagnosing a website, programming an input method, or confirming that a file contains the intended characters.

The pair differs in its first letter and therefore in pronunciation and meaning. Plain c is not an “unaccented version” of ĉ.

Choose an input method, then publish Unicode

Several workflows are reliable. The best one is the method that lets you type fluently without forgetting conversion.

• An Esperanto keyboard layout assigns the six letters directly or through a modifier key. This is efficient for frequent writing.
• A compose key, dead key, or character picker builds the letter from a base letter and a diacritic. Availability depends on the operating system and selected keyboard.
• A mobile Esperanto keyboard or carefully configured long-press menu can expose the characters. Verify that ŭ, not û, is offered.
• A text replacement or converter can turn x-system sequences such as cx and ux into ĉ and ŭ. Convert before sending or publishing.
• For an isolated character, copying from a trusted palette is acceptable, though slow.

These examples are ordinary (neutral) Esperanto. The letters do not signal emphasis, foreignness, or elevated style. They simply spell the words.

A quick verification routine

After installing or enabling an input method, type all twelve forms once:

ĉ ĝ ĥ ĵ ŝ ŭ — Ĉ Ĝ Ĥ Ĵ Ŝ Ŭ

Then test them inside real words. Check especially these three traps:

1. ŭ must have a breve, not a circumflex: aŭ, not aû.
2. The mark must stay attached when you copy, search, or export the text.
3. Uppercase letters keep their diacritics: Ĝoja, not GxOJA or Goja.

The short exchange tests uppercase Ĉ, lowercase ĝ, and ordinary punctuation in context. Testing full sentences is more revealing than testing an isolated character because some applications alter text only during autocorrection or export.

Unicode composition and normalization

Most Esperanto letters can be stored either as one precomposed character or as a base letter followed by a combining mark. The two versions can look identical. For example, a visible ŝ may internally be one character or the sequence s + combining circumflex.

Well-designed software normalizes equivalent sequences before comparison. If a search inexplicably misses a word that looks correct, normalization may be the cause. For normal writing, prefer the output produced by a mature Esperanto keyboard or converter; do not manually stack floating diacritics. Detailed normalization and database behavior belong to the dedicated normalization topic.

Unicode is an encoding standard, not a font. If a box or missing-glyph symbol appears, the text may be correctly encoded while the chosen font lacks a glyph. Switch to a modern font before rewriting correct letters as plain ASCII.

Temporary fallback systems

The foundational h-system and the widely used x-system arose because correct type was not always available. They remain useful under technical constraints. The x-system maps the six letters to cx, gx, hx, jx, sx, ux; a converter can reverse those sequences reliably because x is not an Esperanto letter.

See the x-system for conversion boundaries and mixed-text hazards. That page treats the input code in detail; the goal on this page remains correct Unicode output.

In ordinary modern prose, however, these are input or fallback conventions, not parallel spellings. Write ĝis, not gxis, in a polished message when Unicode works. The Academy has explicitly framed nonstandard substitutions as technical measures for circumstances in which correct supersigns cannot be used, not as orthographic reform.

Capitalization and word boundaries

Esperanto normally capitalizes the first word of a sentence and proper names, not every content word in a heading. A diacritic never disappears because a letter is uppercase: Ĉ, Ĝ, Ĥ, Ĵ, Ŝ, Ŭ are all legitimate forms. The fact that ŭ rarely begins an ordinary Esperanto word does not eliminate uppercase Ŭ; it is needed in all-capitals text and when discussing the letter itself.

Input conversion should also respect token boundaries. Do not allow a global converter to alter email addresses, code, URLs, or unadapted foreign names containing x. Convert Esperanto fields deliberately, or review the output.

Common Mistakes

1. Omitting the diacritic because the word remains guessable. Guessability does not make the spelling correct.

2. Leaving x-system input unconverted in finished prose. The sequence is a technical code, not the displayed spelling.

3. Giving ŭ the wrong mark. Esperanto uses a breve on this letter.

4. Dropping diacritics from capitals. Uppercase is not a reason to revert to a plain letter.

5. Importing English title capitalization. This is separate from entering Unicode correctly.

Key Takeaways

• Publish the actual Unicode letters ĉ, ĝ, ĥ, ĵ, ŝ, ŭ, including their uppercase forms.
• The diacritic is part of the letter and can distinguish words such as caro and ĉaro.
• Use a keyboard, compose sequence, replacement rule, or converter, then verify real sentences.
• Ŭ takes a breve; ĉ, ĝ, ĥ, ĵ, ŝ take circumflexes.
• Treat h-system and x-system forms as constrained fallbacks or input codes, not normal finished spelling.