Replies: 4 comments 1 reply
-
|
I guess not |
Beta Was this translation helpful? Give feedback.
-
|
From my point of view, Loop support is probably less about a direct file converter and more about whether there is a stable export or API path that can turn Loop content into something MarkItDown can reason about reliably. Without that intermediate representation, support tends to become brittle very quickly. If there is a Graph or export-based route, documenting that integration path may be more realistic than pretending Loop is just another ordinary document format. |
Beta Was this translation helpful? Give feedback.
-
|
I don’t think MarkItDown supports Microsoft Loop directly right now. Loop is not listed in the supported input formats in the README. So the practical path would be to export the Loop content to something MarkItDown already supports, like HTML, PDF, or Word, and convert that instead. So: not direct support, but possibly via export first. |
Beta Was this translation helpful? Give feedback.
-
|
Looking into this for a use case I have, has anyone experimented with exporting .loop to any of these formats? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Does this support conversion from microsoft Loop documents, we have all our document sin microsoft loop, we need a way to share them to llm
Beta Was this translation helpful? Give feedback.
All reactions