I am the author of the supplementary-test page on i18nguy.com.
The method for choosing the characters is described on the page, so isn’t a
mystery. See below.
I do not believe any of the characters are offensive, although context matters
greatly and languages evolve, so it is possible tha
I agree with Doug. Base64 maps each byte of the source string to unique bytes
in the destination string. Decoding is also a unique mapping.
If the encoded string is “translated” in some way by additional processes,
canonical or otherwise, then all bets are off.
If you disagree, please offer
Philippe,
Where is the use of whitespace or the idea that 1-byte pieces do not need all
the equal sign paddings documented?
I read the rfc 3501 you pointed at, I don’t see it there.
Are these part of any standards? Or are you claiming these are practices
despite the standards? If so, are
Philippe, quote the entire section:
In some circumstances, the use of padding ("=") in base-encoded data
is not required or used. In the general case, when assumptions about
the size of transported data cannot be made, padding is required to
yield correct decoded data.
Imple
My notes on Hebrew numbers on
http://www.i18nguy.com/unicode/hebrew-numbers.html include:
"Using letters for numbers, there is the possibility of confusion as to whether
a string of letters is a word or a numerical value. Therefore, when numbers are
used with text, punctuation marks are added
James Kass wrote:
If a text is published in all italics, that’s style/font choice. If a text is
published using italics and roman contrastively and consistently, and everybody
else is doing it pretty much the same way, that’s a convention.
Asmus Freytag responded:
But not all co
Martin,
James is making the case there is demand or a user need and that the proof is
that users are using inconsistent tactics to simulate a solution to their
problem.
The response that:
"Almost by definition, styled text isn't plain text, even if it's simulated by
something else."
is a bit
> But even most adults won't know the rules for what to italicize that
> have been brought up in this thread. Even if they have read books that
> use italic and bold in ways that have been brought up in this thread,
> most readers won't be able to tell you what the rules are. That's left
> to c
"Looking back at the history of computing, a large chunk of the
underlying technology has hit stability. ARM chips, x86 chips, Unix,
and Windows have all been around since 1985 or before, roughly 35
years ago and 35 years since the first programmed computer. They
aren't wildly changing."
I would
This thread has gone on for a bit and I question if there is any more light
that can be shed.
BTW, I admit to liking Asmus definition for functions that span text being a
definition or criteria for rich text.
I also liked James examples of the twitter use case.
The arguments against ital
AM, Tex via Unicode wrote:
Perhaps the question should be put to twitter, messaging apps, text-to-voice
vendors, and others whether it will be useful or not.
If the discussion continues I would like to see more of a cost/benefit
analysis. Where is the harm? What will the benefit to user
I am surprised at the length of this debate, especially since the arguments are
repetitive…
That said:
Twitter was offered as an example, not the only example just one of the most
ubiquitous. Many messaging apps and other apps would benefit from italics. The
argument is not based on addi
David, Asmus,
· “without external standards, then it's simply impossible.”
· “And without external standard, not interoperable.“
As you both know there are de jure as well as de facto standards. So for years
people typed : - ) as a smiley without a de facto standard and at some poi
David,
"italics has never been considered part of plain text and has always been
considered outside of plain text. "
Time to change the definition if that is what is holding you back. As has been
said before, interlinear annotation, emoji and other features of Unicode which
are now considered
Oy veh!
From: Unicode [mailto:unicode-boun...@unicode.org] On Behalf Of Mark E.
Shoulson via Unicode
Sent: Monday, April 15, 2019 5:27 PM
To: unicode@unicode.org
Subject: Emoji Haggadah
The only thing more disturbing than the existence of The Emoji Haggadah
(https://www.amazon.com/Emoji-H
What I would find useful is an emoji for when my phone falls into the toilet.
-Original Message-
From: Unicode [mailto:unicode-boun...@unicode.org] On Behalf Of Doug Ewell via
Unicode
Sent: Saturday, June 1, 2019 2:04 PM
To: unicode@unicode.org
Subject: Re: Proposal to extend the U+1F4A9
Asmus, are you including the case where an accented character maps to two
unaccented characters?
e.g. Å to AA or Ä to AE
From: Unicode [mailto:unicode-boun...@unicode.org] On Behalf Of Asmus Freytag
(c) via Unicode
Sent: Wednesday, July 17, 2019 11:07 AM
To: Norbert Lindenberg
Cc: Unicode
Now that comma ellipses (,,,) are a thing (at least on social media) do we need
a character proposal?
Asking for a friend,,, J
tex
:
On 10/6/2019 4:05 PM, Tex via Unicode wrote:
Now that comma ellipses (,,,) are a thing (at least on social media) do we need
a character proposal?
Asking for a friend,,, J
tex
I thought the main reason we ended up with the period (dot) one is because it
was originally needed for CJK-s
19 matches
Mail list logo
