Commitment to Rapid & Transparent Correction
Accuracy is the cornerstone of CopyCharacter. While our ingestion pipelines and automated test suites validate thousands of characters, edge cases in platform keyboards, browser font fallbacks, and complex script rendering can occur.
We actively encourage developers, researchers, and typographers to notify us of any factual errors, broken code snippets, or typographical discrepancies. We investigate every report thoroughly against authoritative primary standards.
How to Submit an Error Report
To enable prompt investigation and resolution, please provide the following details when submitting a correction:
- Target URL: The exact page address on CopyCharacter where the error appears (e.g.,
https://copycharacter.com/unicode/u-2014/). - Discrepancy Description: The specific property, name, byte sequence, or keyboard shortcut that appears inaccurate.
- Authoritative Citation: The primary standard or specification supporting your correction (e.g. Unicode 17.0
UnicodeData.txtline number, WHATWG HTML entity entry, or official Apple/Microsoft documentation). - Environment (if applicable): For rendering bugs, please include your Operating System, browser version, and installed font.
Ready to Report an Issue?
Use our structured contact routing form to send your correction report directly to our technical team.
Review Workflow & 48-Hour SLA
Correction reports follow a structured review process:
A technical maintainer inspects the report and compares the claimed error against Level 1 standards sources.
If verified, the correction is applied to our relational database or template source, and the test suite is executed.
The patch is pushed to production, the server cache is purged, and the page's last updated timestamp is refreshed.
Changelog Transparency & Standards Shifts
When international consortia ratify major revisions (such as a new Unicode release or updated CLDR exemplar sets), CopyCharacter issues a formal update note in our document changelog. Non-material fixes (such as fixing a spelling typo or adjusting CSS contrast) do not alter the legal effective date of our policy documents.