LiteralKit guides

LiteralKit guides

LiteralKit guides sit beside the converters and copy boards. They explain a job that needs more than a picker: where a math operator comes from, when superscript is a footnote instead of a power, what a word-level translator will not invent, and how heart or arrow glyphs differ across fonts. They are not extra generators and they are not a blog of keyword clones.

Browse symbol guides from LiteralKit

Each of these guides links to the tool that actually copies or converts the mark. Read the guide when you need the surrounding decision; open the tool when you need a character.

What LiteralKit guides are for

These articles exist because a copyable character is easy to paste and easy to misuse. A math operator that looks right in one font can box on another. A superscript two can mean a square, an ordinal, or a footnote depending on the line around it. A heart dingbat is not the same object as a heart emoji. The essays spell those distinctions in running prose so the tool page can stay on the conversion or the board.

These articles are not a second copy of the tool. They do not install fonts. They do not run a silent lookalike engine. They do not claim that every conversion stays on the device: Shakespeare is documented on its own page as a network rewrite after Rewrite. Notation and symbol guides describe Unicode text you can copy from the matching tool, then test in the destination app.

Use the essays when you need history, compatibility, or a “when not to use this mark” warning. Use the tool directory when you already know the job. The split keeps a generator page from turning into an essay, and it keeps an essay from pretending to be a converter.

Compatibility is the usual reason to open an essay after a failed paste. A valid code point can still draw as tofu, as an emoji presentation, or as a different weight when fallback fonts mix. The guides say to test the exact character in the exact destination. They also say when to stop copying and use LaTeX, MathML, a word processor’s native superscript, or an accessible icon instead. That stop line is part of the publishing method described on About.

Word-level translator limits get their own guide because a Morse or Braille map is not a fluent language model. The translator-limits essay describes dictionary lookup, leftovers, and the jobs those pages refuse. If you need a character-by-character map, open the translator. If you need to know why a sentence will not come back as prose, stay on the guide.

Superscript and subscript uses are listed as practical jobs: powers, chemistry counts, ordinals, and compact labels in plain text. Those two essays are not a formula editor tutorial. They point at the generator when you need the mark, and they point away from the generator when the destination can encode structure properly. Heart and arrow guides do the same for glyph choice: dingbat versus emoji, lookalike versus intended mark.

New essays ship only when the extra prose earns a URL: a recurring confusion, a compatibility trap, or a use list that would crowd the tool. Duplicate essays that only change the title are refused. If a guide and a tool start to say the same sentences, the guide should drop the conversion steps and keep the decision framework.

Start with the list above. Each card is one of the LiteralKit guides in the current set. If you arrived from search looking for a converter, the related tool on that guide is the page that copies. If you arrived looking for an explanation, stay here, read the matching guide, and only then open the tool. That is the whole job of this index: put the essays in one place so the directory of tools can stay a directory of tools.

Guides on this site are short on purpose. Guides explain a decision. Guides do not convert text. Guides do not copy a character. Guides point at the tool that does. That split is why the directory of converters can stay a directory, and why these LiteralKit guides can stay essays.

A practical reading order is decision first, copy second. If you are choosing between a dingbat star and a sparkle emoji, read the star essay then open the star board. If you are choosing between a raised two and a native editor superscript command, read the superscript-uses essay then open the generator only if the destination is plain text. If you are choosing between a Morse map and a model rewrite, the translator-limits essay is the stop line: listed tokens convert; Shakespeare is the labeled exception on its own page.

Font fallback, emoji presentation, and search normalization are recurring themes across the set. They are repeated because they fail in the same way on phones, documents, and games. Testing the exact paste in the exact destination is cheaper than discovering a box after you publish. Keep a plain spelling next to a styled line when the line is a name, a password, or a citation. That advice is editorial, not a ranking trick, and it matches the leftover rule on the converters.

The index will stay short. Six essays is already a lot for a utility site. If a seventh appears, it will be because a tool page was accumulating the same explanation in three places. Until then, use the list, follow the related-tool link, and treat this page as a table of contents rather than a seventh article.

Loading interactive tools…