Christoph Burgmer <cburg...@ira.uka.de> added the comment:
Antoine Pitrou wrote:
> capwords() itself could be deprecated, since it's an obvious one-
> Replacing in with another method, however, will just confuse and
annoy
> existing users.
Yes, sorry, I meant the semantics, where as you are right for the
specific function.
Marc-Andre Lemburg wrote:
> 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).
ICU already has the full implementation, so Python could get away with
just supporting the default implementation (as seen with other case
mappings).
>>> from PyICU import UnicodeString, Locale, BreakIterator
>>> en_US_locale = Locale('en_US')
>>> breakIter = BreakIterator.createWordInstance(en_US_locale)
>>> s = UnicodeString("There's a hole in the bucket.")
>>> print s.toTitle(breakIter, en_US_locale)
There's A Hole In The Bucket.
>>> breakIter.setText("There's a hole in the bucket.")
>>> last = 0
>>> for i in breakIter:
... print s[last:i]
... last = i
...
There's
A
Hole
In
The
Bucket
.
----------
_______________________________________
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
