William Overington wrote:
>
> I decided that trying to design emoji for 'I' and for 'You' seemed
> interesting so I decided to have a go at designing some.
>
> However pictures of people with arrows seemed to be ambiguous in
> meaning and also they seemed to need to be too detailed for rendering
A good compromise between human readability, machine processability and
filesize would be using YAML.
Unlike JSON, YAML supports comments, anchors and references, multiple
documents in a file and several other features.
Regards,
Marius Spix
On Fri, 31 Aug 2018 06:58:37 +0200 (CEST) Marcel Schn
isc: ""
-
cp: 0001
na1: "START OF HEADING"
name_alias:
- [SOH,abbreviation]
- [START OF HEADING,control]
props: *
Regards,
Marius Spix
On Sat, 1 Sep 2018 08:00:02 +0200 (CEST)
schrieb Marcel Schneider wrote:
> On 31/08/18 08:25 Marius
The capital ẞ (U+1E9E) has been officially approved by the Council for the
German Language since July 2018. However, there is no word starting with ß,
that means the character is only relevant for full-capitalized words. It may
only stand alone in spaced type, when there is no available italic f
Dear Mark,
I found another sample here:
https://www.marketscreener.com/BRILL-5240571/pdf/61308/Brill_Report.pdf
On page 86 it says that the aleph with diaresis is a number with
the value 1000.
See also the attached clipping.
A second source is the Brown-Driver-Briggs Hebrew-English Lexicon of t
The Wikipedia page states, U+0310 is a general-purpose combining
diacritical mark. I would treat it similar like U+0308 (COMBINING
DIAERESIS) or U+030C (COMBINING CARON), which are both characters with
multiple names and different meanings depending on the script and the
language. The main benefit
Unicode characters are already using a technique called hatching.
For example LARGE RED CIRCLE (U+1F534) has thin vertical stripes, which is recognized as red.
See also: https://en.wikipedia.org/wiki/Hatching_(heraldry)
Gesendet: Dienstag, 30. April 2019 um 21:17 Uhr
Von: "Hans Åberg v
Combining Grapheme Joiner (U+034F) is probably what you want as it is default
ignorable and keeps the acute on top of the E. However it nay break languages
with di- and trigraphs or complex diacritics.
Best regards
Marius
> Gesendet: Samstag, 22. Juni 2019 um 02:14 Uhr
> Von: "Sławomir Osipiu
A few suggestions
There is a reason why the C standard library function fgetc(FILE*) returns an unsigned int instead of a char, because the constant EOF (end of file) must be outside of the definition area of a char.
Some encodings like Base64 or Quoted-printable use the escape character =
Unfortunately, the CJK Compatibility block is full, but U+321F in the Enclosed
CJK Letters and Months seems to be free. I definitely see a usage for the
proposed character.
Gesendet: Donnerstag, 26. September 2019 um 13:21 Uhr
Von: "Fred Brennan via Unicode"
An: unicode@unicode.org
Betreff: O
What about the idea to provide half-width forms for the SI prefixes and half-width forms for common units? For example, you could encode petaohm as HALFWIDTH LATIN CAPITAL LETTER CAPITAL P + HALF WIDTH GREEK CAPITAL LETTER OMEGA, gigacalories as HALFWIDTH LATIN CAPITAL LETTER G + HALF WIDTH LATIN S
Unicode has a HEAVY PLUS SIGN (U+2795) and a HEAVY MINUS SIGN (U+2796).
I wonder, if a HEAVY EQUALS SIGN could complete that character set.
This would allow emoji phrases like 🐈 ➕👨= ❤️. (man plus cat equals
love) looking typographically better, when you replace the equals sign
with a new HEAVY EQUA
So, WG2 N5058, was literally a TROLL submission.
> Gesendet: Samstag, 21. Dezember 2019 um 03:29 Uhr
> Von: "Shriramana Sharma via Unicode"
> An: "UnicoDe List"
> Betreff: Not accepted by UTC but in ISO ballot?
>
> I was looking at the pipeline for something else, and for the first
> time I see
Cecause the middle button of many mice is a scroll button, I think, we
need five different characters:
LEFT MOUSE BUTTON CLICK (mouse with left button black)
MIDDLE MOUSE BUTTON CLICK (mouse with middle button black)
RIGHT MOUSE BUTTON CLICK (mouse with right button black)
MOUSE SCROLL UP (mouse w
Unicode characters are named after their appearance, not their
semantics. For example the diaresis and the umlaut share the code-point
U+0308. A printed booklet cannot be aware if the user is right- or
left-handed. This is the same issue as with U+2BEA and U+2BEB, which
are designed for ltr and rtl
I wonder if there is any interest in adding stop words to CLDR? Stop
words are ignored by natural language processing algorithms, with use
cases like search engines, word clouds and text classification.
There are already existing collections with stop words like [1] or [2]
which could be used, but
That is a pretty interesting finding. This glyph was not part of
http://www.unicode.org/L2/L2018/18165-n4944-hieroglyphs.pdf
but has been first seen in
http://www.unicode.org/L2/L2019/19220-n5063-hieroglyphs.pdf
The only "evidence" for this glyph I could find, is a stock photo,
which is clearly ma
That glyph is coded on position U+1F5B3 OLD PERSONAL COMPUTER, see
http://users.teilar.gr/~g1951d/Aegyptus.pdf
Gesendet: Donnerstag, 13. Februar 2020 um 07:58 Uhr
Von: "うみほたる via Unicode"
An: unicode@unicode.org
Betreff: RE: Egyptian Hieroglyph Man with a Laptop
The early versions of the fon
18 matches
Mail list logo
