I’ve got a problem:
The Bluebook law review (rather stupidly) a) uses small caps for names,
and b) only uses them in some contexts (books).
Unless I’m being dense, the solution given the existing schema would be
horrendously complex. I’m having a hard time, in fact, understanding how
to modify the below macro to achieve this. It seems to me I probably
have to add a bunch of conditionals.
But …
… I seem recall Simon saying something about inheritance within
substitution. So:
a) would that solve my problem in this case, where I just use a
conditional within the top-level name to specify the small-caps
formatting for books, and then the same would apply to editors and
translators that substituted?
b) can we document this more clearly within the schema? This is rather
terse:
Short version of “names” element, without children, allowed in
c) even bigger, do we need to be able to specify a macro purely for
names, without any variable?
Bruce
I’ve got a problem:
The Bluebook law review (rather stupidly) a) uses small caps for
names,
and b) only uses them in some contexts (books).
Unless I’m being dense, the solution given the existing schema would
be
horrendously complex. I’m having a hard time, in fact, understanding
how
to modify the below macro to achieve this. It seems to me I probably
have to add a bunch of conditionals.
But …
… I seem recall Simon saying something about inheritance within
substitution. So:
a) would that solve my problem in this case, where I just use a
conditional within the top-level name to specify the small-caps
formatting for books, and then the same would apply to editors and
translators that substituted?
Not sure quite what you mean by the “top-level name.”
b) can we document this more clearly within the schema? This is rather
terse:
Short version of “names” element, without children, allowed in
Yes, we probably should.
c) even bigger, do we need to be able to specify a macro purely for
names, without any variable?
I am aware it isn’t incredibly elegant, is there any reason the
following wouldn’t work?
Simon
Simon Kornblith wrote:
…
… I seem recall Simon saying something about inheritance within
substitution. So:
a) would that solve my problem in this case, where I just use a
conditional within the top-level name to specify the small-caps
formatting for books, and then the same would apply to editors and
translators that substituted?
Not sure quite what you mean by the “top-level name.”
The “author” name element.
b) can we document this more clearly within the schema? This is rather
terse:
Short version of “names” element, without children, allowed in
Yes, we probably should.
Any suggestion?
c) even bigger, do we need to be able to specify a macro purely for
names, without any variable?
I am aware it isn’t incredibly elegant, is there any reason the
following wouldn’t work?
That might indeed work, though it is a little convoluted (as you note).
Can others here take a look at Simon’s example below? Is it clear enough
to be sensible?>
Can others here take a look at Simon’s example below? Is it clear
enough
to be sensible?
This seems clear and reasonable to me. Elena> -------------------------------------------------------------------------
Simon Kornblith wrote:
<if macro="name-macro">
One problem: this bit isn’t valid. If we add that conditional, how would
we document it?
Bruce
Bruce D’Arcus wrote:
Simon Kornblith wrote:
<if macro="name-macro">
One problem: this bit isn’t valid. If we add that conditional, how would
we document it?
Alright, I didn’t get an answer for this, so I’ll suggest adding:
## is true if the macro specified returns any text
attribute macro { token }
Any opinions?
Bruce
Oops. I don’t think there’s any reason that couldn’t be:
…but we could also implement a macro conditional.
Simon
Simon Kornblith wrote:> On Feb 12, 2008, at 5:45 PM, Bruce D’Arcus wrote:
Bruce D’Arcus wrote:
Simon Kornblith wrote:
<if macro="name-macro">
One problem: this bit isn’t valid. If we add that conditional, how
would
we document it?
Alright, I didn’t get an answer for this, so I’ll suggest adding:
is true if the macro specified returns any text
attribute macro { token }
Any opinions?
Oops. I don’t think there’s any reason that couldn’t be:
…but we could also implement a macro conditional.
Nah, that’s a good point; if it works without adding a new attribute,
not much point in adding it.
But I could use some feedback on documenting that other thing I
mentioned yesterday (I forget what it is ATM).
Bruce