From haynes@sierratel.com Tue Aug 8 20:51:12 2000 From: haynes@sierratel.com (Matthew Haynes) Date: Tue, 08 Aug 2000 12:51:12 -0700 Subject: [I18n-sig] I18n-sig -- confirmation of subscription --request 806019 Message-ID: <399064B0.D79255E5@sierratel.com> confirm 806019 From wunder@inktomi.com Sat Aug 26 00:22:11 2000 From: wunder@inktomi.com (Walter Underwood) Date: Fri, 25 Aug 2000 16:22:11 -0700 Subject: [I18n-sig] Nomalization in 1.6? Message-ID: <852889715.967220531@nosferatu.inktomi.com> Is support for Unicode normalization planned (or already in) 1.6? I can't find it in 1.6b1, but I could be missing something. wunder -- Walter Underwood Senior Staff Engineer, Ultraseek Server, Inktomi Corp. formerly Infoseek Software, GO.com, The Walt Disney Company http://www.ultraseek.com/ http://www.inktomi.com/ All Mickey Mouse films are founded on the motif of leaving home in order to learn what fear is. -- Walter Benjamin, 1931 From mal@lemburg.com Mon Aug 28 10:18:11 2000 From: mal@lemburg.com (M.-A. Lemburg) Date: Mon, 28 Aug 2000 11:18:11 +0200 Subject: [I18n-sig] Nomalization in 1.6? References: <852889715.967220531@nosferatu.inktomi.com> Message-ID: <39AA2E53.AF675C5D@lemburg.com> Walter Underwood wrote: > > Is support for Unicode normalization planned (or already in) 1.6? > I can't find it in 1.6b1, but I could be missing something. This would be nice to have for 2.1 indeed. Plans for adding Unicode compression as codec and full support of normalization have been on the plate, but this would either need a volunteer to step up or some funding by a commercial entity. -- Marc-Andre Lemburg ______________________________________________________________________ Business: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/ From tdickenson@geminidataloggers.com Thu Aug 31 13:49:28 2000 From: tdickenson@geminidataloggers.com (Toby Dickenson) Date: Thu, 31 Aug 2000 13:49:28 +0100 Subject: [I18n-sig] Terminology gap Message-ID: Ive recently been updating my documentation to account for Unicode issues, and have been troubled by the lack of a good name to describe an object that can be *either* a "plain string" or a "unicode string". My best attempt so far is to call it a "string-like object", but that feels too long for something so common. I would like to use the simple "string", but a quick poll of my local developers suggests that this does not convey the unicode option. Does anyone have any suggestions? Toby Dickenson tdickenson@geminidataloggers.com From mal@lemburg.com Thu Aug 31 14:35:28 2000 From: mal@lemburg.com (M.-A. Lemburg) Date: Thu, 31 Aug 2000 15:35:28 +0200 Subject: [I18n-sig] Terminology gap References: Message-ID: <39AE5F20.E68BC43F@lemburg.com> Toby Dickenson wrote: > > Ive recently been updating my documentation to account for Unicode > issues, and have been troubled by the lack of a good name to describe > an object that can be *either* a "plain string" or a "unicode string". I usually use "8-bit string" and "Unicode object". > My best attempt so far is to call it a "string-like object", but that > feels too long for something so common. > > I would like to use the simple "string", but a quick poll of my local > developers suggests that this does not convey the unicode option. > > Does anyone have any suggestions? I think the accepted term is "string", since someday Python will have a string base class. Unicode objects and 8-bit strings will then be subclasses of this string class. -- Marc-Andre Lemburg ______________________________________________________________________ Business: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/