Oleksii Shmalko

Looks like an instance of #15

@2Belette, I believe #20 should fix that.

oh, org-use-sub-superscripts is already implemented now, so the only thing left is to pass correct configuration from org-roam-ui See https://github.com/rasendubi/uniorg/blob/11ef10311b05ebd4d0dea80a7f4c51d4aa82edcf/packages/uniorg-parse/src/parse-options.ts#L14 for config documentation

Just looked into this again and it seems to be even more complicated than that. @ispringle your last solution fails on nested children with newlines: ```org-mode #+begin_verse some text *and...

UPD: I am currently experimenting with Astro and published an `astro-org` integration that allows importing `.org` files in JS/Astro. It can be used as follows. In astro.config.mjs: ```js import org...

Cool, what unsoundness is possible?

Sure. What rule is violated? What are the safety requirements of parameters?

Hey. `uniorg-rehype` is specifically an org-to-html converter (rehype/hast is an AST representation of HTML), so I'm not sure what you mean by supporting more backends. There are multiple ways to...

Hey, you're correct that `#+NAME:` and `#+CAPTION:` are ignored by `uniorg-rehype`. I think the good behavior is to transform ```org-mode #+CAPTION: hello [[image.png]] ``` into: ```html hello ``` I think...

Definitely in the scope of the project. This is also closely related to #+OPTIONS as they also influence how file is parsed. The main challenge with these is that they...