Skip to content
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

Update from OliverBalfour/obsidian-pandoc #8

Open
wants to merge 14 commits into
base: master
Choose a base branch
from

Conversation

michaelkimball
Copy link

Push changes from main repo

frogkind and others added 14 commits June 30, 2022 09:47
because btoa() on a SVG data that contains non-Latin1 characters get InvalidCharacterError
This sets the working directory of pandoc to teh directory the source
file lives in. This makes it easier to use resources located relative to
the input file.

An example is a logo reference in a frontmatter block for a pandoc
template (like the eisvogel template).
Use esbuild and obsidian-auto-plugin. Improve relative asset embeds. Update docs.
@AB1908
Copy link

AB1908 commented Dec 28, 2022

There really isn't a reason to keep this fork updated given that Oliver has become active again and is maintaining the plugin. We'll do some cleanup soon.

@michaelkimball
Copy link
Author

I think according to this OliverBalfour#139 that Oliver wants to pass the repo to this GitHub org and there hasn't been an update in a few months. This can be closed though if it's better to come from the current repo maintainer.

@AB1908
Copy link

AB1908 commented Dec 28, 2022

Ah I missed the development. Thanks for the update!

@Gewerd-Strauss
Copy link

This would be really useful. I get by so far, but I already know that there will be a date at which I will have to ditch obsidian pandoc for the more complicated rmd-instance solely because no images will become a deal-breaker. So far, I can get by. I might also just write my own dirty hack for this that is in conceptualisation so far.

Given that there are 2 and a half-ish alternative relative image path fixes up so far in that OliverBalfour#139, I am at least hopeful that it might get resoved at some point. What confuses me is the "alternative relative image [...]". This suggests that a solution exists which allows image export already, but that there might be better methods of doing so. To my knowledge, that is not the case.


As far as I know, images are just not implemented at all so far. (At least the doc's don't seem to mention them at all, and any and all attempts at exporting an image so far has failed miserably on my end.)

Can someone with a bit more knowledge on the current state of things perhaps confirm if that assumption of mine is correct as of right now?

If I am wrong, please help me figure out how to do so :P

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.

None yet

7 participants