docling-parse 1.3.0__tar.gz → 1.3.1__tar.gz

docling_parse-1.3.1/CHANGELOG.md

@@ -0,0 +1,88 @@
+## [v1.3.1](https://github.com/DS4SD/docling-parse/releases/tag/v1.3.1) - 2024-09-30
+
+### Fix
+
+* Sdist and wheels content ([#28](https://github.com/DS4SD/docling-parse/issues/28)) ([`f3febc5`](https://github.com/DS4SD/docling-parse/commit/f3febc53a2a6565b16847113633f92d1a2dab48a))
+
+## [v1.3.0](https://github.com/DS4SD/docling-parse/releases/tag/v1.3.0) - 2024-09-20
+
+### Feature
+
+* Add windows support ([#22](https://github.com/DS4SD/docling-parse/issues/22)) ([`05e6aa3`](https://github.com/DS4SD/docling-parse/commit/05e6aa30d6de76694cf7f04be2633b2f5e129ef2))
+
+## [v1.2.1](https://github.com/DS4SD/docling-parse/releases/tag/v1.2.1) - 2024-09-18
+
+### Fix
+
+* Clean code ([#20](https://github.com/DS4SD/docling-parse/issues/20)) ([`992df42`](https://github.com/DS4SD/docling-parse/commit/992df4235ca624b47ce63be71592fa895c732e07))
+
+## [v1.2.0](https://github.com/DS4SD/docling-parse/releases/tag/v1.2.0) - 2024-09-09
+
+### Feature
+
+* Build linux arm64 architecture ([#17](https://github.com/DS4SD/docling-parse/issues/17)) ([`3f51a2c`](https://github.com/DS4SD/docling-parse/commit/3f51a2c571259491a79899db02cfe2de26a5c17f))
+
+## [v1.1.3](https://github.com/DS4SD/docling-parse/releases/tag/v1.1.3) - 2024-08-30
+
+### Fix
+
+* Resolve more assert errors ([#16](https://github.com/DS4SD/docling-parse/issues/16)) ([`c3a6b03`](https://github.com/DS4SD/docling-parse/commit/c3a6b038571909a41b3abd237215b756c3eacc62))
+
+## [v1.1.2](https://github.com/DS4SD/docling-parse/releases/tag/v1.1.2) - 2024-08-29
+
+### Fix
+
+* Out-of-range vector error ([#15](https://github.com/DS4SD/docling-parse/issues/15)) ([`4ed034c`](https://github.com/DS4SD/docling-parse/commit/4ed034cc0fb3988a9216e3574b9f34c155dae452))
+
+## [v1.1.1](https://github.com/DS4SD/docling-parse/releases/tag/v1.1.1) - 2024-08-23
+
+### Fix
+
+* Replace assert with exceptions ([#12](https://github.com/DS4SD/docling-parse/issues/12)) ([`6565f32`](https://github.com/DS4SD/docling-parse/commit/6565f32bdeb17d9796a94ccf3c8f8c4e0e73bf49))
+
+## [v1.1.0](https://github.com/DS4SD/docling-parse/releases/tag/v1.1.0) - 2024-08-22
+
+### Feature
+
+* Deal with qpdf errors on a page by page basis ([#11](https://github.com/DS4SD/docling-parse/issues/11)) ([`400fcb3`](https://github.com/DS4SD/docling-parse/commit/400fcb30b1813206bb98a17d85537af1471837a2))
+
+## [v1.0.0](https://github.com/DS4SD/docling-parse/releases/tag/v1.0.0) - 2024-08-22
+
+### Feature
+
+* Adding load/unload from key ([#9](https://github.com/DS4SD/docling-parse/issues/9)) ([`dd122d0`](https://github.com/DS4SD/docling-parse/commit/dd122d0c938e0054d22540949c9ee5b839c34c54))
+
+### Breaking
+
+* adding load/unload from key ([#9](https://github.com/DS4SD/docling-parse/issues/9)) ([`dd122d0`](https://github.com/DS4SD/docling-parse/commit/dd122d0c938e0054d22540949c9ee5b839c34c54))
+
+## [v0.3.1](https://github.com/DS4SD/docling-parse/releases/tag/v0.3.1) - 2024-08-22
+
+### Fix
+
+* Resolve segfaults ([#8](https://github.com/DS4SD/docling-parse/issues/8)) ([`8ab088d`](https://github.com/DS4SD/docling-parse/commit/8ab088daf07c2c1d959aab79d0845e2181667b0e))
+
+## [v0.3.0](https://github.com/DS4SD/docling-parse/releases/tag/v0.3.0) - 2024-08-21
+
+### Feature
+
+* Read page by page ([#7](https://github.com/DS4SD/docling-parse/issues/7)) ([`92e02ec`](https://github.com/DS4SD/docling-parse/commit/92e02ec4c1bdfc3e5cb899de8ea0e3384848560d))
+
+## [v0.2.0](https://github.com/DS4SD/docling-parse/releases/tag/v0.2.0) - 2024-08-13
+
+### Feature
+
+* Add reading from BytesIO ([#6](https://github.com/DS4SD/docling-parse/issues/6)) ([`195777b`](https://github.com/DS4SD/docling-parse/commit/195777b656969d5021b7d8d55d2d208b61dfcb0f))
+
+## [v0.1.0](https://github.com/DS4SD/docling-parse/releases/tag/v0.1.0) - 2024-08-07
+
+### Feature
+
+* First release to pypi ([#4](https://github.com/DS4SD/docling-parse/issues/4)) ([`f762774`](https://github.com/DS4SD/docling-parse/commit/f762774a8db2bd198b9c017a36a25fdd98ac1b41))
+
+## [v0.0.1](https://github.com/DS4SD/docling-parse/releases/tag/v0.0.1) - 2024-08-07
+
+### Fix
+
+* Unit-tests ([#3](https://github.com/DS4SD/docling-parse/issues/3)) ([`fa7bef7`](https://github.com/DS4SD/docling-parse/commit/fa7bef7f35209d7f3d3d4a3eef37f704f94c9cac))
+* Add and fix cli ([#1](https://github.com/DS4SD/docling-parse/issues/1)) ([`ccb7675`](https://github.com/DS4SD/docling-parse/commit/ccb7675e248f9aba088a4b0c846caf7363be14bc))

docling_parse-1.3.1/CMakeLists.txt

@@ -0,0 +1,176 @@
+cmake_minimum_required(VERSION 3.12)
+
+project(docling_parse VERSION 1.0.0 LANGUAGES CXX C)
+#set(CMAKE_VERBOSE_MAKEFILE off)
+
+message(STATUS "cmake osx-deployment: " ${CMAKE_OSX_DEPLOYMENT_TARGET})
+
+# minimum macosx, ignored on other platforms
+if(APPLE)
+    if(NOT CMAKE_OSX_DEPLOYMENT_TARGET)
+        message(STATUS "cmake is not set")            
+    elseif(CMAKE_OSX_DEPLOYMENT_TARGET VERSION_LESS 10.15)
+        set(CMAKE_OSX_DEPLOYMENT_TARGET "10.15" CACHE STRING "Minimum macOS version" FORCE)
+    endif()
+endif()
+
+message(STATUS "cmake system-version: " ${CMAKE_SYSTEM_VERSION})
+message(STATUS "cmake osx-deployment: " ${CMAKE_OSX_DEPLOYMENT_TARGET})
+
+# ************************
+# ***     paths        ***
+# ************************
+
+if(NOT DEFINED TOPLEVEL_PREFIX_PATH)
+    set(TOPLEVEL_PREFIX_PATH ${CMAKE_CURRENT_SOURCE_DIR})
+endif()
+
+if(NOT DEFINED CMAKE_INSTALL_PREFIX)
+    set(CMAKE_INSTALL_PREFIX ${TOPLEVEL_PREFIX_PATH}/install_dir)
+endif()
+
+if(NOT DEFINED EXTERNALS_PREFIX_PATH)
+    set(EXTERNALS_PREFIX_PATH "${TOPLEVEL_PREFIX_PATH}/externals" CACHE INTERNAL "")
+endif()
+
+if(NOT DEFINED RESOURCES_PREFIX_PATH)
+    set(RESOURCES_PREFIX_PATH "${TOPLEVEL_PREFIX_PATH}/resources" CACHE INTERNAL "")
+endif()
+
+if(NOT "${TOPLEVEL_PREFIX_PATH}/cmake" IN_LIST CMAKE_MODULE_PATH)
+    set(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} "${TOPLEVEL_PREFIX_PATH}/cmake")
+endif()
+
+if(NOT DEFINED CMAKE_PDF_DATA_DIR)
+    set(CMAKE_PDF_DATA_DIR "${TOPLEVEL_PREFIX_PATH}/docling_parse/pdf_resources")
+endif()
+
+set(ENV_ARCH $ENV{CIBW_ARCHS})
+message(STATUS "cibw arch: " ${ENV_ARCH})
+
+set(CMAKE_OSX_ARCHITECTURES $ENV{CIBW_ARCHS})
+#message(STATUS "cibw arch: " ${ENV_ARCH})
+
+set(ENV_ARCHFLAGS $ENV{ARCHFLAGS})
+message(STATUS "arch flags: " ${ENV_ARCHFLAGS})
+
+message(STATUS "      top path: " ${TOPLEVEL_PREFIX_PATH})
+message(STATUS "      lib path: " ${EXTERNALS_PREFIX_PATH})
+message(STATUS "  install path: " ${CMAKE_INSTALL_PREFIX})
+message(STATUS "    cmake path: " ${CMAKE_MODULE_PATH})
+message(STATUS "  cmake system: " ${CMAKE_SYSTEM_PROCESSOR})
+message(STATUS "cmake osx arch: " ${CMAKE_OSX_ARCHITECTURES})
+
+# ************************
+# ***  cxx-flags       ***
+# ************************
+
+set(CMAKE_CXX_STANDARD          20)
+set(CMAKE_CXX_STANDARD_REQUIRED ON)
+
+#set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wall -Wno-sign-compare -g3 -DROOT_PATH='\"${TOPLEVEL_PREFIX_PATH}\"' ${ENV_ARCHFLAGS}")
+#set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wall -Wno-sign-compare -O3 -DROOT_PATH='\"${TOPLEVEL_PREFIX_PATH}\"' ${ENV_ARCHFLAGS}")
+
+if (WIN32)
+    set(TEST_PATH "\\\"${TOPLEVEL_PREFIX_PATH}\\\"")
+    add_definitions(-DROOT_PATH="\\\"${TOPLEVEL_PREFIX_PATH}\\\"")
+    set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wall -Wno-sign-compare -O3 ${ENV_ARCHFLAGS}")
+else()
+    set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wall -Wno-sign-compare -O3 -DROOT_PATH='\"${TOPLEVEL_PREFIX_PATH}\"' ${ENV_ARCHFLAGS}")
+endif()
+
+message(STATUS "cxx-compiler: " ${CMAKE_CXX_COMPILER})
+message(STATUS "cxx-flags   : " ${CMAKE_CXX_FLAGS})
+message(STATUS "cxx-standard: " ${CMAKE_CXX_STANDARD})
+
+# ************************
+# *** libraries        ***
+# ************************
+
+if(NOT EXISTS ${EXTERNALS_PREFIX_PATH})
+  execute_process(COMMAND mkdir ${EXTERNALS_PREFIX_PATH})
+  execute_process(COMMAND mkdir ${EXTERNALS_PREFIX_PATH}/bin)
+  execute_process(COMMAND mkdir ${EXTERNALS_PREFIX_PATH}/lib)
+  execute_process(COMMAND mkdir ${EXTERNALS_PREFIX_PATH}/include)
+  execute_process(COMMAND mkdir ${EXTERNALS_PREFIX_PATH}/resources)
+endif()
+
+include(cmake/subdirlist.cmake)
+
+include(cmake/extlib_json.cmake)
+include(cmake/extlib_utf8.git.cmake)
+include(cmake/extlib_jpeg.cmake)
+# include(cmake/extlib_qpdf_v10.cmake)
+include(cmake/extlib_qpdf_v11.cmake)
+# include(cmake/extlib_pybind11.cmake)
+
+include(cmake/os_opts.cmake)
+
+# ***********************
+# ***  includes       ***
+# ***********************
+
+include_directories(${EXTERNALS_PREFIX_PATH}/include)
+
+subdirlist(EXTERNALS_INCLUDES ${EXTERNALS_PREFIX_PATH}/include)	
+include_directories(${EXTERNALS_INCLUDES})
+
+message(STATUS "subdirs: " ${SUBDIRS})
+
+include_directories(${TOPLEVEL_PREFIX_PATH}/src)
+
+subdirlist(SUBDIRS ${TOPLEVEL_PREFIX_PATH}/src)
+include_directories(${SUBDIRS})
+
+# **********************
+# ***  Executables   ***
+# **********************
+
+add_executable(parse.exe "${TOPLEVEL_PREFIX_PATH}/app/parse.cpp")
+
+set_property(TARGET parse.exe PROPERTY CXX_STANDARD 20)
+
+target_link_libraries(parse.exe ${LIB_LINK})
+
+# **********************
+# ***  Libraries     ***
+# **********************
+
+add_library(parse STATIC "${TOPLEVEL_PREFIX_PATH}/app/parse.cpp")
+
+set_target_properties(parse PROPERTIES POSITION_INDEPENDENT_CODE ON)
+
+target_link_libraries(parse ${LIB_LINK})
+
+# ***************************
+# ***  Python-binding     ***
+# ***************************
+
+# https://pybind11.readthedocs.io/en/stable/compiling.html
+find_package (Python COMPONENTS Interpreter Development)
+find_package(pybind11 CONFIG REQUIRED)
+
+pybind11_add_module(docling_parse "${TOPLEVEL_PREFIX_PATH}/app/pybind_parse.cpp")
+
+add_dependencies(docling_parse json utf8)  # we have to list the headers-only deps here
+target_compile_definitions(docling_parse PRIVATE VERSION_INFO=${EXAMPLE_VERSION_INFO})
+
+target_link_libraries(docling_parse PRIVATE parse)
+
+# *****************
+# ***  Install  ***
+# *****************
+
+install(TARGETS docling_parse DESTINATION "${TOPLEVEL_PREFIX_PATH}/docling_parse")
+
+# *****************
+# ***  Testing  ***
+# *****************
+
+#function(do_test target arg result)
+#  add_test(NAME Comp${arg} COMMAND ${target} ${arg})
+#  set_tests_properties(Comp${arg} PROPERTIES PASS_REGULAR_EXPRESSION ${result})
+# endfunction()
+
+# do a bunch of result based tests
+# do_test(Tutorial 4 "4 is 2")

docling_parse-1.3.1/CODE_OF_CONDUCT.md

@@ -0,0 +1,129 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement using
+[deepsearch-core@zurich.ibm.com](mailto:deepsearch-core@zurich.ibm.com).
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html).
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+Homepage: [https://www.contributor-covenant.org](https://www.contributor-covenant.org)
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are available at
+[https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations).

docling_parse-1.3.1/CONTRIBUTING.md

@@ -0,0 +1,163 @@
+## Contributing In General
+Our project welcomes external contributions. If you have an itch, please feel
+free to scratch it.
+
+To contribute code or documentation, please submit a [pull request](https://github.com/DS4SD/docling-parse/pulls).
+
+A good way to familiarize yourself with the codebase and contribution process is
+to look for and tackle low-hanging fruit in the [issue tracker](https://github.com/DS4SD/docling-parse/issues).
+Before embarking on a more ambitious contribution, please quickly [get in touch](#communication) with us.
+
+For general questions or support requests, please refer to the [discussion section](https://github.com/DS4SD/docling-parse/discussions).
+
+**Note: We appreciate your effort, and want to avoid a situation where a contribution
+requires extensive rework (by you or by us), sits in backlog for a long time, or
+cannot be accepted at all!**
+
+### Proposing new features
+
+If you would like to implement a new feature, please [raise an issue](https://github.com/DS4SD/docling-parse/issues)
+before sending a pull request so the feature can be discussed. This is to avoid
+you wasting your valuable time working on a feature that the project developers
+are not interested in accepting into the code base.
+
+### Fixing bugs
+
+If you would like to fix a bug, please [raise an issue](https://github.com/DS4SD/docling-parse/issues) before sending a
+pull request so it can be tracked.
+
+### Merge approval
+
+The project maintainers use LGTM (Looks Good To Me) in comments on the code
+review to indicate acceptance. A change requires LGTMs from two of the
+maintainers of each component affected.
+
+For a list of the maintainers, see the [MAINTAINERS.md](MAINTAINERS.md) page.
+
+
+## Legal
+
+Each source file must include a license header for the MIT
+Software. Using the SPDX format is the simplest approach.
+e.g.
+
+```
+/*
+Copyright IBM Inc. All rights reserved.
+
+SPDX-License-Identifier: MIT
+*/
+```
+
+We have tried to make it as easy as possible to make contributions. This
+applies to how we handle the legal aspects of contribution. We use the
+same approach - the [Developer's Certificate of Origin 1.1 (DCO)](https://github.com/hyperledger/fabric/blob/master/docs/source/DCO1.1.txt) - that the Linux® Kernel [community](https://elinux.org/Developer_Certificate_Of_Origin)
+uses to manage code contributions.
+
+We simply ask that when submitting a patch for review, the developer
+must include a sign-off statement in the commit message.
+
+Here is an example Signed-off-by line, which indicates that the
+submitter accepts the DCO:
+
+```
+Signed-off-by: John Doe <john.doe@example.com>
+```
+
+You can include this automatically when you commit a change to your
+local git repository using the following command:
+
+```
+git commit -s
+```
+
+
+## Communication
+
+Please feel free to connect with us using the [discussion section](https://github.com/DS4SD/docling-parse/discussions).
+
+
+
+## Developing
+
+### Usage of Poetry
+
+We use Poetry to manage dependencies.
+
+
+#### Install
+
+To install, see the documentation here: https://python-poetry.org/docs/master/#installing-with-the-official-installer
+
+1. Install the Poetry globally in your machine
+    ```bash
+    curl -sSL https://install.python-poetry.org | python3 -
+    ```
+    The installation script will print the installation bin folder `POETRY_BIN` which you need in the next steps.
+
+2. Make sure Poetry is in your `$PATH`
+    - for `zsh`
+        ```sh
+        echo 'export PATH="POETRY_BIN:$PATH"' >> ~/.zshrc
+        ```
+    - for `bash`
+        ```sh
+        echo 'export PATH="POETRY_BIN:$PATH"' >> ~/.bashrc
+        ```
+
+3. The official guidelines linked above include useful details on the configuration of autocomplete for most shell environments, e.g. Bash and Zsh.
+
+
+#### Create a Virtual Environment and Install Dependencies
+
+To activate the Virtual Environment, run:
+
+```bash
+poetry shell
+```
+
+To spawn a shell with the Virtual Environment activated. If the Virtual Environment doesn't exist, Poetry will create one for you. Then, to install dependencies, run:
+
+```bash
+poetry install
+```
+
+**(Advanced) Use a Specific Python Version**
+
+If for whatever reason you need to work in a specific (older) version of Python, run:
+
+```bash
+poetry env use $(which python3.9)
+```
+
+This creates a Virtual Environment with Python 3.9. For other versions, replace `$(which python3.9)` by the path to the interpreter (e.g., `/usr/bin/python3.9`) or use `$(which pythonX.Y)`.
+
+
+#### Add a new dependency
+
+```bash
+poetry add NAME
+```
+
+## Coding style guidelines
+
+We use the following tools to enforce code style:
+
+- iSort, to sort imports
+- Black, to format code
+
+
+We run a series of checks on the code base on every commit, using `pre-commit`. To install the hooks, run:
+
+```bash
+pre-commit install
+```
+
+To run the checks on-demand, run:
+
+```
+pre-commit run --all-files
+```
+
+Note: Checks like `Black` and `isort` will "fail" if they modify files. This is because `pre-commit` doesn't like to see files modified by their Hooks. In these cases, `git add` the modified files and `git commit` again.
+

docling_parse-1.3.1/MAINTAINERS.md

@@ -0,0 +1,9 @@
+# MAINTAINERS
+
+- Christoph Auer - [@cau-git](https://github.com/cau-git)
+- Michele Dolfi - [@dolfim-ibm](https://github.com/dolfim-ibm)
+- Maxim Lysak - [@maxmnemonic](https://github.com/maxmnemonic)
+- Panos Vagenas - [@vagenas](https://github.com/vagenas)
+- Peter Staar - [@PeterStaar-IBM](https://github.com/PeterStaar-IBM)
+
+Maintainers can be contacted at [deepsearch-core@zurich.ibm.com](mailto:deepsearch-core@zurich.ibm.com).

{docling_parse-1.3.0 → docling_parse-1.3.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: docling-parse
-Version: 1.3.0
+Version: 1.3.1
 Summary: Simple package to extract text with coordinates from programmatic PDFs
 Home-page: https://github.com/DS4SD/docling-parse
 License: MIT