gitonthescene

[This](https://github.com/k2052/org-to-markdown) might be of interest.

That first line looks like [headline](https://orgmode.org/manual/Headlines.html#Headlines) in org-mode, not the beginning of [bold text](https://orgmode.org/manual/Emphasis-and-Monospace.html#Emphasis-and-Monospace). Do you use org-mode in emacs? What does it look like there?

I've now incorporated [orga-stringify](https://github.com/gitonthescene/orgajs/tree/master/packages/orga-stringify) into my fork. It's just pure javascript currently. But when you run the following code on [this sample org file](https://github.com/higham/org-mode-syntax-cheat-sheet.git) it differs from the orginal only...

The head version of my fork now handles the trailing newline. Moreover, it completely reproduces all of the test examples but three. It renumbers two list examples where the numbers...

Hey there, Not that this needs to be a goal to have these line up, but for curiosity sake I wrote the following tiny `elisp` function to have a look...

Also, to align with the unified structure maybe orga-unified should be called orga-parse sort of like [remark-parse](https://github.com/remarkjs/remark/tree/master/packages/remark-parse) and there can be another package with a frozen parser like [remark](https://github.com/remarkjs/remark/tree/master/packages/remark). Or...

It would be great to get a reply here. The more full featured the tools are the more likely they are to be used.

Thanks. You're welcome to play with my fork. I'm happy to answer any questions you might have.

Hey, thanks for getting back. I think it makes sense to put in all the tokens until they become a performance problem and even then make the level of detail...

If you mean you want to keep unified wrappers separate from a core orga library, I think that that makes sense. One of the things I like about the unified...