Editorial policy

What we publish

Our pages cover Unicode characters, keyboard entry, HTML representations, spelling distinctions, and language context. The first task on a character page is practical: let the reader copy the exact character. Supporting sections explain how to type it and how to distinguish it from similar forms.

We create a separate page only when it completes a distinct task. A broad page such as N with accent helps readers compare several N forms. The focused N with tilde guide answers the narrower need for Ñ and ñ. We use the same separation for C with accent and C with cedilla.

Research and review

Technical character names and code points are checked against the Unicode Standard. Keyboard methods are checked against operating-system or software documentation when an official source is available. Language statements use authoritative language institutions, official orthography, or established reference works appropriate to the claim.

We identify the conditions that can change an instruction, including the operating system, app, input language, physical keyboard, and selected layout. We avoid presenting one shortcut as universal when its behavior depends on those conditions.

Writing principles

Visitor-facing copy is written in US English. We use the character’s technical name where precision matters and explain the everyday name people are likely to recognize. Examples are chosen to clarify a real distinction, not to fill a page with keyword variations.

Advertising, if introduced, will not determine which characters are included, how they are described, or what conclusion a page reaches. Commercial placements will remain visually separate from editorial content and interactive tools.

Corrections

Readers can report an incorrect code, shortcut, name, language example, broken link, or unclear instruction at [email protected]. A useful report includes the page address, the statement in question, and the device or app involved when relevant.

We check the report against the strongest available source and test the behavior when it can be reproduced. Confirmed errors are corrected in the source content so the web page, structured data, Markdown mirror, and future references remain consistent. A page’s review date changes only after a substantive review.

Publisher and accountability

Sören Schmidt is responsible for the published content and final editorial decisions. See sources and methodology for the verification process, accessibility for our product expectations, or contact to report a problem.