Earlier quoted context omitted.
Hmm, they did include that block for encoding arbitrary bitmap images. (U+2800)
U+2800 etc. is for Braille, which is an alphabet. Nothing to do with bitmaps.
Unicode Standard, Version 12.0
31–40 of 56 posts
Re: Unicode Standard, Version 12.0
#32Are the more fancy scripts supported by Unicode used by real people in production? By scholars? With special fonts? Or is it more like Unicode just wanting to support everything, even though the target audience is actually using something else? Asking because I'm impressed by the aim of the whole Unicode project but having no real experience with it beyond the basics.
Mostly scholars. But even if nobody at all would be using it currently, the explicit goal of Unicode is to support all scripts. Unicode is meant to make all other text encodings obsolete so the world never has to think about text encodings again (which mostly worked so far). That goal can only be reached/maintained if every script anyone might plausibly want to use is contained in Unicode.
Technically speaking Unicode is not an encoding, but otherwise your point is mostly correct.
Re: Unicode Standard, Version 12.0
#33Earlier quoted context omitted.
Perhaps Unicode could solve the emoji problem once and for all by providing a mechanism for encoding arbitrary .svgs as multi-kilobyte strings of modifier characters.
Emojis started being included in Unicode because they were already in the text encodings used by Japenese SMS. Multi-kb glyphs wouldn't exactly fly in SMS.
[0]Once they added global 3G/UMTS support their networks got SMS support, but it's only used by phone number verification services and 2FA, nobody actually sends them. Their homegrown 2G networks before that launched messaging using E-mail.
Re: Unicode Standard, Version 12.0
#34 Also in Version 12.0, the following Unicode Standard Annexes have notable modifications ⟨…⟩
UAX #14, Unicode Linebreaking Algorithm
UAX #29, Unicode Text Segmentation
UAX #31, Unicode Identifier and Pattern Syntax
UAX #38, Unicode Han Database (Unihan)
UAX #45, U-Source IdeographsRe: Unicode Standard, Version 12.0
#35Earlier quoted context omitted.
Mostly scholars. But even if nobody at all would be using it currently, the explicit goal of Unicode is to support all scripts. Unicode is meant to make all other text encodings obsolete so the world never has to think about text encodings again (which mostly worked so far). That goal can only be reached/maintained if every script anyone might plausibly want to use is contained in Unicode.
> Unicode is to support all scripts. Unicode is meant to make all other text encodings obsolete so the world never has to think about text encodings again Technically speaking Unicode is not an encoding, but otherwise your point is mostly correct.
Re: Unicode Standard, Version 12.0
#36Every top comment is about Emoji… Law of triviality in action ;) Also in Version 12.0, the following Unicode Standard Annexes have notable modifications ⟨…⟩ UAX #14, Unicode Linebreaking Algorithm UAX #29, Unicode Text Segmentation UAX #31, Unicode Identifier and Pattern Syntax UAX #38, Unicode Han Database (Unihan) UAX #45, U-Source Ideographs
How many people do you really think care about Elymaic script? Or about Nandinagari?
Re: Unicode Standard, Version 12.0
#37Re: Unicode Standard, Version 12.0
#38Earlier quoted context omitted.
Hmm, they did include that block for encoding arbitrary bitmap images. (U+2800)
U+2800 etc. is for Braille, which is an alphabet. Nothing to do with bitmaps.
(Reason for that is that the dot patterns are heavily overloaded and even language specific. German digits are different from US ones, for example)
Re: Unicode Standard, Version 12.0
#39Earlier quoted context omitted.
Do you think that the committee approving new emojis is qualified to seamlessly transition into discussing the minutiae of cuneiform formatting? It may be a guess on my part, but I'm pretty confident that there are two different (and probably non-overlapping) sets of people working on these two areas.
Of course I know this is two different committees. I'm not talking about that level of separation but splitting Unicode in Unicode proper and the emoji in another standard. Emoji standardisation is orthogonal to encoding present and past writing systems once the set of existing Japanese emoji were encoded. So it became a shit show as soon as the standard created previously non-exiting characters as emoji. In comparis…
Re: Unicode Standard, Version 12.0
#40Emojis are a plot to make English-speaking developers care about fixing their code to work with Unicode.
If only they hadn't tried to cut it down to 16 bits near the start, we could have avoided a lot of the partial support that emojis expose.
Seems strange they would miscount so grossly otherwise.