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 alexs, ezio.melotti, lemburg, loewis, senn
Date 2009-10-14.20:16:27
SpamBayes Score 0.0063383
Marked as misclassified No
Message-id <4AD6319D.3090601@egenix.com>
In-reply-to <1255548330.08.0.951222721211.issue4610@psf.upfronthosting.co.za>
Content
Jeff Senn wrote:
> 
> Jeff Senn <senn@users.sourceforge.net> added the comment:
> 
> Yikes! I just noticed that u''.title() is really broken! 
> 
> It doesn't really pay attention to word breaks -- 
> only characters that "have case".  
> Therefore when there are (caseless)
> combining characters in a word it's really broken e.g.
> 
>>>> u'n\u0303on\u0303e'.title()
> u'N\u0303On\u0303E'
> 
> That is (where '~' is combining-tilde-over)
> n~on~e -title-cases-to-> N~On~E

Please have a look at http://bugs.python.org/issue6412 - that patch
addresses many casing issues, at least up the extent that we can
actually fix them without breaking code relying on:

len(s.upper()) == len(s)

for upper/lower/title.

If we add support for 1-n code point mappings, then we can only
enable this support by using an option to the casing methods (perhaps
not a bad idea: the parameter could be used to signal the local
to assume).
History
Date User Action Args
2009-10-14 20:16:29lemburgsetrecipients: + lemburg, loewis, senn, ezio.melotti, alexs
2009-10-14 20:16:27lemburglinkissue4610 messages
2009-10-14 20:16:27lemburgcreate