Skip to main content
Quality & Verification v1.0

Fact-Checking & Technical Verification

The four-tier hierarchy of standards and empirical testing used to verify all technical data on CopyCharacter.

Effective Date: 2024-09-01 Last Updated: 2026-09-12
Defined the four-tier hierarchy of authoritative technical standards and verification workflows.

The Four-Tier Hierarchy of Authoritative Sources

To maintain absolute technical reliability, CopyCharacter enforces an objective four-tier hierarchy of authority when verifying characters, encoding formulas, keyboard shortcuts, and developer documentation.

Level 1 — Primary Authority

International Standards Consortia Specifications

The definitive source of truth. Includes official specifications, machine-readable data tables, and living standards published by:

  • The Unicode Consortium: Unicode Standard 17.0 (UCD data files, UTS #51 for Emoji, UTS #35 for CLDR).
  • WHATWG: HTML Living Standard §13.5 (Named character references) and URL Living Standard.
  • IETF (Internet Engineering Task Force): RFC 3629 (UTF-8), RFC 2781 (UTF-16), RFC 3986 (URI Percent-Encoding).
  • W3C: Character Model for the World Wide Web and XML specifications.
Level 2 — Platform Authority

Official Operating System & Runtime Documentation

Used to verify keyboard shortcuts, physical input architectures, and runtime-specific font fallbacks:

  • Microsoft Developer Network (MSDN): Windows Alt code algorithms, HexNumpad registry requirements, and Windows keyboard layouts.
  • Apple Developer Documentation: macOS Option key modifier tables and Apple Human Interface Guidelines.
  • FreeDesktop.org & X11: XKB Compose key sequences and GTK Unicode hex entry protocols.
Level 3 — Empirical Verification

Direct Execution Testing

Before publishing code examples, algorithms, or byte conversion formulas, they are subjected to automated execution tests across contemporary runtimes:

  • PHP 8.2+ mbstring and IntlChar extensions.
  • Modern JavaScript engines (V8 / Node.js, SpiderMonkey, JavaScriptCore) testing String.fromCodePoint() and regex Unicode property escapes.
  • Python 3.11+ unicodedata module.
Level 4 — Secondary References

Peer-Reviewed Academic & Linguistic Manuals

Consulted strictly for historical context, writing system orthographies, and complex typographic nuances (e.g., The World's Writing Systems, Daniels & Bright; The Chicago Manual of Style). Secondary references never supersede Level 1 or Level 2 authorities.

Empirical Code & Encoding Testing

Developer guides published on CopyCharacter often demonstrate complex byte conversions, such as transforming surrogate pairs into 4-byte UTF-8 sequences. Every code snippet is tested to confirm:

  • Proper handling of Unicode boundaries (e.g. U+0000, U+FFFF, U+10000, U+10FFFF).
  • Correct detection and rejection of malformed surrogate code points (U+D800 through U+DFFF).
  • Semicolon requirement nuances in WHATWG legacy HTML entity parsers.

Operating System Keyboard Shortcut Testing

Keyboard shortcuts frequently vary based on keyboard hardware, active input locale, and operating system updates. We verify our keyboard tables across:

  • Windows 11: Testing both ANSI numeric keypad entries (with leading zero) and OEM code page entries (without leading zero).
  • macOS Sequoia: Physical testing on standard US English and localized keyboard layouts.
  • Linux / GNOME: Verifying XKB compose files (/usr/share/X11/locale/en_US.UTF-8/Compose).

Resolving Standards Discrepancies

When a legacy operating system behavior conflicts with a modern Unicode recommendation, CopyCharacter clearly documents both: we cite the canonical Unicode 17.0 property as normative, and provide explanatory notes detailing platform-specific deviations.