This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients ezio.melotti, lemburg, vbr
Date 2010-11-19.15:29:49
SpamBayes Score 0.00038775476
Marked as misclassified No
Message-id <4CE697EB.2050304@egenix.com>
In-reply-to <1290177387.08.0.667845269575.issue10459@psf.upfronthosting.co.za>
Content
Vlastimil Brom wrote:
> 
> New submission from Vlastimil Brom <vlastimil.brom@gmail.com>:
> 
> I just noticed an ommision of come character names in unicodedata module.
> These are some CJK - Ideographs:
> 
> 龼 (0x9fbc) - 鿋 (0x9fcb)
>  (CJK Unified Ideographs [19968-40959] [0x4e00-0x9fff])
> 
> 𪜀 (0x2a700) - 𫜴 (0x2b734)
> (CJK Unified Ideographs Extension C [173824-177983] [0x2a700-0x2b73f])
> 
> 𫝀 (0x2b740) - 𫠝 (0x2b81d)
>  (CJK Unified Ideographs Extension D [177984-178207] [0x2b740-0x2b81f])
> 
> The names are probably to be generated - e.g. CJK UNIFIED IDEOGRAPH-2A700 ... etc.

I don't think we should fill those rather big ranges with generated
names, unless there's a standard for this. There are quite a
few ranges in the Unicode database that are assigned, but don't
have a literal name associated with them.
History
Date User Action Args
2010-11-19 15:29:50lemburgsetrecipients: + lemburg, vbr, ezio.melotti
2010-11-19 15:29:49lemburglinkissue10459 messages
2010-11-19 15:29:49lemburgcreate