Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a44fb7d4ece2376a

Jump to content

Template talk:ISO 15924/unicode-chapter

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia

Issues with the new Unicode document structure

[edit]

With the release of Unicode 16.0, individual PDF chapters are gone. Instead, it's web based. For example, https://www.unicode.org/versions/Unicode15.0.0/ch09.pdf becomes https://www.unicode.org/versions/Unicode16.0.0/core-spec/chapter-9 (no PDF, just HTML). Per https://www.unicode.org/versions/Unicode16.0.0/#Core_Specification "The HTML version of the core specification is authoritative. However, for convenience of reference, an archival version of core specification is also available as a single pdf. (12 MB)". It seems excessive to link to the large, non-authoritative PDF but if that's the solution, the template will need to be updated with bookmarks, not just chapters. For example, https://www.unicode.org/versions/Unicode15.0.0/ch19.pdf becomes https://www.unicode.org/versions/Unicode16.0.0/UnicodeStandard-16.0.pdf#G45398 for Bamum (chapter 19.6). What should become of this template? Does someone want to transform it into providing HTML links instead of PDFs when the version is 16.0.0 or newer? Should the template be deprecated and a new one created that is just for HTML? I'm not sure. But I know it's not possible to easily update it for the new Unicode document structure. DRMcCreedy (talk) 22:54, 17 September 2024 (UTC)Reply