I’m with you on this one. Some styles lack this preceding comma, so it is
desirable to explicitly declare it.
Rintze
It validates and looks right, although csledit.xul of course doesn’t get it
(but it doesn’t choke either).
Rintze
I’m with you on this one. Some styles lack this preceding comma, so it is
desirable to explicitly declare it.Rintze
I don’t know what the old approach was, so I’ll need a little guidance
on this one. Can you provide a set of examples of CSL that illustrate
the difference, and the output each should produce?The old approach is magic: print the et-al term at the end of the
author list with a preceding ", " (which, then, is an implicit
prefix).That’s what you’re doing.So what I’m suggesting is just that the prefix be required when using
cs:et-al:I’m just wondering if people agree.
Okie-dokie. Here are some tests that reflect the new behaviour.
If no et-al styling element is provided, a comma-space is inserted
automagically:
If a styling element is given, the automagic prefix is not added:
The prefix attribute can be used to provide a custom separator:
Frank2009/3/23 Rintze Zelle <@Rintze_Zelle>:
Perfecto!
One minor point: I just committed a change to the schema, so that
'alternate-term="and-others"'
… should be:
'term="and others"'.
That aligns things better, it seems.
Bruce
Okie-dokie. Here are some tests that reflect the new behaviour.
If no et-al styling element is provided, a comma-space is inserted
automagically:
XBib download | SourceForge.net
If a styling element is given, the automagic prefix is not added:
XBib download | SourceForge.net
The prefix attribute can be used to provide a custom separator:
Perfecto!
One minor point: I just committed a change to the schema, so that
‘alternate-term=“and-others”’
… should be:
‘term=“and others”’.
That aligns things better, it seems.
Looks good. I’ve checked that in.
Frank