Skip to content

Process citations / references with pandoc-manubot-cite filter#300

Merged
dhimmel merged 10 commits intomanubot:masterfrom
dhimmel:pandoc-manubot-cite
Jan 14, 2020
Merged

Process citations / references with pandoc-manubot-cite filter#300
dhimmel merged 10 commits intomanubot:masterfrom
dhimmel:pandoc-manubot-cite

Conversation

@dhimmel
Copy link
Member

@dhimmel dhimmel commented Jan 7, 2020

Before merge:

  • change repo back to manubot/manubot

Testing out manubot/manubot#99 and how it would be integrated with rootstock.

@dhimmel dhimmel force-pushed the pandoc-manubot-cite branch from 5e82a38 to dcff05a Compare January 7, 2020 15:51
@AppVeyorBot
Copy link

AppVeyor build 1.0.71 for commit dcff05a by @dhimmel is now complete. The rendered manuscript from this build is temporarily available for download at:

@manubot manubot deleted a comment from AppVeyorBot Jan 7, 2020
@manubot manubot deleted a comment from AppVeyorBot Jan 7, 2020
@dhimmel dhimmel force-pushed the pandoc-manubot-cite branch from 301ab30 to 3ae0f1d Compare January 7, 2020 16:04
@AppVeyorBot
Copy link

AppVeyor build 1.0.73 for commit 3ae0f1d by @dhimmel failed.

@AppVeyorBot
Copy link

AppVeyor build 1.0.74 for commit 9b1192f by @dhimmel is now complete. The rendered manuscript from this build is temporarily available for download at:

@AppVeyorBot
Copy link

AppVeyor build 1.0.75 for commit bb468d1 by @dhimmel is now complete. The rendered manuscript from this build is temporarily available for download at:

Comment on lines +29 to +30
citekey-aliases:
tag:deep-review: doi:10.1098/rsif.2017.0387
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For reference, it looks like users need to replace the tab separation from citation-tags.tsv with a space for the YAML to be valid. We could look into manubot process converting citation-tags to citation-aliases if --skip-citations is specified.

I'm also not sure that this is the best place to specify citekey-aliases. It is okay. We should see how it interacts with defaults and per-markdown file yaml metadata blocks. Another option is to default to the link-reference syntax for defining aliases.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A possible downside of defaulting to the link-reference syntax could be a greater chance of multiply defined tags. We could recommend putting them all in one Markdown file, even a new dedicated files like tags.md.

Copy link
Member Author

@dhimmel dhimmel Jan 13, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A possible downside of defaulting to the link-reference syntax could be a greater chance of multiply defined tags

This is easy to detect and warn (update already do).

We could recommend putting them all in one Markdown file, even a new dedicated files like tags.md.

One downside of this is that it doesn't allow normal markdown viewers to render the link. One of the big benefits of link-reference syntax is the ability of:

[@citekey] to render as a link

[@citekey]: https://github.com/manubot/rootstock/pull/300

To render in places like GitHub like below:

@citekey to render as a link

@AppVeyorBot
Copy link

AppVeyor build 1.0.76 for commit 49dcfcd by @dhimmel is now complete. The rendered manuscript from this build is temporarily available for download at:

@AppVeyorBot
Copy link

AppVeyor build 1.0.77 for commit b6d61e1 by @dhimmel is now complete. The rendered manuscript from this build is temporarily available for download at:

@AppVeyorBot
Copy link

AppVeyor build 1.0.78 for commit 3984ee9 by @dhimmel is now complete. The rendered manuscript from this build is temporarily available for download at:

add temp citation-tags.tsv for testing
@AppVeyorBot
Copy link

AppVeyor build 1.0.79 for commit d1967d9 by @dhimmel is now complete. The rendered manuscript from this build is temporarily available for download at:

@dhimmel dhimmel changed the title Attempt using pandoc-manubot-cite filter Process citations / references with pandoc-manubot-cite filter Jan 13, 2020
@dhimmel dhimmel requested a review from agitter January 13, 2020 22:37
@AppVeyorBot
Copy link

AppVeyor build 1.0.80 for commit 0a7fe11 by @dhimmel is now complete. The rendered manuscript from this build is temporarily available for download at:

@AppVeyorBot
Copy link

AppVeyor build 1.0.81 for commit feb228c by @dhimmel is now complete. The rendered manuscript from this build is temporarily available for download at:

@dhimmel
Copy link
Member Author

dhimmel commented Jan 14, 2020

@agitter I am going to merge, since I want to start rolling out this change for additional testing and usage experience. Will address any comments in a subsequent PRs.

@dhimmel dhimmel merged commit 6636b91 into manubot:master Jan 14, 2020
@dhimmel dhimmel merged commit 6636b91 into manubot:master Jan 14, 2020
@dhimmel dhimmel deleted the pandoc-manubot-cite branch January 14, 2020 15:00
dhimmel added a commit that referenced this pull request Jan 14, 2020
This build is based on
6636b91.

This commit was created by the following Travis CI build and job:
https://travis-ci.com/manubot/rootstock/builds/144344566
https://travis-ci.com/manubot/rootstock/jobs/275411125

The full commit message that triggered this build is copied below:

Process citations / references with pandoc-manubot-cite filter

merges #300
dhimmel added a commit that referenced this pull request Jan 14, 2020
This build is based on
6636b91.

This commit was created by the following Travis CI build and job:
https://travis-ci.com/manubot/rootstock/builds/144344566
https://travis-ci.com/manubot/rootstock/jobs/275411125

The full commit message that triggered this build is copied below:

Process citations / references with pandoc-manubot-cite filter

merges #300
Copy link
Member

@agitter agitter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This merged pull request looks good to me. I found two small things that could be addressed in a future pull request.

```

This syntax is also used by [`pandoc-url2cite`](https://github.com/phiresky/pandoc-url2cite).
Make sure to place these link reference definitions in their own paragraphs.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In a future pull request, we can note that these can be placed in any of the content Markdown files. The location for these aliases could be ambiguous because they are not in a dedicated tags file.

tag:my-doi: doi:10.1016/S0022-2836(05)80360-2
```

For backwards compatability, tags can also be defined in `content/citation-tags.tsv`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

compatability -> compatibility

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants