text-transform, enforce-case, etc.

CSL Development
1

Can we get rid of the text-transform attribute and use enforce-case
for all transformations (since we support attributes that text-
transform doesn’t)?

I propose:
attribute enforce-case { “title” | “sentence” | “uppercase” |
“lowercase” | “capitalize-first” | “capitalize-words”}

Title/sentence are separate from capitalize-first/capitalize-words
because the former two require some kind of intelligent algorithm or
specialized data entry method, while the latter two are dumb
algorithms. Additionally, if some format requires each word of the
title capitalized regardless of length, it could use “capitalize-words.”

Also, should “capitalize-first” and “capitalize-words” set everything
that’s it doesn’t capitalize to lowercase? It doesn’t make much
difference to me, since I think these attributes will be used mostly
with locale terms, but it’s something we should document in the schema.

Simon

2

Simon Kornblith wrote:

Can we get rid of the text-transform attribute and use enforce-case
for all transformations (since we support attributes that text-
transform doesn’t)?

I propose:
attribute enforce-case { “title” | “sentence” | “uppercase” |
“lowercase” | “capitalize-first” | “capitalize-words”}

Seems fine to me. Any other opinions?

In doing this, we’d be deviating from the CSS/FO/ODF basis of the
formatting attributes, but I’m fine with that if we need to.

Bruce