Open AB1908 opened 2 years ago
Found someone who forked it and seems to be working on some commits 👀 https://github.com/BumbrT/obsidian-html-export
That's actually pretty cool. I think we can use that fork as the main one for now but we need a way to indicate that that fork has some fixes and request that folks open their issues there as well. I'll try and bring this back to the community. I never got around to implementing fixes myself sadly as EOY is quite busy for me.
That's actually pretty cool. I think we can use that fork as the main one for now but we need a way to indicate that that fork has some fixes and request that folks open their issues there as well. I'll try and bring this back to the community. I never got around to implementing fixes myself sadly as EOY is quite busy for me.
I also fixed some bugs and create a modified version of obsidian-pandoc. (Because I update to the latest plugin toolchain, I just create a brand new repo.) https://github.com/RainCat1998/obsidian-pandoc You can export md note to html perfectly using my patched version.
That's actually pretty cool. I think we can use that fork as the main one for now but we need a way to indicate that that fork has some fixes and request that folks open their issues there as well. I'll try and bring this back to the community. I never got around to implementing fixes myself sadly as EOY is quite busy for me.
If there is an 'official' community fork, I will glad to summit my patch.
Hello, have there been any updates on this? Or is there now a community branch that I can use? Thanks :)
Hey @ReaderGuy42, sorry I haven't been on top of this. Let me look around and get back to you.
Hi @AB1908, thanks!
I have a fork that adds proper support for exporting files with embeds of blocks and headings - if there is a new effort, I will merge my fixes in there. I'm not a JS dev so I don't want to take ownership :).
I have a fork that adds proper support for exporting files with embeds of blocks and headings - if there is a new effort, I will merge my fixes in there. I'm not a JS dev so I don't want to take ownership :).
That'd be cool. A while ago I tried installing something like that and it was over my head, so I'm going to wait on installing your fork, because I don't understand npm. But keep me up to date if this gets put in with the Community plugins :) Thanks!
No worries :) It's not that hard just to use pandoc on its own for now to convert a .md to a .docx, for example. I actually also just tried BRAT for @phillipjohnston's fork but it told me the repo was incomplete, I think because a main.js
is missing.
Thanks :)
I just uploaded the files @ReaderGuy42. If BRAT still doesn't work email me (address in profile) so we don't clutter this thread.
I just uploaded the files @ReaderGuy42. If BRAT still doesn't work email me (address in profile) so we don't clutter this thread.
Works perfectly, awesome! Thanks :)
@argenos, can you fork @phillipjohnston's fork?
Might be best if @phillipjohnston makes a PR to master in https://github.com/obsidian-community/obsidian-pandoc/ https://github.com/obsidian-community/obsidian-pandoc/.
Happy to.
Hey everyone! The fork obsidian-community/obsidian-pandoc now has a release and can be installed via BRAT. It will have to be installed this way till we can fix the listing on community plugins. Meanwhile, if anyone wants to help with migrating issues over to the new repo and with reaching out to folks who have updated forks, it would be greatly appreciated!
Hi Oliver. Before we start any discussion, we want to give you a massive thanks for all the time and effort you've put into creating this plugin. A ton of people, myself included, use the plugin for our Obsidian workflows. You've kept up the spirit of Obsidian by helping us do more inside our favorite PKM tool.
We understand that not everyone has the time to maintain and respond to issues. Active development can be challenging when there are other things to attend to and that sometimes it can be taxing to think of "pending work". You're probably well aware that there's a number of issues with some people eagerly awaiting fixes.
A few of us would love to step in and help out in whatever way we can. Although some people have offered to implement fixes, it's hard to merge them without the right permissions. On that note, we wanted to ask if you were willing to transfer ownership of the repo to either a willing member or an organization maintained by the Obsidian community. It's a difficult decision to make right away so please take your time and let us know how you feel about this. In case you wish that we take some other route like forking the repo, that's fine by us as well.
At the end of the day, we're happy that you've done so much for the community and we want to take your work further. We hope you can let us know soon! In the event that it takes longer than a month for you to respond, we'll be continuing with bug fixes in a fork and we can decide where to go from there.
Link to relevant discussion: https://discord.com/channels/686053708261228577/840286264964022302/912325658657554442