You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the system supports referencing images using URIs in markdown formatting, which has proven valuable for many data pipeline implementations. For example:
Proposed Enhancement
I propose extending this URI reference functionality to table images as well. This addition would provide more flexibility in document handling, particularly in cases where current markdown tables created may not be correct.
Technical Implementation
I've already prototyped a similar functionality using the following approach:
Store image data in item.image and its URI in item.image.uri using the item.get_image()
Implement reference handling through the existing image processing pipeline:
Hello sir. I wonder that referencing images using URIs in markdown formatting, which has proven valuable for many data pipeline implementations? Why URIs are better than text/table in the output of markdown by OCR? Could you give me some cases or prove?
Requested feature
Background
Currently, the system supports referencing images using URIs in markdown formatting, which has proven valuable for many data pipeline implementations. For example:
Proposed Enhancement
I propose extending this URI reference functionality to table images as well. This addition would provide more flexibility in document handling, particularly in cases where current markdown tables created may not be correct.
Technical Implementation
I've already prototyped a similar functionality using the following approach:
Store image data in item.image and its URI in item.image.uri using the item.get_image()
Implement reference handling through the existing image processing pipeline:
I think this would enable extensibility of pipelines using docling and very beneficial to do various kinds of post-processing on table images.
...
Alternatives
...
The text was updated successfully, but these errors were encountered: