Declaring Character and Language Coverage
Declare the repertoires the font actually supports, and verify automatic estimates against its glyphs and shaping.
Codepage and Unicode Coverage
Coverage fields declare supported repertoires; they do not add missing glyphs or mappings. Use Detect codepages and Unicode-range Detect as starting points, then compare the declarations with the actual encoded glyph set.

Codepages & Languages separates available codepages from the selected declarations. This example has Windows 1252 Latin 1 selected.
Recall the Codepage filter in Font Filters and customizable .cpg/uranges.dat files in The User Data Folder and Customizable Data Files. The codepage fields describe legacy Windows character sets. Unicode-range fields describe broader block coverage. Manual or hexadecimal editing is available for specialized cases, but set bits because the font supports the repertoire, not to make it appear more complete.
If Unicode ranges are left unset, export can generate them from the font's coverage. Review the result when precise repertoire declarations matter.
Use Symbol font only for a deliberate symbol-font workflow. Its legacy character-set and cmap conventions can involve the U+F020–U+F0FF private-use range and differ from an ordinary Unicode text font. Do not enable it merely because the drawings are pictorial.
Design-language and supported-language metadata use language identifiers such as BCP 47 tags. Auto-calculation can propose values, but language support also depends on shaping, marks, and appropriate forms, not only the presence of characters.