Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75143
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAHMUw2EohSiEszkxER4CsR9L0FWz=P9audQ5o6WxLpn4KQjXfA@mail.gmail.com>
References: <CAHMUw2EohSiEszkxER4CsR9L0FWz=P9audQ5o6WxLpn4KQjXfA@mail.gmail.com>
Date: Mon, 30 Jun 2014 14:36:29 +0200
Message-ID: <CALtuQzAX+jS9M4qVXQnrUi+7L5DZn8QwLOtztQRCjo5QoTWTSw@mail.gmail.com>
To: Tjerk Meesters <tjerk.meesters@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bd91a14e4d36804fd0ceae0
Subject: Re: [PHP-DEV] Re: ucwords() vs title case
From: krebs.seb@gmail.com (Sebastian Krebs)

--047d7bd91a14e4d36804fd0ceae0
Content-Type: text/plain; charset=UTF-8

2014-06-30 13:54 GMT+02:00 Tjerk Meesters <tjerk.meesters@gmail.com>:

> Hi internals,
>
> I came across this old bug: https://bugs.php.net/bug.php?id=34407
>
> The desired behaviour for that particular person:
>
>     "the (world) now" => "The (World) Now"
>
> Currently PHP adopts a very simple rule:
> 1. Capitalise first character (no matter what it is)
> 2. Capitalise character preceded by a space, tab, etc.
>
> Using string.title() from Python you'd get the expected behaviour; they
> use:
> 1. Capitalise first letter of a word
> 2. Lowercase subsequent letters of a word
>

Actually letting a function "uppercase first (letter)" lowercase all
subsequent would be even more unexpected.


> 3. Non-letters delimit words
>
> Personally I find that the latter is too much of a departure from what we
> currently have; a compromise could be to treat punctuation as a word
> delimiter.
>
> Thoughts?
>
>
> --
> --
> Tjerk
>



-- 
github.com/KingCrunch

--047d7bd91a14e4d36804fd0ceae0--