Talk:Unicode


308 characters not mentioned

The only detail for Unicode 1.0.1 is about 20902 CJK Unified Ideographs added, but in total 21204 characters were added and 6 were removed. In total, 308 characters were not mentioned at all. Did I miss something while reading the page? What happened to those characters? Can somebody at least explain to me? Apologies in advance if I wasted your time. Mucksrunt (talk) 13:31, 26 August 2024 (UTC)[reply]

The Unicode 1.0.1 changes were messy. They brought Unicode into alignment with ISO 10646 and happened prior to the stability policies in place today. I don't come up with 308 characters but looking through the infoboxes for the various Unicode blocks (which I beleive are accurate), I find these changes with Unicode version 1.0.1:

Input requested on Unicode block template redesign

Hey! On a lark, I decided to try a minor redesign of the Unicode block templates while fixing the pressing issue of dark mode support—see Wikipedia:Village pump (technical)#Unicode block template and tell me any thoughts you have, as I think it's probably worthwhile to at least refresh these templates. Remsense ‥ 论 15:44, 11 September 2024 (UTC)[reply]

I have two concerns on your proposed redesign: First, the link to the Unicode PDF chart is no longer obvious to the reader as it's now a reference as opposed to being clear in the chart heading. Easy access to the PDF is especially important for not widely supported code ranges. Second, consolidating the notes onto a single line is OK for most of the cases but will be harder to understand for charts with longer notes like Template:Unicode chart Hangul Jamo. DRMcCreedy (talk) 17:41, 11 September 2024 (UTC)[reply]
Moving to a reference wasn't my idea directly, as I can see it either way. Per your second point, I would actually handle this by adding additional lines for those extra notes. Remsense ‥ 论 17:53, 11 September 2024 (UTC)[reply]
@Drmccreedy I think I've finished iterating on the design for now in response to feedback here and at the Village Pump—I'm still not totally sure how/whether to display the default footnote and the PDF code chart reference, but other than that I think it's just about ready to consider deploying. Any further thoughts? Remsense ‥ 论 05:01, 13 September 2024 (UTC)[reply]

Unicode BMP Status

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

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

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]

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.