Talk:Unicode

message: A security advisory has been recently released from two researchers, one from the University of Cambridge and the other from the same and from the University of Edinburgh, in which they assert that carefully crafted computer source code can be used to introduce vulnerabilities in apparently harmless programs. Some security groups (like the one for Rust language) are already taking measures and issuing their own security advisories.
I think that is something that affects Unicode as source code is one of the main applications of the standard. What do ye think would be a good way to introduce that to the article?
https://krebsonsecurity.com/2021/11/trojan-source-bug-threatens-the-security-of-all-code/
https://www.trojansource.codes/trojan-source.pdf
https://blog.rust-lang.org/2021/11/01/cve-2021-42574.html
Bruno Unna (talk) 12:02, 1 November 2021 (UTC)
replies: text: Looks like existing  is the place to go. Indeed, a true Unicode case (). Also consider mentioning at Bidirectional text? -DePiep (talk) 12:29, 1 November 2021 (UTC)
thread_title:  Vulnerabilities 

message: I was designing text shapes for electrical symbols and electronic elements. I design them on the Unicode-encoded FontCreator program, but after exporting it and copying and pasting the symbol I designed into the phone programs, it does not work and appears in the form of a question mark, what is the solution? (Note this topic is important for articles development, I want to design different symbols for non-electrical shapes and not only in the field of electricity and I don't want them to be thumbnails but text). Mohmad Abdul sahib talk☎ talk 18:15, 18 April 2022 (UTC)
replies: text: Likely, FontCreator has the appropriate font, containing the electric symbols. But the receiving programm does not. Looks like the font should have (Unicode block) Miscellaneous Technical. Requires downloadingf a certain font, but I cannot help any further. -DePiep (talk) 19:52, 14 July 2022 (UTC)
thread_title:  question 

message: I am adding new blocks & data to Wikidata now. Assuming no DAB needed here, the pages are:
DePiep (talk) 16:10, 13 September 2022 (UTC)
replies: text: QID added -DePiep (talk) 16:33, 13 September 2022 (UTC)

text: more listing -DePiep (talk) 18:02, 13 September 2022 (UTC)
replies: text: Not much time to complete this list, for me. DePiep (talk) 18:12, 13 September 2022 (UTC)
thread_title:  Version 15 & Wikidata 

message: A proposal is opened at WP:COMP § Taskforce WP Unicode –_proposal. Please take a look. DePiep (talk) 09:35, 2 October 2022 (UTC)
thread_title:  New Taskforce WikiProject Unicode? 

message: The offending sentence is:"The Unicode standard defines three and several other encodings exist, all in practice variable-length encodings." (Sure, you could strain to interpret that to mean "all but UTF-32", but let's keep it clear. It clearly implies all encodings are variable length. Wikipedia's own article on UTF-32 says it is fixed length. (Because it only needs to use 21 of the 32 bits for Unicode code points, it is very inefficient (and rarely used, afaik). But rarely used is not the same as "doesn't exist", and "all are variable" clearly implies it doesn't exist. I'd have to look again, are there really 3 variable Unicode encodings? I can only think of UTF-8 and UTF-16. (and some others that afaik are not "defined" in the Unicode standard (like GB18030), or that are obsolete (like UTF-7).) Replace "all" with "all common encodings" or something similar, and mention UTF-32.174.130.71.156 (talk) 11:43, 15 December 2022 (UTC)
replies: text: I think the intended meaning of this was that even if code points are fixed-size, modern Unicode is effectively variable-width, as what the user thinks is a "character" sometimes needs multiple code points.Spitzak (talk) 16:40, 15 December 2022 (UTC)
replies: text: Yes, Unicode includes both combining characters and precomposed characters, e.g., < “a” latin small letter a> < "¨" combining diaeresis> is equivalent to < "ä" latin small letter A with diaeresis>. Further, some glyphs exist at multiple code points for historical reasons. There is a discussion of cannonical forms in the Unicode standard. --Shmuel (Seymour J.) Metz Username:Chatul (talk) 21:57, 15 December 2022 (UTC)

text: It seems odd to me to describe code points as "fixed size".  They're just an abstract number.  It's when you encode (or store) the code points that you get variable lengths, at least for UTF-8, UTF-EBCDIC, and UTF-16 as described in the article. I think combining characters are a red herring for this discussion.  DRMcCreedy (talk) 23:10, 15 December 2022 (UTC)
replies: text: The Unicode standard does restrict the number of code points, so describing them as as fixed length 21-bit or 32-bit data is reasonable. Spitzak is referring to characters, which indeed are variable length, a separate issue from the length of an encoded code point that does deserve mention. --Shmuel (Seymour J.) Metz Username:Chatul (talk) 17:14, 16 December 2022 (UTC)
thread_title:  Lead is simply wrong. 

message: I object to the reversal by , citing WP:ITALICTITLE inappropriately. I'd say that the name, a noun, should not be in italics.
ITALICTITLE referst to the name of a work, ie the work itself (play, periodic, book). However, the Unicode standard is a standard, not a book &tc. not even it's publication. The Standard is abstraction: the set of rules. It is a proper noun full stop. Key is, the article title notes the subject: the standard not the book. DePiep (talk) 17:04, 21 April 2023 (UTC)
replies: text: -DePiep (talk) 10:43, 23 April 2023 (UTC)
thread_title:  Inline mentioning 

message: I don't know if it would be manageable, but Unicode clearly does not have all commonly used symbols. A simple example is the very commonly used 'slash marks' used to count. Most reading this will be familiar with the sequence /, //, ///, ////, and //// with the crossmark (strike-through) diagonal (top left to bottom right) rather than horizontal. (This is typical in the USA, I understand European convention is slightly different). I request the editors to consider the addition of a list of missing (but documented) symbols.40.142.183.146 (talk) 11:49, 9 June 2023 (UTC)
replies: text: Unicode's non-inclusion of tally marks is covered in . I don't think it's a good idea to include it also in this article. That would open the door of listing every proposal that has not yet been accepted. Indefatigable (talk) 15:42, 9 June 2023 (UTC)

text: I also oppose this idea.  The set of unencoded symbols is open-ended and may exceed the number of encoded symbols.  There would also be no way to determine which unencoded symbols merit mention. DRMcCreedy (talk) 16:01, 9 June 2023 (UTC)
thread_title:  Why no section about missing graphemes? 

message: Unicode 16 is set to release in September 2024. I think the following (con)scripts definitely need to be encoded:
* Chữ Việt Trí - an alphabet invented by Tôn Thất Chương in 2012 for Vietnamese language. It's still nicer than Latin-based Quoc Ngu and needs wide recognition as the Shavian and Hangul did.
* Add support for Quikscript.
* Add extra missing runes from Baconsthrope and Sedgeford and Armanen runes
* Possibly add something more.
94.180.80.9 (talk) 07:31, 9 July 2023 (UTC)
replies: text: Take a look at Unicode's FAQ for Submitting Successful Character and Script Proposals. Wikipedia isn't affiliated with The Unicode Consortium so requests here won't be seen or acted upon by the people who can actually add characters/scripts to the Unicode Standard. DRMcCreedy (talk) 14:39, 9 July 2023 (UTC)
thread_title:  Proposed new writing systems to be encoded into Unicode 16 

message: Welcome, I want the Kurdistan flag on my keyboard 85.94.240.91 (talk) 23:28, 2 November 2023 (UTC)
replies: text: Unfortunately, the flag of Kurdistan is not presently encoded in Unicode. Remsense聊 23:32, 2 November 2023 (UTC)
replies: text: Nor will it be added per Unicode's proposal guidelines for flags DRMcCreedy (talk) 00:34, 3 November 2023 (UTC)
thread_title:  Welcome, I want the Kurdistan flag on my keyboard  

message: In the Codespace and code points section, it refers to "the interval [0, 17 \times 2^{16})". 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 : "? The origin of the latter number is available later in the sentence (with the hexadecimal number 0x10FFFF). Alternatively, a less obscure notation might be [0, (2^{20}+2^{16}-1)]. Tarl N. (discuss) 22:55, 11 May 2024 (UTC)
replies: text: I think I was the one who originally added this. Please do replace it with something more straightforward. Remsense诉 23:10, 11 May 2024 (UTC)
replies: text: Done, using prose: ... Tarl N. (discuss) 08:01, 12 May 2024 (UTC)
thread_title:  Codespace and code points