-
-
Notifications
You must be signed in to change notification settings - Fork 61
Remove brackets from author-in-text numerical citations? #133
Comments
So we have [1] says rather than [Reference 1] says or Reference 1 says This seems to be what IEEE likes.
Maybe not a bad solution. @nickbart, any thoughts?
Pandoc-citeproc strives to allow you to switch bib formats without
any changes in the source, and this change would break that.
On the other hand, the brackets are appropriate for ieee but not
for nature and some other styles.
I'm really not sure what the best approach is.
|
Well, short of including specific formatting instructions into pandoc-citeproc that are dependent on but not included in the CSL style used, a plain number is probably the best solution. This would also solve a minor problem with nature.csl and other styles using superscripts: (a) A superscript as grammatical part of the sentence looks very odd, and (b) any space between the number and preceding punctuation (like: end of previous sentence) is removed. |
I now ran into exactly this problem with nature.csl ;) Both I think this approach could be very systematic in that |
+++ Bela Hausmann [Aug 26 15 06:26 ]:
That sounds reasonable to me. |
See discussion in #133. This change also removes unsetAffixes from Text.CSL.Style's exported functions. This function was only used in one places and is very simple. As a result of the API change, the version has been bumped to 0.8.
Hi!
Sorry that I’m being annoying about this topic, but would it be possible to remove the brackets for author-in-text numerical citations (which were introduced in e3a85ef)? If somebody wants the brackets they could just use the normal way.
Example:
The current way is a bit redundant:
right now yields exactly the same thing:
Wouldn’t it be better to have this result:
And then, if somebody (e.g. me) wants a prefix they could just write it into the text? Maximum flexibility but still simple!
Want do you think?
Thanks!!
Bela
The text was updated successfully, but these errors were encountered: