Top Tweets for #UTC154

over 8 years ago

@srl295 @rscook @Apple Here's a revised photo excerpt with one more reference… #UTC154

1

6

2

0

over 8 years ago

Courtesy of Dr. Richard Cook, and for everyone's enjoyment, here is a panoramic view of #UTC154 in full session. #Unicode11

3

13

6

0

over 8 years ago

Based on #PRI363 and its feedback, along with discussions that took place during #UTC154 last week, #UTS37 (#Unicode Ideographic Variation Database) was updated to reduce the number of encoded variants → https://t.co/DrETztj81Q

1

5

8

0

over 8 years ago

@belleveinvis @eisoch Nope. #Unicode11 issues had priority during #UTC154, and because it was only a four-day meeting, there wasn’t enough time to discuss L2/18-012. But, the submitters should read the feedback in L2/18-048, and consider preparing a revised proposal → https://t.co/0HCI8dvI0P

0

2

0

over 8 years ago

@sridatta_a @lianghai @unicode Unfortunately, there wasn’t sufficient time to discuss L2/17-276R during #UTC154, so there was an action to add it to the agenda for #UTC155. L2/18-039 recommended its encoding, so there don’t seem to be any significant barriers other than time → https://t.co/Z7fcblKc1D

1

2

0

over 8 years ago

The #Unicode11 “Beta” was just authorized at #UTC154! Stay tuned for the announcement of its availability.

0

10

7

0

over 8 years ago

A total of 84 new characters were accepted during #UTC154 for a future version of the standard. They were proposed in the following documents → L2/17-213R (1), L2/17-214R (1), L2/17-242R (6), L2/17-369 (2), L2/17-428 (1), L2/17-440 (1) & L2/18-016R (72).

1

15

9

0

over 8 years ago

Unfortunately, there wasn’t enough time during #UTC154 to discuss L2/18-013, which is my second—and more controversial—SVS (Standardized Variation Sequence) proposal, meaning that it will be discussed during #UTC155 in April/May at @Adobe’s HQ → https://t.co/Jmv4jA34dw

0

2

0

over 8 years ago

@ArmeF97 @sridatta_a @lianghai @unicode That hasn’t happened yet, but will happen before the meeting ends later today. #OnPinsAndNeedles #Unicode11 #UTC154

0

1

0

over 8 years ago

@sridatta_a @lianghai @unicode I have the 🗝 to @unicode, and am broadcasting new character or script acceptance decisions with the explicit permission of the UTC. #UTC154

1

5

0

over 8 years ago

@BabelStone @mashabow The UTC accepted this character on Tuesday, to be added to #UAX45 for #Unicode11. Also, IRG N2294, which was just posted, gives our friends in China a chance to propose it as a UNC, though I don’t feel that it rises to that level → https://t.co/ypSSgZ6fR6 #UTC154 #IRG50 🇨🇳

0

1

0

over 8 years ago

🗝 #UTC154 #Unicode11

0

2

1

0

over 8 years ago

@mexamexo8 Already discussed earlier today, but not quite ready to be accepted by the UTC. @anshumanpandey_ #UTC154

1

0

over 8 years ago

Six of the seven @creativecommons characters proposed in L2/17-242R were accepted—with changes—at #UTC154 for a future version of the standard (CIRCLED EQUALS SIGN was unified with U+229C ⊜ CIRCLED EQUALS) → https://t.co/jI5H3Mpste #CreativeCommons

0

11

7

0

over 8 years ago

The character SHARADA VOWEL SIGN PRISHTHAMATRA E in L2/17-214R was accepted at #UTC154 for a future version of the standard → https://t.co/VB9KKanJmb @a_srinidhi

1

3

5

0

over 8 years ago

The character SHARADA SIGN INVERTED CANDRABINDU in @anshumanpandey_’s proposal, L2/17-428, was accepted at #UTC154 for a future version of the standard → https://t.co/Sdvb5nw0Ju

0

2

5

0

Unicode IVD Registrar—異体字王 @IVD_Registrar

over 8 years ago

72 characters for the Dives Akuru script in @anshumanpandey_’s thorough and well-formed proposal, L2/18-016R, which was funded by the “Adopt-a-Character” program, were accepted at #UTC154 for a future version of the standard → https://t.co/UEy3ce3OOE

0

16

9

0

over 8 years ago

#PRI363 (aka Proposed Update of #UTS37) was discussed at #UTC154 yesterday, and a new version will be published soon, with minor changes based on review comments from @henryfhchan (the last two examples for the second case will be removed) → https://t.co/04hjVBMtDJ

0

4

2

0