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

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

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 11 Nov 2015 10:40:36 +1300
Message-ID: <CAOp6jLbNRsG=yf5bNHj2pSnftHFudc=5Ao3aHUEpcfCxwUmn6g@mail.gmail.com>
To: Jonathan Kew <jfkthame@gmail.com>
Cc: Sebastian Zartner <sebastianzartner@gmail.com>, Adam Rich <adamzr@gmail.com>, www-style list <www-style@w3.org>
On Wed, Nov 11, 2015 at 10:28 AM, Jonathan Kew <jfkthame@gmail.com> wrote:

> On the other hand, if you capitalize text with things like "left/right,
> forward/back", Gecko gives you "Left/right, Forward/back", which doesn't
> look as good as the Webkit result "Left/Right, Forward/Back".
>
> Basically, you can't win -- there's no simple, correct answer without
> sophisticated (language- and context-specific) analysis of the content that
> would be way out of scope for CSS.
>

Note that --- as I'm sure you know :-) --- Gecko capitalizes exactly at
after line-break opportunities, so you can at least work around cases of
insufficient capitalization, e.g. by inserting a <wbr> before 'right'.
Which is probably a good idea anyway.

Rob
-- 
lbir ye,ea yer.tnietoehr  rdn rdsme,anea lurpr  edna e hnysnenh hhe uresyf
toD
selthor  stor  edna  siewaoeodm  or v sstvr  esBa  kbvted,t
rdsme,aoreseoouoto
o l euetiuruewFa  kbn e hnystoivateweh uresyf tulsa rehr  rdm  or rnea
lurpr
.a war hsrer holsa rodvted,t  nenh hneireseoouot.tniesiewaoeivatewt sstvr
esn
Received on Tuesday, 10 November 2015 21:41:20 UTC

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