Hi,
citeproc-rb is getting closer to replicating the Zotero example outputs, but
I’ve run into a couple of problems:
In the AMA style, there is the following structure (under the 'book’
condition):
<group suffix=".">
<text macro="title" prefix=" " suffix="."/>
<text macro="edition" prefix=" " />
<text macro="editor" prefix=" (" suffix=")"/>
</group>
At the moment I’m getting title output which looks like:
Splitting the Difference…
The Zotero style page outputs this correctly.
Is there some special handling of suffixes to accomplish this? How does the
processor know when to append the suffix
(in the case of editor), and when not to (in the case of title with no
further data)?
Similar problems crop up in treatment of other styles, otherwise citeproc-rb
is getting reasonably close.
Regards,
Liam.
citeproc-rb is getting closer to replicating the Zotero example outputs, but
I’ve run into a couple of problems:
In the AMA style, there is the following structure (under the ‘book’
condition):
<group suffix=".">
<text macro="title" prefix=" " suffix="."/>
<text macro="edition" prefix=" " />
<text macro="editor" prefix=" (" suffix=")"/>
</group>
At the moment I’m getting title output which looks like:
Splitting the Difference…
So I presume in your output, you’re seeing:
Splitting the Difference…
?
The Zotero style page outputs this correctly.
Is there some special handling of suffixes to accomplish this? How does the
processor know when to append the suffix
(in the case of editor), and when not to (in the case of title with no
further data)?
I vaguely recall Simon talking about this and implementing some code
that suppresses duplicate punctuation. We should confirm that and
document the rule(s).
Similar problems crop up in treatment of other styles, otherwise citeproc-rb
is getting reasonably close.
Great.
Bruce
So I presume in your output, you’re seeing:
Splitting the Difference…
Right, exactly.
I vaguely recall Simon talking about this and implementing some code
that suppresses duplicate punctuation. We should confirm that and
document the rule(s).
Yes, this is tricky based on how I’ve currently implemented the processor.
But this is important, since it also produces double spacing and similar
problems elsewhere.
Regards,
Liam.