W3C home > Mailing lists > Public > www-style@w3.org > November 2015

Re: [css-text] text-transform: capitalize Word Boundaries too strict

From: fantasai <fantasai.lists@inkedblade.net>
Date: Tue, 10 Nov 2015 15:38:42 -0800
To: Jonathan Kew <jfkthame@gmail.com>, robert@ocallahan.org
Cc: Sebastian Zartner <sebastianzartner@gmail.com>, Adam Rich <adamzr@gmail.com>, www-style list <www-style@w3.org>
Message-ID: <56428002.8030806@inkedblade.net>
On 11/10/2015 02:17 PM, Jonathan Kew wrote:
>
> Yes, if you control the content. But if you control the content, you'd do better to avoid relying on the vagaries of
> text-transform:capitalize at all, and instead make sure you explicitly capitalize things exactly as desired.
>
> IMO, the main use-case for text-transform:capitalize would be when external content with "uncontrolled" casing is being pulled
> in -- e.g. headlines, captions, etc. from a variety of data sources -- and you want to give it all a reasonably
> uniform-looking, title-like appearance but don't want ALL UPPERCASE and can't afford the resources to apply copy-editing by a
> human (or a high-end natural-language processing system).

Yeah, and know that will often look wrong. Things that you might want
capitalized should be capitalized in source. They can be uppercased or
lowercased as necessary via CSS, but 'text-transform: capitalize' is
really only useful on :first-letter, IMHO.

~fantasai
Received on Tuesday, 10 November 2015 23:39:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:58 UTC