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: a40750510a98c424

Jump to content

Talk:Unicode

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 1 month ago by W.andrea in topic Page jumping on load

Unicode BMP Status

[edit]

According to the Unicode Roadmap, the status is not categorised. I’ve tried to categorise them: here’s the result:

0000-058F Most basic LTR scripts
0590-08FF RTL scripts
0900-109F Most Asian and Indian scripts and languages
10A0-10FF Georgian (unique part)
1100-167F Larger scripts, including UCAS, Ethiopic and Hangul
1680-16FF Historical scripts
1700-1CFF Most Asian scripts, somewhat European
1D00-1FFF Latin and other basic LTR scripts
2000-2BFF Set of symbols, including punctuation and math and currency
2C00-2CFF Latin, Glagolitic (I don't know how to categorize them)
2C80-2E7F African scripts and most LTR scripts
2E80-9FFF CJK scripts, including Japanese, Hangul Jamo and ideographs
A000-A4FF Asian scripts
A500-A7FF Most LTR Scripts including the Medieval, African and Asian scripts
A800-ABFF Most Asian scripts
AC00-D7FF Hangul / Korean
D800-F8FF Surrogates & Private Use
F900-FFFF Mixed scripts, especially alternative or presentation forms 

MarcoToa1 (talk) 01:57, 26 May 2025 (UTC)Reply

I'm not sure where you are going with this. It looks like original research, which isn't allowed in Wikipedia articles. DRMcCreedy (talk) 14:34, 27 May 2025 (UTC)Reply
There seems to be a table like this at BMP that is where you want to go. Spitzak (talk) 15:18, 27 May 2025 (UTC) — Preceding unsigned comment added by Banovercheckcross (talk • contribs) Reply

"Mapping to Legacy Character Sets" on Hangul

[edit]

Near the beginning of this section, it says "This is most pronounced in the three different encoding forms for Korean Hangul".

This needs clarification. Im only aware of two redundant encodings for Korean Hangul, those being the precomposed blocks and the positional jamo. Is the third such encoding the unpositioned jamo? Those characters aren't rendered in blocks by font engines, so I don't think they would count. Awelotta (talk) 04:01, 1 October 2025 (UTC)Reply

Web browser support

[edit]

In the ‘Web’ section, it says “Web browsers have supported Unicode, especially UTF-8, for many years“. Can someone tag this with {{when}}? The article is semi-protected so I cannot do so myself. ~2026-23664-53 (talk) 12:47, 17 April 2026 (UTC)Reply

Done! Thanks for pointing this out :) — W.andrea (talk) 17:46, 28 July 2026 (UTC)Reply

Page jumping on load

[edit]

The table in § Versions seems to be making the page jump on load, e.g. when going to § Architecture and terminology (permalink). To confirm, I made a sandbox without the table, and when you go to its § Architecture and terminology, the page doesn't jump.

I'm going to collapse the table as a bandage fix, but if anyone has a better solution, by all means go ahead. For example, maybe it would be better to split the section into its own article like Unicode version history.

— W.andrea (talk) 18:15, 28 July 2026 (UTC)Reply