- From: Sebastian Zartner <sebastianzartner@gmail.com>
- Date: Tue, 10 Nov 2015 20:04:09 +0100
- To: Adam Rich <adamzr@gmail.com>
- Cc: www-style list <www-style@w3.org>
Received on Tuesday, 10 November 2015 19:04:56 UTC
CSS Text Module Level 3 doesn't define what to consider as word boundary. It lets it up to the user agent to determine this. The related paragraph says this: "For capitalize, what constitutes a “word“ is UA-dependent; [UAX29] is suggested (but not required) for determining such word boundaries. Authors should not expect capitalize to follow language-specific titlecasing conventions (such as skipping articles in English)." Note that Gecko actually capitalizes the words as you expect in your examples. Sebastian On 6 November 2015 at 09:30, Adam Rich <adamzr@gmail.com> wrote: > Hi, > > I am using text-transform: capitalize; and I'm finding that it treats > punctuation within a word as a word boundary. For example: > > word(s) gets transformed into Word(S) > afortunado/a gets transformed into Afortunado/A > > In these cases, the S and the A should not be capitalized. In the first > case, the S is there to indicate that the word may be plural. In the second > case, the word is Spanish and the A is there because the adjective could be > for a male or female reader. > > Can the word boundary rules get adjusted to deal with these cases? > > Thanks, > - Adam >
Received on Tuesday, 10 November 2015 19:04:56 UTC