Guido, do you have an opinion on whether to have str.title() handle
embedded apostrophes, "you're" --> "You're" instead of "You'Re"?

IMO, the problem comes-up often enough that people are looking for
workarounds (i.e. string.capwords() was a failed hack created to handle
the problem and django.titlecase() is a successful attempt at a workaround).

I'm not worried about Antoines's comment that we can't change anything
ever.  I am concerned about his point (mentioned on IRC) that there are
no context free solutions (the absolute right answer is hard).  While
the change would seem to always be helpful in an English context, in
French the proper title casing of "l'argent" is "L'Argent".  Then again,
there are cases in French that don't work under either method (i.e.
title casing Amaury Forgeot d'Arc ends-up capitalizing the D no matter
what we do).

Options:

1. Leave everything the same (rejecting requests for apostrophe handling
and forever live with the likes of You'Re).

2. Handle embedded single apostrophes, fixing most cases in English, and
wreaking havoc on the French (who are going to be ill-served under any
scenario).

3. Add an optional argument to str.title() with a list of characters
that will not trigger a transition.  This lets people add apostrophes
and hyphens and other characters of interest.  Hyphens are hard because
cases like mother-in-law should properly be converted to Mother-in_Law
and hyphens get used in many odd ways.

4. Add a new string method for handling title case with embedded
apostrophes but leaving the old version unchanged.

My order of preferences is 2,4,3,1.