- From: Paul Nelson (ATC) <paulnel@winse.microsoft.com>
- Date: Tue, 9 Oct 2007 14:49:45 -0700
- To: Brad Kemper <brkemper@comcast.net>, <www-style@w3.org>
Brad, I see your point and like the idea of adding a new keyword. My suggested value may be long, but is easy to understand what will happen. lowercase-then-capitalize: Converts all bicameral characters to lower case and then capitalizes the first character of each word. Paul -----Original Message----- From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf Of Brad Kemper Sent: Wednesday, October 10, 2007 12:08 AM To: www-style@w3.org Subject: Re: Proposal: "text-transform" property revision Paul, that is a good argument not to use it that way all the time, and perhaps not on BBC headlines, but there are probably a lot of situations to be able to lowercase the letters first, before capitalizing them. For instance, I often have to deal with a system that stores all of its data in ALL CAPS, and I use VBscript on the server right now to make them lowercase and then Initial Capped. It does mess up a few things like initialisms, but it is more acceptable than the alternative, at least for me with that (limited) particular usage. If I understand correctly, what Jens proposed would not actually change the way "capitalize" would work on its own (it would still not affect letters that did not begin a word whn not combined with a different key word), but would only have the side effect you described when combined with "lowercase" in the same text transformation. It does seem like a good option to me. Perhaps a new key word ("upperandlowercase") would be easier to implement than combining two there? On Oct 7, 2007, at 3:02 PM, Paul Nelson (ATC) wrote: > > I believe that we are better off doing as what the current > specification > gives in this regards. > > capitalize - Puts the first character of each word in uppercase; other > characters are unaffected > > A stylesheet would have to be verified against every usage if the > proposal is used ([lowercase || capitalize]) > > The following are headlines from > http://news.bbc.co.uk/2/hi/europe/default.stm. > "Poland debate aired on UK radio" -> "Poland Debate Aired On Uk Radio" > "US conciliatory over missile plan" -> "Us Conciliatory Over Missile > Plan" > "Barclays drops ABN Amro offer" -> Barclays Drops Abn Ambro Offer" > > > I can think of places where there are advantages to the proposal, I > believe there are too many common uses of capitalized text that > would be > converted incorrectly. > > Paul > > > -----Original Message----- > From: www-style-request@w3.org [mailto:www-style-request@w3.org] On > Behalf Of Jens Meiert > Sent: Monday, October 08, 2007 1:28 AM > To: www-style@w3.org > Subject: Proposal: "text-transform" property revision > > > Dear Working Group, > > > I may suggest again what I proposed almost three years ago [1], to > slightly modify the "text-transform" property [2] (or its allowed > value > combinations, respectively): > > uppercase | [lowercase || capitalize] | none | inherit > > The above combination just intends to allow > > text-transform: lowercase capitalize > > as well, a combination that enables grammar compliant "styling" of > words > so that they become, sure, lowercase but also capitalized. Thus, > authors > could e.g. (almost) "correct" the formatting of English headings, > and it > would surely benefit many other languages as well. > > > Best regards, > Jens. > > > [1] http://lists.w3.org/Archives/Public/www-style/2004Feb/0507.html > [2] http://www.w3.org/TR/CSS21/text.html#caps-prop > > -- > Jens Meiert > http://meiert.com/en/ > > > >
Received on Tuesday, 9 October 2007 21:48:54 UTC