I wrote:
> As others have stated, it was easily demonstrated that applications
> existed in Japan which required a single code point for the era name.
> That is what necessitated the acceptance, let alone fast-tracking, of
> U+32FF SQUARE ERA NAME REIWA.
Well, this is what I've heard, anyway.
On Mon, 30 Sep 2019 01:32:02 -0700
Asmus Freytag via Unicode wrote:
> On 9/30/2019 1:01 AM, Andre Schappo via Unicode wrote:
>
> On Sep 27, 1 Reiwa, at 08:17, Julian Bradfield via Unicode
> wrote:
>
> Or one could allow IDS to have leaf components that are any
> characters, not just
SMALL CAL TRIGRAPH and millimol as HALFWIDTH LATIN SMALL LETTER M + HALF WIDTH LATIN SMALL MOL TRIGRAPH.
Marius Spix
Gesendet: Montag, 30. September 2019 um 10:32 Uhr
Von: "Asmus Freytag via Unicode"
An: unicode@unicode.org
Betreff: Re: On the lack of a SQUARE TB glyph
On 9
On 9/30/2019 1:01 AM, Andre Schappo via
Unicode wrote:
On Sep 27, 1 Reiwa, at 08:17, Julian Bradfield via Unicode wrote:
Or one could allow IDS to have leaf components that are any
characters, not just ideographic characters, and then one could
> On Sep 27, 1 Reiwa, at 08:17, Julian Bradfield via Unicode
> wrote:
>
> Or one could allow IDS to have leaf components that are any
> characters, not just ideographic characters, and then one could have
> all sorts of fun.
I do like this idea.
Note: This is a modified repost as I
On 9/29/2019 7:42 AM, Andre Schappo via
Unicode wrote:
Or one could allow IDS to have leaf components that are any
characters, not just ideographic characters, and then one could have
all sorts of fun.
I do like that idea
André
Fred Brennan wrote:
> The purpose of Unicode is plaintext encoding, is it not? The square TB
> form is fundamentally no different than the square form of Reiwa,
> U+32FF ㋿, which was added in a hurry. The difference is that SQUARE
> TB's necessity and use is a slow thing which happened over
> Or one could allow IDS to have leaf components that are any
> characters, not just ideographic characters, and then one could have
> all sorts of fun.
I do like that idea
André Schappo
Fred,
2 hours and 33 minutes from now (today). But you don't need to try to
synch a proposal like this to a particular script ad hoc meeting. That
group meets roughly once a month, and any new proposal coming in right
now wouldn't be on the Unicode 13.0 train, even if the UTC immediately
> * Does the existence of the legacy Adobe encoding Adobe-Japan1-6 shift the
> balance? It has a SQUARE TB at CID+8306.
The code point suggests that it was already there as early as
Adobe-Japan1-1 in 1993. The fact makes it seem certainly weird why it
hasn't been included like its fellows nearby.
On 2019-09-27, David Starner via Unicode wrote:
> On Thu, Sep 26, 2019 at 8:57 PM Fred Brennan via Unicode
> wrote:
[snip]
>> There is no sequence of glyphs that could be logically mapped, unless you're
>> telling me to request that the sequence T B be recommended for general
>> interchange as
On Thu, Sep 26, 2019 at 8:57 PM Fred Brennan via Unicode
wrote:
> The purpose of Unicode is plaintext encoding, is it not? The square TB form is
> fundamentally no different than the square form of Reiwa, U+32FF ㋿, which was
> added in a hurry. The difference is that SQUARE TB's necessity and use
On 2019-09-27 5:15 AM, Fred Brennan via Unicode wrote:
I only have two lingering questions.
* Does the existence of the legacy Adobe encoding Adobe-Japan1-6 shift the
balance? It has a SQUARE TB at CID+8306.
https://www.adobe.com/content/dam/acom/en/devnet/font/pdfs/5078.Adobe-Japan1-6.pdf
I'm sorry to write twice to the list but after some discussion on Twitter it
is certain I'm going to write a request.
I only have two lingering questions.
* Does the existence of the legacy Adobe encoding Adobe-Japan1-6 shift the
balance? It has a SQUARE TB at CID+8306.
On Friday, September 27, 2019 3:56:39 AM PST Ken Whistler wrote:
> On 9/26/2019 4:21 AM, Fred Brennan via Unicode wrote:
> > There is a clear demand for a SQUARE TB. In the font SMotoya Sinkai W55
> > W3,
> > which is ©2008 株式会社 モトヤ, the glyph is unencoded and accessed via the
> > Discretionary
On 9/26/2019 4:21 AM, Fred Brennan via Unicode wrote:
There is a clear demand for a SQUARE TB. In the font SMotoya Sinkai W55 W3,
which is ©2008 株式会社 モトヤ, the glyph is unencoded and accessed via the
Discretionary Ligatures (`dlig`) OpenType feature. It has name `T_B.dlig`.
Aye, there's the
Fred Brennan wrote:
> I can't help but notice that there is no "SQUARE TB" glyph.
Marius Spix replied:
> 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.
IIRC
rg
Betreff: On the lack of a SQUARE TB glyph
Greetings,
I can't help but notice that there is no "SQUARE TB" glyph.
We have SQUARE KB, GB and MB, starting at U+3385. But no SQUARE TB?
SQUARE GB is at U+3387, and U+3388 is...SQUARE CAL, ㎈, so no space was even
left for it—not very future-
Greetings,
I can't help but notice that there is no "SQUARE TB" glyph.
We have SQUARE KB, GB and MB, starting at U+3385. But no SQUARE TB?
SQUARE GB is at U+3387, and U+3388 is...SQUARE CAL, ㎈, so no space was even
left for it—not very future-proof!
The purposes of these glyphs is, as you
19 matches
Mail list logo
