unstructured/typings/docx/oxml/table.pyi

"""Table-related XML element-types."""

from __future__ import annotations

from typing import List

from docx.oxml.xmlchemy import BaseOxmlElement

class CT_Row(BaseOxmlElement):
    tc_lst: List[CT_Tc]

class CT_Tc(BaseOxmlElement):
    @property
    def vMerge(self) -> str | None: ...

class CT_Tbl(BaseOxmlElement): ...
fix(docx): Table.text duplicates merged cell text (#2134) Summary. The `python-docx` table API is designed for _uniform_ tables (no merged cells, no nested tables). Naive processing of DOCX tables using this API produces duplicate text when the table has merged cells. Add a more sophisticated parsing method that reads only "root" cells (those with an actual `<tc>` element) and skip cells spanned by a merge. In the process, abandon use of the `tabulate` package for this job (which is also designed for uniform tables) and remove the whitespace padding it adds for visual alignment of columns. Separate the text for each cell with a single newline ("\n"). Since it's little extra trouble, add support for nested tables such that their text also contributes to the `Table.text` string. The new `._iter_table_texts()` method will also be used for parsing tables in headers and footers (where they are frequently used for layout purposes) in a closely following PR. Fixes #2106. 2023-11-21 14:22:40 -08:00			`"""Table-related XML element-types."""`

			`from __future__ import annotations`

			`from typing import List`

rfctr: docx partitioning (#1422) Reviewers: I recommend reviewing commit-by-commit or just looking at the final version of `partition/docx.py` as View File. This refactor solves a few problems but mostly lays the groundwork to allow us to refine further aspects such as page-break detection, list-item detection, and moving python-docx internals upstream to that library so our work doesn't depend on that domain-knowledge. 2023-09-19 15:32:46 -07:00			`from docx.oxml.xmlchemy import BaseOxmlElement`

fix(docx): Table.text duplicates merged cell text (#2134) Summary. The `python-docx` table API is designed for _uniform_ tables (no merged cells, no nested tables). Naive processing of DOCX tables using this API produces duplicate text when the table has merged cells. Add a more sophisticated parsing method that reads only "root" cells (those with an actual `<tc>` element) and skip cells spanned by a merge. In the process, abandon use of the `tabulate` package for this job (which is also designed for uniform tables) and remove the whitespace padding it adds for visual alignment of columns. Separate the text for each cell with a single newline ("\n"). Since it's little extra trouble, add support for nested tables such that their text also contributes to the `Table.text` string. The new `._iter_table_texts()` method will also be used for parsing tables in headers and footers (where they are frequently used for layout purposes) in a closely following PR. Fixes #2106. 2023-11-21 14:22:40 -08:00			`class CT_Row(BaseOxmlElement):`
			`tc_lst: List[CT_Tc]`

			`class CT_Tc(BaseOxmlElement):`
			`@property`
			`def vMerge(self) -> str \| None: ...`

rfctr: docx partitioning (#1422) Reviewers: I recommend reviewing commit-by-commit or just looking at the final version of `partition/docx.py` as View File. This refactor solves a few problems but mostly lays the groundwork to allow us to refine further aspects such as page-break detection, list-item detection, and moving python-docx internals upstream to that library so our work doesn't depend on that domain-knowledge. 2023-09-19 15:32:46 -07:00			`class CT_Tbl(BaseOxmlElement): ...`