Knowledge · Rule
Non-UTF-8 encoded content file
Package Structure · E-ENC
Definition
One of your chapter files isn't encoded as UTF-8, which can cause garbled text or validator failures on Kindle.
Why
- Chapter saved as Windows-1252 / ISO-8859-1 while XML declares UTF-8.
- Missing or conflicting charset in XML declaration vs HTTP-equiv meta.
- Copy/paste from a legacy tool that wrote a different code page.
- Binary corruption mistaken for text encoding issues (less common).
Impact
May block submission on KDP when this rule fails.
Platforms
| Platform | Result |
|---|---|
| KDP | May reject |
| Apple Books | May reject |
| Google Play | Warning |
| Kobo | Warning |
References
- EPUB / XML encoding requirements
- Cermify Rule Set kdp-epub-2026-07
Last updated · 2026-08-03
Why we believe
Provenance is loaded from RID (same source as Rule Radar) — not a second copy.
Loading provenance…