redux on bluebook

I forgot about this earlier thread, but might be worth looking at
again before we settle on the solution.

http://sourceforge.net/mailarchive/message.php?msg_id=53208a5f0901191713p5684347sa92e394fb52a20ae%40mail.gmail.com

Bruce

I forgot about this earlier thread, but might be worth looking at
again before we settle on the solution.

http://sourceforge.net/mailarchive/message.php?msg_id=53208a5f0901191713p5684347sa92e394fb52a20ae%40mail.gmail.com

Ah, days of youth. :slight_smile:

The condition that I suggest there isn’t
needed. We have first-reference-note-number now. If that returns nil
when the value would be the same as the current note number, it covers
the case, with . So that
one can be tossed out.

I’ve been struggling to come up with a readable an unambiguous name
for the note-distance attribute. No luck yet, but I’ve started to
wonder whether this could be folded into the position condition as
position=“reset”, with the actual reset condition described in an
option (or global attribute). So:

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

The “reset” value would need to be independent of the
ibid-with-locator, ibid, and subsequent values – a cite could have
both reset TRUE and subsequent TRUE – to allow references of
different types to be handled differently.

The syntax above could be extended later to cover page resets, if that
were ever desired, with the addition of something like a
position-reset-type option.

Frank

I’ve been struggling to come up with a readable an unambiguous name
for the note-distance attribute. No luck yet, but I’ve started to
wonder whether this could be folded into the position condition as
position=“reset”, with the actual reset condition described in an
option (or global attribute).

Yes, I was considering something like this as well. The only immediate
thing that jumps out to me is what the value means here?