en-dash for collapsed numeric citation ranges

I’m pretty sure that we’ve already agreed that en-dash should be used
for numeric ranges generally.

I can fix the processor to use en-dash for these ranges in a fresh
release (due out later today), but just in case, I’d like to confirm
that I’ll not be making a boo-boo.

Frank

This is correct.

Bruce

I’m pretty sure that we’ve already agreed that en-dash should be used
for numeric ranges generally.

http://forums.zotero.org/discussion/18480/endash-instead-of-hyphen-in-collapsed-numeric-citations/#Item_5

I can fix the processor to use en-dash for these ranges in a fresh
release (due out later today), but just in case, I’d like to confirm
that I’ll not be making a boo-boo.

This is correct.

Bruce

Great, I’ll make the adjustment. Meanwhile, the OP in the linked
thread has pointed out that other languages where there has been
takeup of CSL may have different conventions for the range delimiter
(Russian orthography apparently only knows of em-dash). Not sure how
it should be handled, but there seems to be a live issue.

Frank

Can you make a ticket for the spec? I guess we need to document this
behavior.

RintzeOn Wed, Jun 22, 2011 at 9:23 PM, Frank Bennett <@Frank_Bennett>wrote:

Will do. I looked at it during the morning commute, and it seems we
already have a range-delimiter attribute in the schema, on or under
cs:date. If the same attribute were allowed on cs:layout under
cs:citation, it would address this. It’s one possible approach,
anyway.

Frank

I’m pretty sure that we’ve already agreed that en-dash should be used
for numeric ranges generally.

http://forums.zotero.org/discussion/18480/endash-instead-of-hyphen-in-collapsed-numeric-citations/#Item_5

I can fix the processor to use en-dash for these ranges in a fresh
release (due out later today), but just in case, I’d like to confirm
that I’ll not be making a boo-boo.

This is correct.

Bruce

Another question while the topic is up. Would it be right to apply
en-dash to year-suffix ranges as well? So:

(Smith, 2005a–b)

citeproc-js is currently using hyphen, but if en-dash is correct, I
can make that change in the next release, due out soon.

Frank

Yes.

I’m pretty sure that we’ve already agreed that en-dash should be used
for numeric ranges generally.

http://forums.zotero.org/discussion/18480/endash-instead-of-hyphen-in-collapsed-numeric-citations/#Item_5On Jun 23, 2011 6:42 PM, “Frank Bennett” <@Frank_Bennett> wrote:

On Thu, Jun 23, 2011 at 1:16 AM, Bruce D’Arcus <@Bruce_D_Arcus1> wrote:

On Wed, Jun 22, 2011 at 9:15 PM, Frank Bennett <@Frank_Bennett> wrote:

I can fix the processor to use en-dash for these ranges in a fresh
release (due out later today), but just in case, I’d like to confirm
that I’ll not be making a boo-boo.

This is correct.

Bruce

Another question while the topic is up. Would it be right to apply
en-dash to year-suffix ranges as well? So:

(Smith, 2005a–b)

citeproc-js is currently using hyphen, but if en-dash is correct, I
can make that change in the next release, due out soon.

Frank


Simplify data backup and recovery for your virtual environment with
vRanger.

Installation’s a snap, and flexible recovery options mean your data is
safe,

secure and there when you need it. Data protection magic?
Nope - It’s vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev


xbiblio-devel mailing list
xbiblio-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel


Yes.

Great, thanks. I’ll set up the fix.

Frank