OK, I’m still trying to wrap my head around this stuff. Here’s the example (from the Vancouver style) that is giving me some problem…
<group prefix=" " suffix=". ">
<text term="in" suffix=": " text-case="capitalize-first" />
<text macro="editor" />
<text variable="container-title" />
</group>
In this case, which takes precedence and why? Both of the text macros following the term depend on a variable in the data stream.
Does that mean the if either of the text elements following the text-term element are blank the entire group is discarded?
Ron.________________________________________
From: Frank Bennett [@Frank_Bennett]
Sent: Saturday, February 20, 2010 7:14 AM
To: development discussion for xbiblio
Subject: Re: [xbiblio-devel] Text elements
On Sat, Feb 20, 2010 at 10:36 AM, Jerome, Ron <@Jerome_Ron> wrote:
What about adding a new attribute to text elements (term, value) which are
dependent on another variable to be output. I would propose a
“dependent-variable” attribute, which would have to evalute to TRUE before
the term or value would be output.
Again IMHO, this would greatly simplify processing logic.
I don’t like to be the nay-sayer in the room, but I think this might
be a risky move. The conditions that cause failure of any variable to
render can turn on conditional branching, either inside the cs:names
element (through cs:substitute), or through a proper cs:choose node.
The only failsafe way to know whether a variable was rendered is to
run the conditions and find out. For a couple of (admittedly
contrived) examples:
The following will produce output if either the “author” or the
“editor” var is present:
The following will produce output only if both the “author” and the
“editor” vars are present:
With cs:group operating as an implicit conditional based on actual
output from at least one variable, the style designer only needs to
worry about grouped joins, and the conditional logic follows without
any additional coding (and associated debugging). With 180+ styles in
circulation, keeping things simple for style maintainers ends up being
a priority.
I’ve felt a bit of frustration myself over implementing some of these
features (a trawl through the archives will show that I wasn’t nearly
so nice about my own objections…). But I think on this one there’s
a fairly sound reason for retaining the current behavior of cs:group.
That’s only my take; Bruce, Rintze and others may have other views.
Frank
Ron.
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
Best Open Source Mac Front-Ends 2023
xbiblio-devel mailing list
xbiblio-devel@lists.sourceforge.net
xbiblio-devel List Signup and Options
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
xbiblio-devel mailing list
xbiblio-devel@lists.sourceforge.net