RE: Titlecasing words starting with numeric glyphs and period as word separator

From: CE Whitehead (
Date: Wed Mar 02 2011 - 13:54:04 CST

  • Next message: Mark Davis ☕: "Re: Titlecasing words starting with numeric glyphs and period as word separator"

    Date: Wed, 2 Mar 2011 03:00:18 -0500
    > I'm not suggesting or requesting anything here, but I posted the message here to let you know about
    > the current activities in CSS, and to let you know that if Unicode can define something new, I will try
    > to incorporate the efforts into the text-transform property.
    Thanks, Koji.
    Date: Wed, 2 Mar 2011 11:01:01 -0800
    Subject: Re: Titlecasing words starting with numeric glyphs and period as word separator

    > I agree with Asmus that probably the best choice for CSS in lieu of language-specific information would
    > be a "sentence-case", which modifies the case of the 'first' character of the first word, but leaves the
    > rest of the word and the rest of text alone. What amounts to the 'first character of the first word' needs
    > a bit more discussion.

    > the Dodgers lose => the Dodgers lose
    > 49ers win // leave alone
    Agreed. (I sort of think "49ers" can be set in stone.)
    > diSilva in finals => DiSilva in finals // not Disilva
    > lhistoire du Qubec => lhistoire du Qubec
    In a title this would either be:
    "L'histoire du Quebec" (sorry I don't put accents in email)
    or "L'Histoire du Quebec"
    (French allows either system -- the first is when the title is in "sentence format" and the second is when the title is in "title format" -- according to the rules at ;
    sorry I do not have a more scholarly reference here for you, but the info at seems right to me;
    Spanish on the other hand allows only the first system -- that is you only capitalize the very first word, and no others, even when the first word is a determiner)
    (The rules for titles are language-specific for the languages I know, and these rules can vary even within a language depending on the style manual being followed;
    so you are right; leaving rules for all but the first word out of the database might be best in some cases, since, for some cases, in order to make titles conform to rules of style, a parser would be needed that would recognize parts of speech;
    however, I do not personally think there would be any difficulty, in the case of English, to identify prepositions, conjunctions, and determiners of less than four letters in length C:
    but I am not an expert on this. So someone else might want to comment . . .)
    --C. E. Whitehead

    > Mark

    > Il meglio linimico del bene

    > On Tue, Mar 1, 2011 at 16:51, Asmus Freytag <> wrote:

    >>On 3/1/2011 4:28 PM, Shawn Steele wrote:

    >>I didnt mean you were an English teacher, but my mother was
    >> I meant that Ive seen title casing being used by computer >> applications for CamelCasing (then remove the spaces). Im >> not suggesting thats right, but its clearly a different use case >> than Titles of Books on

    >> For a CSS feature it needs to have some generic usability. The problem is that
    >> "uppercasing the first letter of every word without exception" does not have a strong >> use case - there are simply too few cases where you can use it - for example, you >> can not use in styling English titles or headings (nor in many other languages, there >> for other reasons, to wit: they don't use "title case" conventions at all).

    >> If you apply it to the first word only, you get sentence casing, which does have a
    >> reasonably widespread use case, and 99.x% of all sentences don't start with a word
    >> that needs exceptional "title" casing.

    >> That, to me would seem to be the best use case you can squeeze of this.

    >> A./


    This archive was generated by hypermail 2.1.5 : Wed Mar 02 2011 - 13:56:34 CST