Earlier quoted context omitted.
I think if you ship the font in your app to get consistent emoji renderings across platforms (no need to dump unicode for this) you might have appeased the people who want emojis to look the same on all platforms, but then you will enrage the people who want emojis on all of their apps to look the same.
So how much space will be wasted shipping a bunch of fonts that all include however many goddamned emojis there are?
Unicode 13.0
61–70 of 96 posts
Re: Unicode 13.0
#62Earlier quoted context omitted.
German, a European language that has been more or less standardized for several centuries, with a Latin-based alphabet, added a new letter (ẞ) to its alphabet in 2017. As long as that continues to happen, Unicode will have to add new characters, even if no more ancient scripts are discovered and no new writing systems are developed for currently unwritten languages.
Small precision for those who don't know the context: the Eszett (which comes from the ligature of 'ss') existed for centuries already in German writing. 2017 is just the date of its official integration in the alphabet, so it's not a 'new' letter created from scratch. I say that because I remember learning it at school a few decades ago (even if at the time we were warned the subject was touchy), and I was surprised…
ß is both visually and from its name (‘s’ ‘z’) a ligature of s and z (“Eszett” in English is “ess-zed). An ss ligature would look like a double integral sign. “Sz” seems like a better way to represent that sound, so I don’t know why it morphed into “ss”
Greek has two characters for s, one for use in the middle and one for the ends of words. English lost this in the late 18th or early 19th century (look in the Declaration of Independence for examples). German kept it longer, at least in Fraktur, which included other standard ligatures, even in handwritten text, such as ch, tz et al. The Umlaut mark can also be considered a ligature for E which is how it was originally drawn.
Re: Unicode 13.0
#63Possibly the most important addition is this: > Symbols added in this release (which aren't implemented as emojis) include a Creative Commons symbol, as well as other related glyphs for non-commercial licences, or to indicate where attribution is required. So you can now indicate license requirements, such as attribution, share-alike, or non-commercial use only. Those can apply to a vast number of works, so does nice…
(This is why there is no Apple logo or character for TAFKATAFKAP, for one thing.)
Re: Unicode 13.0
#64Possibly the most important addition is this: > Symbols added in this release (which aren't implemented as emojis) include a Creative Commons symbol, as well as other related glyphs for non-commercial licences, or to indicate where attribution is required. So you can now indicate license requirements, such as attribution, share-alike, or non-commercial use only. Those can apply to a vast number of works, so does nice…
Re: Unicode 13.0
#65Earlier quoted context omitted.
You are probably joking, but I am seriously annoyed there's no donkey emoji.
Is U+130D8 not good enough for you?
I wonder why Gardiner's descriptions never made it into Unicode? https://en.wikipedia.org/wiki/List_of_Egyptian_hieroglyphs#E
O, wait, there are censored genitalia in D block ...
Re: Unicode 13.0
#66Earlier quoted context omitted.
> So how far off is Unicode from being 'done'? Do you think human written language is ‘done’ and will never evolve?
I think that most of the changes in Unicode 13 are not from the evolution of human written language. I don't know anyone who's ever written "blueberries" by drawing a picture of some blueberries in the middle of their text.
Re: Unicode 13.0
#67> Unicode 13.0 adds 5,930 characters, for a total of 143,859 characters. These additions include 4 new scripts, for a total of 154 scripts, as well as 55 new emoji characters. So how far off is Unicode from being 'done'? At what point will they be able to stop adding characters and scripts?
[0]: https://linguistics.berkeley.edu/sei/index.html [1]: https://linguistics.berkeley.edu/sei/scripts-not-encoded.htm...
Re: Unicode 13.0
#68Possibly the most important addition is this: > Symbols added in this release (which aren't implemented as emojis) include a Creative Commons symbol, as well as other related glyphs for non-commercial licences, or to indicate where attribution is required. So you can now indicate license requirements, such as attribution, share-alike, or non-commercial use only. Those can apply to a vast number of works, so does nice…
Was it not Unicode policy not to include logos/trademarks as characters? What changed? (This is why there is no Apple logo or character for TAFKATAFKAP, for one thing.)
https://creativecommons.org/wp-content/uploads/2016/10/CC-Un...
The CC logo and icons as a matter of trademark law are governed by CC’s trademark policy, which specifies conditions of their use “in a manner reasonable to the medium and context.” According to Unicode criteria for encoding symbols, a trademark weakens, but does not disqualify, the case for encoding. As such, we would like to address this point directly, in addition to emphasizing the criteria that strengthens the case for encoding. So as to be sure there exists no misunderstanding, CC is seeking inclusion of the CC logo and icons in the Unicode standard notwithstanding that CC asserts trademark rights in its logo and icons.
The aims of Unicode and the CC trademark policy are not antagonistic to one another. It is perfectly consonant with the purposes for Unicode to allow trademarked logos and icons into its standard without jeopardizing trademark rights of the requesting organization. Especially where, as here, there is a clear and public trademark policy by the submitting organization in place that clarifies when and how the logo and icons may be used, and such marks are ubiquitous.
Though the CC logo and icons are trademarked, they are a widely-used functional marking tool that indicates permissive use as an alternative to the well-known © symbol, followed by the icons that represent those terms.
As such, they were accepted and celebrated by MoMA into its permanent collection,6 alongside universal icons such as the @ symbol and the International Symbol for Recycling—both of which are encoded in the Unicode standard. Encoding the CC logo and icons in UCS would more easily enable creators to mark their works as consistent with CC’s trademark reasonable to the medium and context, in this case within text-based editors.
Re: Unicode 13.0
#69Earlier quoted context omitted.
I suspect emojis as characters will soon be replaced with graphics. Consumers are annoyed or confused when emojis look slightly different on different platforms.
Unified rendering is not really a goal of Unicode. That's better left to the individual platform providers, who have to balance this against keeping their own user experience consistent over time and across devices.
When they were really simple icons, it made sense to treat them as characters. But today they are detailed illustrations.
Re: Unicode 13.0
#70Possibly the most important addition is this: > Symbols added in this release (which aren't implemented as emojis) include a Creative Commons symbol, as well as other related glyphs for non-commercial licences, or to indicate where attribution is required. So you can now indicate license requirements, such as attribution, share-alike, or non-commercial use only. Those can apply to a vast number of works, so does nice…
Was excited when I read your comment, but then looked at the new update and couldn't find an encircled, vertically-flipped C (i.e. copyleft licenses) among the new additions :(