-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Markdown writer: flag for generating inline rather than reference-style footnotes #2567
Comments
Yes, I stumbled upon this several times before. I would really appreciate a flag like this. Btw, thanks for the script, @ltrgoddard! Very helpful! |
No problem! |
@ltrgoddard Thanks for the script! It would be better as a flag, but you saved me some time. |
No problem! On Wed, 13 Jul 2016, 17:18 Evan Edwards, [email protected] wrote:
|
The problem is that inline notes are only possible when the note doesn't contain block-level content. So you can't really have an option to use only inline notes. The best we could do would be to use inline notes when possible. I think that's a bit ugly and not simple conceptually, so I'd prefer not to add such a flag. Note that we now provide an option that will let you have your notes at the end of the enclosing block (e.g. paragraph) or the end of the section rather than the end of the document. This should help for at least some of the cases where you wanted inline notes. |
When converting to Markdown, there is currently no way to make the writer use Pandoc's inline footnotes ("this is some text^[this is a footnote]") in generated text, rather than reference-style notes at the end of the document (see this question on StackOverflow). A flag to specify this behaviour would be useful for anyone converting from, say, a relatively long and heavily noted Docx, who then also needed to add new footnotes or modify the order of existing ones in the resulting Markdown (no more numbering conflicts, etc.) - not as niche a use-case as it sounds, I'd wager. (Edit: I've just hacked up a very simple Python script to do this, but it'd be handy to have it implemented more nicely in Pandoc.)
Just a thought!
The text was updated successfully, but these errors were encountered: