Ken Whistler wrote as follows.
> A flag emoji is represented via a character sequence -- in this particular
> case by an emoji tag sequence, as specified in UTS #51.
> The representation of flag emoji via emoji tag sequences is *OUT OF SCOPE*
> for both the Unicode Standard and for ISO/IEC
In Unicode® Technical Standard #51 Unicode Emoji there is the encoding for the
Welsh flag.
This is in the section
http://www.unicode.org/reports/tr51/#Sample_Valid_Emoji_Tag_Sequences
In the Status section near the start of the document is the following.
quote
A Unicode Technical Standard
In the minutes of the recent meeting of the Unicode Technical Committee,
document http://www.unicode.org/L2/L2018/18272.htm there is the following.
quote
E.2 Proposal to add characters from legacy computers and teletext to the UCS
[Ewell, et al, L2/18-275R]
On phone: Doug Ewell.
Discussion.
Janusz S. Bien wrote:
> Last but not least, let me remind that the thread was started by a question
> what is the most convenient way to describe the properties of PUA characters.
>From what I have learned during the time period of the discussion it seems to
>me that using JSON would be a good
Hi
I have now found the following document.
http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf
William Overington
Friday 31 August 2018
Original message
>From : wjgo_10...@btinternet.com
Date : 2018/08/31 - 21:43 (GMTDT)
To : m...@kli.org, unicode@unicode.org
Hi
Thank you for your posts from earlier today.
Actually I learned about JSON yesterday and I am thinking that using JSON could
well be a good idea.
I found a helpful page with diagrams.
http://www.json.org/
Although I hope that a format of recording information about the properties of
Asmus Freytag wrote:
> There are situations where an ad-hoc markup language seems to fulfill a need
> that is not well served by the existing full-fledged markup languages. You
> find them in internet "bulletin boards" or services like GitHub, where pure
> plain text is too restrictive but the
James Kass wrote:
> Non-conformant? Well, it's probably overkill anyway. A simpler method of
> identifying which PUA convention is being used for a file
would be to either have the first line of the file being something like
[PUA1] or to have the file name be something like
Hi
Mark E. Shoulson wrote:
> I'm not sure what the advantage is of using circled characters instead of
> plain old ascii.
My thinking is that "plain old ascii" might be used in the text encoded in the
file. Sometimes a file containing Private Use Area characters is a mix of
regular
James Kass wrote:
> If a user has thousands of files using PUA characters, and all the files are
> using the same PUA convention, why would each file need to contain metadata
> for each PUA character used within? (Rhetorical)
Because each such file would then be self-contained and
ss...@gmail.com,
richard.wording...@ntlworld.com, m...@kli.org, beckie...@gmail.com,
verd...@wanadoo.fr
Subject : RE: Private Use areas
That sounds like a non-conformant use of characters in the U+24xx block.
Peter
From: Unicode On Behalf Of
William_J_G Overington via Unicode
Sent
Hi
How about the following method.
In a text file that contains text that uses Private Use Area characters, start
the file with a sequence of Enclosed Alphanumeric characters from regular
Unicode, that sequence containing the metadata relating to those Private Use
Area characters as used in
Julian Bradfield wrote:
> Not that I want to hear any more about William's unmentionables; I just wish
> emoji were equally unmentionable.
Well, as you mention them perhaps the moderator will allow the following,
particularly as it relates to Japanese and Japanese has been mentioned
elsewhere
Hi
An approach that you might like to consider in relation to fonts is that it is
possible to have in a font a Description field that consists of plain text.
It is stored twice in the font, in two different ways, one of which is just
plain text, possibly just ASCII.
So if you had text such as
Doug Ewell wrote:
> Yes, you run the risk of someone else's PUA implementation colliding with
> yours. That's why you create a Private Use Agreement, and make sure it's
> prominently available to people who want to use your solution. It's not like
> there are hundreds of PUA schemes anyway.
James Kass wrote:
> Quoting from:
> http://www.unicode.org/emoji/proposals.html
> "◦Simple words (“NEW”) or abstract symbols (“∰”) would not qualify as emoji."
Well, that is quite clear. In order for abstract emoji to become encoded, that
rule would need to be either removed, or made waivable
May I mention please a situation that may be of interest as indicative of some
of the issues with the present system.
In the discussion after the end of the lecture “Unicode Emoji: How do we
standardize that je ne sais quoi?” at the Internationalization & Unicode
Conference 39 conference in
James Kass wrote:
> ... the ESC may simply be overwhelmed with such documents, some of which were
> probably written in crayon.
Maybe a document written in crayon is so that the author can wax lyrical: is it
fair to chalk the author off? :-)
https://en.oxforddictionaries.com/definition/crayon
Hi Markus
> I would not expect for Ä+combining () above = Ä᪻ to look right except with
> specialized fonts.
I had a go making a font this afternoon (that is, afternoon United Kingdom
time) and I am pleased with the result.
As well as with a capital A the two combining characters also work
Janusz S. Bien wrote:
> You seem to assume that my concern is only rendering.
Well my thinking is that what you are wanting is a way to accurately transcribe
documents and maybe printed books from Old Polish into a Unicode-based
electronic format so that the information can be more readily
WJGO >> My suggestion is to use for each desired glyph a sequence consisting of
three characters, and then have an OpenType font decode them so that the glyph
can be displayed.
JSB >This is a prohibitive requirement, because for years there is the lack of
font creators interested in old
Janusz S. Bien wrote:
> I understand there is no sufficient demand for the Unicode Consortium
> maintaining a supplementary non-ideographic variation database. Hence for the
> time being a kind of Private Use variation database seems to be the only
> solution - am I right?
Well, with the
Hi
> I ask the question because there are now several historical corpora of Polish
> under development, which use at present a kind of fall-back or some other ad
> hoc solutions for "nonce glyphs", as they are called in the FAQ.
I wonder if you could say please what are the "kind of fall-back
Thank you for your reply.
John H. Jenkins wrote:
> Memoji are not merely animated emoji; they are personalized avatars.
Some more information about that would be appreciated please. In particular I
am wondering how they are transmitted from one end user to another end user.
For example, is
I have seen the following video.
https://www.youtube.com/watch?v=CjqERCCD4iM
How will memoji be communicated from one device to another?
What happens if a message containing a memoji gets into a web page, such as in
the archives of this mailing list?
So, I am wondering whether memoji will
> The topic of localizable sentences is now closed on this mail list.
> Please take that topic elsewhere.
> Thank you.
May I please mention, with permission, that there is now a thread to discuss
the issue of translations and their context that was mentioned?
I have been reading through the document.
I am wondering if the way forward would be to use a different technique and
instead to encode images directly using vector graphics.
For example, as in the paper that starts at page 21 of IBA Technical Review 20.
IBA was the Independent Broadcasting
Hi Marcel
> I don’t fully disagree with Asmus, as I suggested to make available
> localizable (and effectively localized) libraries of message components,
> rather than of entire messages.
Could you possibly give some examples of the message components to which you
refer please?
Asmus wrote:
Steven R. Loomis wrote:
>Marcel,
> The idea is not necessarily without merit. However, CLDR does not usually
> expand scope just because of a suggestion.
I usually recommend creating a new project first - gathering data, looking at
and talking to projects to ascertain the usefulness of common
Otto Stolz wrote:
> I wonder how English and French ever could be made to use a single script,
> let alone German (“ß”), Icelandic (“þ”), Swedish (“å”), Latvian (“ē”), Chech
> (“č”) or – you name it.
Years ago I used to hand set metal type - letterpress printing was a family
hobby.
For a
Years ago this mailing list had some wonderful long discussions.
A similar such discussion may be interesting now on the topic of Colours - both
for emoji and otherwise, as recent developments could possibly be leading
towards a major change in Unicode.
A few days - including a weekend -
One possibility that might be worth consideration is to map each otherwise
unmapped glyph in the font each to a distinct code point in the Private Use
Area. This being as well as all of the automated glyph substitution, not
instead of it.
This is not an ideal solution and may be regarded by
Doug Ewell wrote:
> Martin J. Dürst wrote:
>> Please enjoy. Sorry for being late with forwarding, at least in some
>> parts of the world.
> Unfortunately, we know some folks will look past the humor and use this
as a springboard for the recurring theme "Yes, what *will* we do when
Unicode
I have been thinking about issues around the proposal.
http://www.unicode.org/L2/L2018/18080-accessibility-emoji.pdf
There is a sentence in that document that starts as follows.
> Emoji are a universal language and a powerful tool for communication,
It seems to me that what is lacking
I have been looking with interest at the following publication.
Proposal For New Accessibility Emoji
by Apple Inc.
www.unicode.org/L2/L2018/18080-accessibility-emoji.pdf
I am supportive of the proposal. Indeed please have more such emoji as well.
In relation to the two dogs.
My own (limited)
Helena Milton asks:
> Greetings. Is there a way to know which font and font size have been used in
> the Unicode charts (for various writing systems)? Many thanks!
Yes, download the PDF (Portable Document Format) code chart document to local
storage.
Open the file in Adobe Reader.
Right
I have learned this evening (I am in England where it is nearly 8pm as I write
this note) that today, Thursday 30 November 2017, is the first International
Digital Preservation Day.
I have searched on the web and found lots of links about International Digital
Preservation Day.
William
A digit with a bar over the top is used to express the common logarithm of a
number that is both greater than zero and also less than one.
https://en.wikipedia.org/wiki/Common_logarithm
William Overington
Tuesday 26 September 2017
Original message
>From : unicode@unicode.org
Date :
Richard Wordingham wrote:
> Just steer them away from UTF-16! (And vigorously prohibit the very concept
> of UCS-2).
UTF-16 is very useful. I use it in my research project.
If the byte content of a UTF-16 file is displayed in a hexadecimal display then
for all plane 0 characters the byte
Asmus Freytag wrote:
> Philippe,
> thank you for your earnest efforts at explaining away a joke.
> I'm sure I'm speaking for the assembled congregation in applauding you for
> your tireless energy in setting the record straight.
Well, as Asmus is purporting to speak
> for animal in animalKingdom:
> createEmojiProposal(animal)
Did you miss a semicolon off the end of that!? ☺
> Emoji are a veritable Pandora box.
Is there an emoji for that!?
The name Pandora reminded me that an electric locomotive was named Pandora. So
I searched and found that a more recent
I have been thinking about having Turtle Graphics Emoji as an educational and
fun idea.
Turtle Graphics Emoji would each be for one turtle graphics command, such as
forward, right and left and then there could be digits in a text message after
the emoji character to act as the parameter to the
An issue that seems to be coming into prominence is that as a result of the
requirement that emoji proposals should not be overly specific, some recent
proposals seem to be trying to emphasise that they are not overly specific by
suggesting that the particular emoji proposed could mean various
Around 1991 I was shopping in a supermarket and I noticed some product that I
was buying had its ingredients list in a lot of languages.
I have been interested in typography and languages since the 1960s. During the
1960s I was given a copy of the Riscatype Accents Catalogue.
A page of
Here is a mnemonic poem, that I wrote on Monday 20 February 2017, now published
as U+1F91F is now officially in The Unicode Standard.
One eff nine one eff
Is the code number to say
In one symbol
A very special message
To a loved one far away
In an email
Or a message of text
I have been reading the following document.
http://www.unicode.org/L2/L2017/17192-response-cmts.pdf
Comments in response to L2-17/147
To: UTC
From: Peter Edberg & Mark Davis, for the Emoji Subcommittee
Date: 2017 June 15
For convenience, here is a link to the L2-17/147 document.
Martin J. Dürst > Sorry to be late with this, but if 20.1 bits turn out to not
be enough, what about 21 bits?
Martin J. Dürst > That would still limit UTF-8 to four bytes, but would almost
double the code space. Assuming (conservatively) that it will take about a
century to fill up all 17
I am concerned about emoji ZWJ sequences being encoded without going through
the ISO process and whether Unicode will therefore lose synchronization with
ISO/IEC 10646.
I have raised this by email and a very helpful person has advised me that
encoding emoji sequences does not mean that Unicode
Ken Whistler wrote:
> I suggest the following:
> 10BEDE for an English flag (reminding one of Bede the Venerable)
> 10CADF for a Welsh flag (harking to Cadfan ap Iago, King of Gwynedd)
> 10A1BA for a Scottish flag (for Alba, of course)
> Surely those would work for you!
Thank you for your
Richard Wordingham wrote:
U+1F3F4 U+E0067 U+E0062 U+E0065 U+E006E U+E0067 U+E007F (English flag)
I looked at that and I realized that although I had effectively seen that
encoding in http://www.unicode.org/reports/tr51/tr51-11.html though expressed
differently, it was only when I saw
On Saturday 8 April 2017 I wrote:
> I have made an OpenType font that implements Michael's proposed format and
> the extension of having variation selectors for the border units that Michael
> kindly added during the discussion.
> I have published the font and the font is available, free, from
51 matches
Mail list logo
