Inline styling support

I’ve been playing around with tagging schemes to place in CSL locales,
to support inline markup. Here’s what I’ve got at the moment:

.... ........ .... .... ........ ........ .... .... ........ ........ ....

This depends on two new “top-level” elements in the locale, "semantic"
and “visual”. The “visual” defines flip-flop behaviour for (some of
the) formatting attributes. The “semantic” element ties a particular
inline markup tag class to one or more formatting attribute/value
pairs.

Feedback welcome. (I don’t want this to be a distraction, though –
if you haven’t commented on Bruce’s proposal for locales markup,
please give that priority.)

Frank

I’ve been playing around with tagging schemes to place in CSL locales,
to support inline markup. Here’s what I’ve got at the moment:

Here is an arrangement that covers the bases a bit better, and is also
more compact.

Top-level locale elements are “semantic” and “visual”. Semantic
elements define top-level markup classes that may apply implicit
markup (defined by one or more “apply” elements), and also allow
explict markup within the semantic span (specified by one or more
"allow" elements).

The value attribute on apply and allow elements refers to a named
visual formatting operation, which may either apply a single CSL
formatting function, or assign one of two functions dynamically
according to context, in “flip-flop” fashion. In the former case, the
"visual" element is a singleton, and in the latter it is a span with
"outer" and “inner” elements specifying the functions to be applied
(the layout is similar to the usage of the “term” element, with its
single, multiple and one-size-fits-all forms).









…</visual

Am not exactly fllowing the use cases and requirements here. For sake
of argument, why not just use your flip flop convention and leave this
out of csl?

Am not exactly fllowing the use cases and requirements here. For sake
of argument, why not just use your flip flop convention and leave this
out of csl?

Very happy to start there.

OK.

I’d just suggest, if you come across a use case where this approach
isn’t enough, note it on the wiki, and post it here.

Bruce