OliverBalfour / obsidian-pandoc

Pandoc document export plugin for Obsidian (https://obsidian.md)
MIT License
719 stars 60 forks source link

[Bug] "Internal Link Processing" option has no effect #163

Open ParkerRobb opened 1 year ago

ParkerRobb commented 1 year ago

I've tried exporting a document using every option under "Internal Link Processing" and nothing changes between my source and the exported PDF. Every wikilink is exported as straight text regardless of which option is chosen.

ParkerRobb commented 1 year ago

For the option below, I'm inputting Markdown, not HTML, if that makes any difference.

FeralFlora commented 1 year ago

I'm having the same issue.

citingfairy commented 1 year ago

I have an issue that seems to be related to this here. I use the Citations plugin to connect to Zotero, hence, my citations in the md look like this: [[[smith2020]], p. 45] Expected outcome would be: (Smith 2020, p. 45) Actual outcome is: ([(Smith 2020)], p. 45) This does not change with any of the given options for Internal Link Processing. If I change the setting "Export files from..." to html, the links and brackets are gone as they should be, but then, of course, the citation doesn't work.

smut-ny commented 1 year ago

Having the same issue. I want to use obsidian links as some sort of comment / hyperlink inside the manuscript, but the brackets [[]] doesn't get removed after the docx export.

ParkerRobb commented 1 year ago

I found a workaround:

If you have Pandoc >3.0 and specify --from=markdown+wikilinks_title_after_pipe as a Pandoc option in "Extra Pandoc options" in the plugin settings, Pandoc itself will process the links and convert them to text (see the Pandoc User's Guide, p108).

(This does nothing to fix the underlying bug in this plugin, however).

RealGreekGeek commented 4 months ago

Thank you for your solution @ParkerRobb. Just one question: Your solution does work insofar as it formats to a hyperlink:

I need it to be in Plain text. Is there any way to solve this problem? :)

zensitively commented 2 months ago

I have the same issue, but @ParkerRobb 's workaround doesn't work for me (using pandoc 3.3).