From 1e10fd34ed32b479704b86714ad193f36377e27d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christoph=20P=C3=A4per?= Date: Mon, 1 May 2017 10:48:31 +0200 Subject: [PATCH] draft text --- latin-letter-components.md | 92 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 latin-letter-components.md diff --git a/latin-letter-components.md b/latin-letter-components.md new file mode 100644 index 0000000..5ecb825 --- /dev/null +++ b/latin-letter-components.md @@ -0,0 +1,92 @@ +Proposal to Add Characters for the Components of Latin Lowercase Letters to the Unicode Standard +====================================================== + +- **Author:** Christoph Päper +- **Mail:** christoph.paeper@crissov.de +- **Submitted:** 2016-[__]-[__] + +Introduction +------------ + +I hereby request the addition of a [______] emoji to the Unicode Standard. Rationals, glyph examples, character properties as well as discussion of inclusion and exclusion factors are included on the following pages. +As per emoji submission guidelines (http://www.unicode.org/emoji/selection.html#submission) this document does not include the character proposal form. + +Glyph and Design +---------------- + +Description + +![Sample Picture](.png) + +Character Properties +-------------------- + +The preferred name of the character is “[______]”. It should be added to the [______] block near other [______] emoji. Properties of the [______] emoji should be identical to those of other emoji. + +* General Category: Other Symbol (So) +* Canonical Combining Class: 0 +* Bidirectional Class: Other Neutral (ON) +* Bidi Mirrored: No + +No case-mapping is required. The character does not decompose in any way. It is not whitespace nor a control character. It has no numeric value. It does [NOT|] make use of emoji modifiers. It has [TEXT|EMOJI] presentation by default. In collation order it should be sorted near other [______] emoji. It should definitely be part of the [______] category. + +Factors for Inclusion +--------------------- + +### A. Compatibility: + +There are no known legacy character sets containing [______]. + +### B. Expected Usage Level: + +I have included several charts supplied by Google Trends showing the frequency of searches for “[______]” in comparison to other emoji. + +Google search for the term “[______]” returns [______] results, which is more than for [______]. + +### C. Image distinctiveness: + +... + +### D. Completeness: + +... + +### E. Frequently Requested: + +... + +Factors for Exclusion +--------------------- + +### F. Overly Specific: + +... + +### G. Open-ended: + +... + +### H. Already Representable: + +... + +### I. Logos, Brands etc. + +... + +### J. Transient: + +... + +References +---------- + +[1] ______: ______ (______) + +License +------- + +The sample images and the sample font included in this proposal were created by me and me alone. I hereby declare that the Unicode Consortium and its members are granted the right to use, edit and redistribute these contents in any way they want without restriction. +Copies of the sample images and font are available at the following address: + +Screenshots were taken from Google Trends (https://www.google.com/trends/) and Twitter (https://twitter.com).