Gurmukhi (Unicode block)

Gurmukhi is a Unicode block containing characters for the Punjabi language, as it is written in India. In its original incarnation, the code points U+0A02..U+0A4C were a direct copy of the Gurmukhi characters A2-EC from the 1988 ISCII standard. The Devanagari, Bengali, Gujarati, Oriya, Tamil, Telugu, Kannada, and Malayalam blocks were similarly all based on their ISCII encodings.

Gurmukhi
RangeU+0A00..U+0A7F
(128 code points)
PlaneBMP
ScriptsGurmukhi
Major alphabetsPunjabi
Assigned80 code points
Unused48 reserved code points
Source standardsISCII
Unicode version history
1.0.074 (+74)
1.0.175 (+1)
4.077 (+2)
5.179 (+2)
11.080 (+1)
Note: [1][2][3]

Block

Gurmukhi[1][2]
Official Unicode Consortium code chart (PDF)
 0123456789ABCDEF
U+0A0x
U+0A1x
U+0A2x
U+0A3x ਿ
U+0A4x
U+0A5x
U+0A6x
U+0A7x
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 Gurmukhi block:

VersionFinal code points[lower-alpha 1]CountUTC IDL2 IDWG2 IDDocument
1.0.0U+0A02, 0A05..0A0A, 0A0F..0A10, 0A13..0A28, 0A2A..0A30, 0A32..0A33, 0A35..0A36, 0A38..0A39, 0A3C, 0A3E..0A42, 0A47..0A48, 0A4B..0A4C, 0A59..0A5C, 0A5E, 0A66..0A7474UTC/1991-056Whistler, Ken, Indic Charts: Devanagari, Bengali, Gurmukhi, Gujarati, Oriya, Tamil, Telugu, Kannada, Malayalam
UTC/1991-057Whistler, Ken, Indic names list
UTC/1991-048BWhistler, Ken (1991-03-27), "III. L. Walk In proposals", Draft Minutes from the UTC meeting #46 day 2, 3/27 at Apple
L2/01-303Vikas, Om (2001-07-26), Letter from the Government from India on "Draft for Unicode Standard for Indian Scripts"
L2/01-304Feedback on Unicode Standard 3.0, 2001-08-02
L2/01-305McGowan, Rick (2001-08-08), Draft UTC Response to L2/01-304, "Feedback on Unicode Standard 3.0"
L2/01-430RMcGowan, Rick (2001-11-20), UTC Response to L2/01-304, “Feedback on Unicode Standard 3.0”
L2/05-371RSidhu, Sukhjinder (2005-11-30), Gurmukhi annotations
L2/06-008R2Moore, Lisa (2006-02-13), "C.8", UTC #106 Minutes
L2/20-055Pournader, Roozbeh (2020-01-16), Proposed sequences for composition exclusions
L2/20-015Moore, Lisa (2020-01-23), "B.13.1.1 Proposed sequences for composition exclusions", Draft Minutes of UTC Meeting 162
1.0.1U+0A4D1(to be determined)
4.0U+0A01, 0A032L2/01-431R[lower-alpha 2]McGowan, Rick (2001-11-08), Actions for UTC and Editorial Committee in response to L2/01-430R
L2/01-405RMoore, Lisa (2001-12-12), "Consensus 89-C19", Minutes from the UTC/L2 meeting in Mountain View, November 6-9, 2001, Accept the twelve Indic characters with names and coding positions as documented in L2/01-431R
L2/02-117N2425McGowan, Rick (2002-03-21), Additional Characters for Indic Scripts
L2/03-102Vikas, Om (2003-03-04), Unicode Standard for Indic Scripts
L2/03-101.4Proposed Changes in Indic Scripts [Gurmukhi document], 2003-03-04
5.1U+0A511L2/05-088RSidhu, Sukhjinder (2005-04-21), Proposed Changes to Gurmukhi
L2/05-167Sidhu, Sukhjinder (2005-08-01), Proposed Changes to Gurmukhi 2
L2/05-180Moore, Lisa (2005-08-17), "Gurmukhi (C.6)", UTC #104 Minutes
L2/05-344Sidhu, Sukhjinder (2005-10-27), Proposed changes to Gurmukhi 3
L2/05-279Moore, Lisa (2005-11-10), "C.14", UTC #105 Minutes
L2/05-384N3021Sidhu, Sukhjinder (2005-12-18), Proposal to encode Gurmukhi 3
L2/06-020McGowan, Rick (2006-01-25), Public Review Issue #82: Representation of Gurmukhi Double Vowels
L2/06-030Sidhu, Sukhjinder (2006-01-27), "E", Proposed Changes to Gurmukhi 4
L2/06-008R2Moore, Lisa (2006-02-13), "B.11.5, C.8", UTC #106 Minutes
N3103 (pdf, doc)Umamaheswaran, V. S. (2006-08-25), "M48.25a", Unconfirmed minutes of WG 2 meeting 48, Mountain View, CA, USA; 2006-04-24/27
U+0A751L2/06-008R2Moore, Lisa (2006-02-13), "C.8", UTC #106 Minutes
L2/06-037RN3073Sidhu, Sukhjinder (2006-04-07), Proposal to encode Gurmukhi Sign Yakash
N3103 (pdf, doc)Umamaheswaran, V. S. (2006-08-25), "M48.25b", Unconfirmed minutes of WG 2 meeting 48, Mountain View, CA, USA; 2006-04-24/27
L2/16-294Singh, Sarabveer (2016-10-27), Changes to Gurmukhi 10
L2/16-302Sharma, Shriramana (2016-10-28), Feedback on L2/16-294 on Gurmukhi
L2/16-327McGowan, Rick (2016-11-07), "Feedback on L2/16-294 (Gurmukhi)", Comments on Public Review Issues (July 27 - Nov 7, 2016)
L2/16-342Anderson, Deborah; Whistler, Ken; Pournader, Roozbeh; Glass, Andrew; Iancu, Laurențiu (2016-11-07), "4", Recommendations to UTC #149 November 2016 on Script Proposals
L2/16-325Moore, Lisa (2016-11-18), "D.4 (later rescinded)", UTC #149 Minutes
L2/16-380Singh, Manvir (2016-12-09), Feedback on L2/16-294
L2/16-384Singh, Sarabveer (2016-12-13), Feedback on L2/16-380
L2/17-037Anderson, Deborah; Whistler, Ken; Pournader, Roozbeh; Glass, Andrew; Iancu, Laurențiu; Moore, Lisa; Liang, Hai; Ishida, Richard; Misra, Karan; McGowan, Rick (2017-01-21), "5. Gurmukhi", Recommendations to UTC #150 January 2017 on Script Proposals
L2/17-016Moore, Lisa (2017-02-08), "Consensus 150-C13", UTC #150 Minutes, Retain the current glyph in the code charts for Yakash, U+0A75, rescinding the decision documented under D.4.1 in the UTC #149 minutes.
11.0U+0A761L2/16-209RA, Srinidhi; A, Sridatta (2016-07-25), Proposal to Encode an Abbreviation Sign for Gurmukhi
L2/16-203Moore, Lisa (2016-08-18), "D.9", UTC #148 Minutes
N4873R (pdf, doc)"M65.08f", Unconfirmed minutes of WG 2 meeting 65, 2018-03-16
  1. Proposed code points and characters names may differ from final code points and names
  2. See also L2/01-303, L2/01-304, L2/01-305, and L2/01-430R
gollark: You would also need a battery.
gollark: Meh, that's just* a hardware problem.
gollark: It would *utterly* fit in a coin, at least.
gollark: Really basic tiny embedded systems?
gollark: Maybe you could use advanced 3D stacking™ technology and solder it on top.

References

  1. "Unicode 1.0.1 Addendum" (PDF). The Unicode Standard. 1992-11-03. Retrieved 2016-07-09.
  2. "Unicode character database". The Unicode Standard. Retrieved 2016-07-09.
  3. "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.