Marc-Andre Lemburg <m...@egenix.com> added the comment: Christoph Burgmer wrote: > > Christoph Burgmer <cburg...@ira.uka.de> added the comment: > > I admit I don't fully understand the semantics of capwords().
string.capwords() is an old function from the days before Unicode. The function is basically defined by its implementation. > But from > what I believe what it should do, this function could be happily > replaced by the word-breaking algorithm as defined in > http://www.unicode.org/reports/tr29/. > > This algorithm should be implemented anyway, to properly solve > issue6412. Simple word breaking would be nice to have in Python as new Unicode method, e.g. .splitwords(). Note however, that word boundaries are just as complicated as casing: there are lots of special cases in different languages or locales (see the notes after the word boundary rules in the TR29). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7008> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
