docling-core: export DoclingDocument to markdown/text locally (Python parity)

Open
#557 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java
Domain
backend

Research direction

Start by reading the DoclingDocument JSON model and comparing the requested local export behavior with Python's markdown and text exports. Implement and verify markdown/text output from archived Docling JSON without re-parsing the original file or using a Serve round-trip; done means both local export forms are available through the proposed API.

Written by the indexing model from the issue text.

Description

DoclingDocument in Java deserializes from JSON, but there is no local export API (export_to_markdown() / text) like in Python.

We persist Docling JSON as canonical artifact and need text/md in later (async) document processing stages (moderation, etc.) without re-parsing the original file and without a Serve round-trip (JSON_DOCLING → md|text works but adds HTTP coupling).

Proposal: add local export in docling-core, e.g. toMarkdown() / toText().

Use case: offline/async workers reading archived JSON only.

Dominant language
Java
Stars
136
Forks
26
Avg merge
1d 1h
Merged PRs (30d)
47

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docling-project/docling-java

All issues in docling-project/docling-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.