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
5 matches
Mail list logo
