I need to repeat publisher to do:
So what if we had this as a default?
E.g. allow the delimiter attribute on publisher?
I guess that doesn’t help for the case where you include the date, but
maybe there’s a similarly simple way to address that?
This also explains why I prefer simple top-level fields. Once you
remove , is there any reason to have </and not just ?
One problem is that there may be other kinds of relevant “place”
variables? For example, the place of a conference, or a hearing.
Either we’ll be making authors use
everywhere (or define a macro to handle
this in nearly every document), or we’ll need to make
actually do something. In my view, the latter is much more intuitive
than the former.
OK, let’s look at the chicago-a style. We have stuff like:
<issue prefix=", ">
<label form="short" text-transform="lowercase"
suffix=". "/>
There’s no way around needing to define the label and its location
relative to the number. Is there really a completely clean, simple, way
to do this?
Right now, we could define this in the defaults:
<locator prefix=", ">
<label form="short" text-transform="lowercase"
suffix=". "/>
I guess what you’re saying is that is only so helpful and that you
might also want to globally define other macros apart from the generic?
Bruce