This is a process I discovered by accident, but it works really well. It takes a bit of setup for pandoc because one has to install homebrew from the terminal and Xcode command-line tools first, then it’s just brew install pandoc after that.
Perhaps Bear could include pandoc so they could offer more import options, or leverage their export options technology into import options.
Pandoc is released under the GPL license and can’t be included in commercial software unless released as open source.
Makes sense. Could there be a way to use whatever technology you use for export for import?
Our importer and exporters are developed internally and the code is not accessible but you can use the Shortcuts export action.
I was thinking all along “programming by you internally”, and not programming by me. Of course, I don’t have access to your internal code!
But I will try shortcuts since you say it’s accessible there.
Waited for a few days so I could come at this fresh: I was wondering if you could adapt your internal exporters also for import, so the types of files that are available for export could be available for import as well. I’m using Bear as storage for all of my non-image documents. I would never try to import my years of receipts, for instance.
Bear ≠ Evernote.
That way I wouldn’t need Typora + pandoc.
The main issue here is attachments. They are imported for Texbundles, .bear, and Markdown, and partially RTF. For HTML it’s a little complex to discern between standard links and attachment links on import.
For ePub, PDF, and Images, it can’t work because the format doesn’t hold generic attachments.
Then I’ll keep using Typora + pandoc 