Old Turkic (Unicode block)

Old Turkic
Range	U+10C00..U+10C4F; (80 code points)
Plane	SMP
Scripts	Old Turkic
Major alphabets	Old Turkic
Assigned	73 code points
Unused	7 reserved code points
Unicode version history
5.2	73 (+73)
	Note: [1][2]

In Unicode, the block Old Turkic is located from U+10C00 to U+10C4F. It is used to display the Old Turkic alphabet.

Old Turkic^[1]^[2] Official Unicode Consortium code chart (PDF)
	0	1	2	3	4	5	6	7	8	9	A	B	C	D	E	F
U+10C0x	𐰀	𐰁	𐰂	𐰃	𐰄	𐰅	𐰆	𐰇	𐰈	𐰉	𐰊	𐰋	𐰌	𐰍	𐰎	𐰏
U+10C1x	𐰐	𐰑	𐰒	𐰓	𐰔	𐰕	𐰖	𐰗	𐰘	𐰙	𐰚	𐰛	𐰜	𐰝	𐰞	𐰟
U+10C2x	𐰠	𐰡	𐰢	𐰣	𐰤	𐰥	𐰦	𐰧	𐰨	𐰩	𐰪	𐰫	𐰬	𐰭	𐰮	𐰯
U+10C3x	𐰰	𐰱	𐰲	𐰳	𐰴	𐰵	𐰶	𐰷	𐰸	𐰹	𐰺	𐰻	𐰼	𐰽	𐰾	𐰿
U+10C4x	𐱀	𐱁	𐱂	𐱃	𐱄	𐱅	𐱆	𐱇	𐱈
Notes 1.^ As of Unicode version 13.0 2.^ Grey areas indicate non-assigned code points

History

The following Unicode-related documents record the purpose and process of defining specific characters in the Old Turkic block:

Version	Final code points[lower-alpha 1]	Count	L2 ID	WG2 ID	Document
5.2	U+10C00..10C48	73	L2/00-128		Bunz, Carl-Martin (2000-03-01), Scripts from the Past in Future Versions of Unicode
			L2/06-392	N3164 (pdf, doc)	Silamu, Wushour (2006-08-14), Proposing to supplement with the special script and character for Uyghur Orkhun to ISO/IEC 10646
				N3177	Scarborough, Benjamin (2006-09-24), Response to N3164, "PROPOSING TO SUPPLEMENT WITH THE SPECLAL SCRIP AND CHARACTER FOR Uyghur Orkhun to ISO/IEC 10646"
				N3153 (pdf, doc)	Umamaheswaran, V. S. (2007-02-16), "M49.24", Unconfirmed minutes of WG 2 meeting 49 AIST, Akihabara, Tokyo, Japan; 2006-09-25/29
			L2/07-216	N3258	Silamu, Wushour (2007-02-01), Proposing to Supplement with the Special Character for Uyghur Orkhun to ISO/IEC 10646
			L2/07-015		Moore, Lisa (2007-02-08), "Action item 110-A100", UTC #110 Minutes, Follow up with the authors of L2/06-392 to better understand the script that they are proposing.
				N3353 (pdf, doc)	Umamaheswaran, V. S. (2007-10-10), "M51.29", Unconfirmed minutes of WG 2 meeting 51 Hanzhou, China; 2007-04-24/27
			L2/07-268	N3253 (pdf, doc)	Umamaheswaran, V. S. (2007-07-26), "M50.39", Unconfirmed minutes of WG 2 meeting 50, Frankfurt-am-Main, Germany; 2007-04-24/27
			L2/07-225		Moore, Lisa (2007-08-21), "C.10", UTC #112 Minutes
			L2/07-305	N3299	Silamu, Wushour (2007-09-19), Proposing to Supplement with the Special Character for Uyghur Orkhun to ISO/IEC 10646
			L2/07-325R	N3357R	Proposal for encoding the Old Turkic script in the SMP of the UCS, 2008-01-01
			L2/08-071	N3357R2	Everson, Michael (2008-01-25), Proposal for encoding the Old Turkic script in the SMP of the UCS
			L2/08-318	N3453 (pdf, doc)	Umamaheswaran, V. S. (2008-08-13), "M52.9", Unconfirmed minutes of WG 2 meeting 52
			L2/08-161R2		Moore, Lisa (2008-11-05), "Old Turkic", UTC #115 Minutes
			L2/08-412	N3553 (pdf, doc)	Umamaheswaran, V. S. (2008-11-05), "M53.09", Unconfirmed minutes of WG 2 meeting 53
			L2/08-361		Moore, Lisa (2008-12-02), "Consensus 117-C19", UTC #117 Minutes
Proposed code points and characters names may differ from final code points and names

gollark: You would still get a massive backlog if you didn't read it at the same speed it was sent, but you could use the linked cards to send it directly/only to the one computer which needs it really fast.

gollark: You would still have to spam and read messages very fast, but it wouldn't affect anything else.

gollark: There are linked cards, which are paired card things which can just directly send/receive messages to each other over any distance. If the problem here is that your data has to run across some central network/dispatcher/whatever, then you could use linked cards in the thing gathering data and the thing needing it urgently to send messages between them very fast without using that.

gollark: It would be kind of inelegant and expensive, but maybe for time- and safety-critical stuff like this you could just send the data directly between the computers which need it by linked card.

gollark: You can save cell cost by allocating item types to cells such that you fill up your cells to max "bytes" rather than max "types".

External links

"Unicode character database". The Unicode Standard. Retrieved 2016-07-09.
"Enumerated Versions of The Unicode Standard". The Unicode Standard. Retrieved 2016-07-09.

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.

[final-3] Proposed code points and characters names may differ from final code points and names

[1] "Unicode character database". The Unicode Standard. Retrieved 2016-07-09.

[2] "Enumerated Versions of The Unicode Standard". The Unicode Standard. Retrieved 2016-07-09.

[1]

[2]