This is great, working on a soon to launch Markdown editor soon so this is especially relevant. I'll play around with it later but I'm curious, how are you deciding pagination boundaries? I've found word and docx and various open source projects vary on philosophy and implementation.
Thanks! Our core product is a Word editor that you can embed in your React / Vue app. So we just repurposed the layout engine to be an accurate converter. You can see how our layout engine "sees" the document in the left tab of the demo.
I've been doing some writing things where they use Docx and I use Markdown (have been since before the LLM craze). Boy is it annoying to go back and forth, will be trying the one direction anyhow
1. I have markdown, I want a docx version, that is equivalent to html rendering, markdown's whole point, almost certainly many options out there
2. I have docx, I want to make edits in markdown (because vim motions), need to sync those edits back. Ideally just some value swaps in the "DOM"
It may very well be the case that Office now supports Markdown natively. I seem to recall possibly seeing that. Google Workspace is as well iirc. One of the two already had support, the other was just releasing the first takes (back when I last looked )
I've been doing some writing things where they use Docx and I use Markdown (have been since before the LLM craze). Boy is it annoying to go back and forth, will be trying the one direction anyhow
1. I have markdown, I want a docx version, that is equivalent to html rendering, markdown's whole point, almost certainly many options out there
2. I have docx, I want to make edits in markdown (because vim motions), need to sync those edits back. Ideally just some value swaps in the "DOM"
It may very well be the case that Office now supports Markdown natively. I seem to recall possibly seeing that. Google Workspace is as well iirc. One of the two already had support, the other was just releasing the first takes (back when I last looked )