Skip to content
This repository has been archived by the owner on Apr 30, 2021. It is now read-only.

Remove brackets from author-in-text numerical citations? #133

Closed
nr0cinu opened this issue May 22, 2015 · 4 comments
Closed

Remove brackets from author-in-text numerical citations? #133

nr0cinu opened this issue May 22, 2015 · 4 comments

Comments

@nr0cinu
Copy link

nr0cinu commented May 22, 2015

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:

[@ref1] says

@ref1 says

right now yields exactly the same thing:

<p><span class="citation">(<a href="#ref-ref1">1</a>)</span> says</p>
<p><span class="citation">(<a href="#ref-ref1">1</a>)</span> says</p>

Wouldn’t it be better to have this result:

<p><span class="citation">(<a href="#ref-ref1">1</a>)</span> says</p>
<p><span class="citation"><a href="#ref-ref1">1</a></span> says</p>

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

nr0cinu referenced this issue May 22, 2015
So we have

    [1] says

rather than

    [Reference 1] says

or

    Reference 1 says

This seems to be what IEEE likes.
@jgm
Copy link
Owner

jgm commented May 27, 2015 via email

@njbart
Copy link
Contributor

njbart commented May 30, 2015

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.

@nr0cinu
Copy link
Author

nr0cinu commented Aug 26, 2015

I now ran into exactly this problem with nature.csl ;) Both @ref and [@ref] render as superscript numbers and I concur that it would make more sense to render the first as a plain number and only the second as superscript.

I think this approach could be very systematic in that @ref would cause pandoc-citeproc to ignore certain arguments from the <layout> specifications. I.e. ignore Affixes (prefix, suffix) and Formatting (vertical-align, etc), but honour delimiter …?

@jgm
Copy link
Owner

jgm commented Aug 26, 2015

+++ Bela Hausmann [Aug 26 15 06:26 ]:

I now ran into exactly this problem with nature.csl ;) Both @ref and
[@ref] render as superscript numbers and I concur that it would make
more sense to render the first as a plain number and only the second as
superscript.

I think this approach could be very systematic in that @ref would cause
pandoc-citeproc to ignore certain arguments from the
specifications. I.e. ignore Affixes (prefix, suffix) and Formatting
(vertical-align, etc), but honour delimiter …?

That sounds reasonable to me.

@jgm jgm closed this as completed in 90785f4 Sep 21, 2015
jgm added a commit that referenced this issue Sep 21, 2015
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.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants