docs-i18nlisted

# Documents in non-Latin scripts The official document skills produce correct files, right up to the moment the text is not Latin. Then the font you specified does not contain the glyphs, and what the reader sees stops being what you asked for. In Word and PowerPoint the application substitutes some other font it finds locally, so the text renders in something you did not choose and that differs between machines. In PDF there is no substitution and the glyphs are simply missing. This is not a rendering quirk. It follows directly from the font list those skills mandate. ## The measurement Run it yourself, it needs only `fontTools`: ```bash python scripts/font-coverage.py ``` Reading the cmap table of each font named in the official skills: | Mandated font | Hebrew | Arabic | CJK | Devanagari | Thai | | --- | --- | --- | --- | --- | --- | | Arial | yes | yes | **no** | **no** | **no** | | Calibri | yes | yes | **no** | **no** | **no** | | Cambria | **no** | **no** | **no** | **no** | **no** | | Times New Roman | yes | yes | **no** | **no** | **no** | | Courier New | yes | yes | **no** | **no** | **no** | | Bookman Old Style | **no** | **no** | **no** | **no** | **no** | | Century Schoolbook | **no** | **no** | **no** | **no** | **no** | Chinese, Japanese, Korean, Hindi and Thai are unsupported by **every** font on the list. Hebrew and Arabic fail on three of the seven. Cyrillic and Greek are fine, which is why this goes unnoticed by anyone testing in a European languag