Content deleted Content added
m Reverted edit by 46.161.194.83 (talk) to last version by Annh07 |
→Codespace and code points: new section |
||
Line 147:
:::Can you work up text that concisely but accurately describes the m$ nomenclature and support for Unicode and the preferred role of UTF-16? -- [[User:Chatul|Shmuel (Seymour J.) Metz Username:Chatul]] ([[User talk:Chatul|talk]]) 18:38, 8 March 2024 (UTC)
::I agree with this. [[User:Remsense|<span style="border-radius:2px 0 0 2px;padding:3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:1px 3px;color:#000">诉</span>]] 01:41, 9 March 2024 (UTC)
== Codespace and code points ==
In the ''Codespace and code points'' section, it refers to "the interval <math>[0, 17 \times 2^{16})</math>". I had to read it several times to figure out what was meant. I originally parsed "0,17" as a European-format decimal number, which made no sense. Eventually I figured what was meant, but it wasn't at all obvious. There is nothing in the referenced Unicode 15 standard which uses that terminology, either. The use of mis-matched bracket and paren is a math construct which makes sense for real intervals, but is less commonly used in integer contexts. It will simply appear wrong to readers without a real analysis background.
May I suggest this might be more understandable replaced with "the range 0 : {{val|1114111}}"? The origin of the latter number is available later in the sentence (with the hexadecimal number 0x10FFFF). Alternatively, a less obscure notation might be <math>[0, (2^{20}+2^{16}-1)]</math>. [[User:Tarl_N.|<b style="color:green">Tarl N.</b>]] ([[User talk:Tarl N.#top|<span style="color:teal">discuss</span>]]) 22:55, 11 May 2024 (UTC)
| |||