New in docx2python Version 3

Better type hints for DocxOutput properties. You should never get an "or" or "Any" type hint for the nested lists returned by Docx2Python.
Support for "strict" namespaces. Word uses a superset of the standard Open Office XML format. Work can restrict itself to the standard by saving with the "strict" namespace. This is now supported.
Tables exported as nested lists are now always nxm (n rows, m columns). This will simplify converting tables to markdown or other data types. Where duplicate_merged_cells is True, the table will be filled to nxm with content from adjacent cells. Where false, the table will be filled to nxm with empty cells.
Tables can now be identified without guessing games (see Par Type).
Word's paragraph styles are now exposed (e.g., Heading 2, Subtitle, Subtle Emphasis - see Par Type). If html=True, these will be exported as html tags where an obvious mapping exists (e.g., Heading 1 -> h1).
A paragraphs's position in a nested list is now exposed (see Par Type).
Input boolean arguments 'html' (False) and 'duplicate_merged_cells' (True) are now keyword only.

Par Type

New in Docx2Python Version 3, the Par type captures some paragraph properties.

html_style: list[str]

A list of html tags that will be applied to the paragraph if html=True.

style: str

The MS Word paragraph style (e.g., Heading 2, Subtitle, Subtle Emphasis), if any. This will facilitate finding headings, etc.

lineage: ("document", str | None, str | None, str | None, str | None)

Docx2Python partially flattens the xml spaghetti so that a paragraph is always at depth 4. This often means building structure where none exists, so the lineage [ostensibly (great-great-grandparent, great-grandparent, grandparent, parent, self)] is not always straightforward. But there are some patterns you can depend on. The most requested is that paragraphs in table cells will always have a lineage of ("document", "tbl", something, something, "p"). Use iter_tables and is_tbl from the docx2python.iterators module to find tables in your document. There is an example in tests/test_tables_to_markdown.py.

runs: list[Run]

A list of Run instances. Each Run instance has html_style and text attributes. This will facilitate finding and extracting text with specific formatting.

list_position: tuple[str | None, list[int]]

The address of a paragraph in a nested list. The first item in the tuple is a string identifier for the list. These are extracted from Word, and may look like indices, but they are not. List "2" might come before list "1" in the document. The second item is a list of indices to show where you are in that list.

1. paragraph  # list_position = ("list_id", [0])
2. paragraph  # list_position = ("list_id", [1])
   a. paragraph  # list_position = ("list_id", [1, 0])
      i. paragraph  # list_position = ("list_id", [1, 0, 0])
   b. paragraph  # list_position = ("list_id", [1, 1])
3. paragraph  # list_position = ("list_id", [2])

docx2python

Extract docx headers, footers, text, footnotes, endnotes, properties, comments, and images to a Python object.

README_DOCX_FILE_STRUCTURE.md may help if you'd like to extend docx2python.

For a summary of what's new in docx2python 2, scroll down to New in docx2python Version 2

For a summary of what's new in docx2python 3, scroll up to New in docx2python Version 3

shared features:

extracts text from docx files
extracts images from docx files

additions:

extracts footnotes and endnotes
converts bullets and numbered lists to ascii with indentation
converts hyperlinks to <a href="http:/...">link text</a>
retains some structure of the original file (more below)
extracts document properties (creator, lastModifiedBy, etc.)
inserts image placeholders in text ('----image1.jpg----')
inserts plain text footnote and endnote references in text ('----footnote1----')
(optionally) retains font size, font color, bold, italics, and underscore as html
extracts math equations
extracts user selections from checkboxes and dropdown menus
extracts comments
extracts some paragraph properties (e.g., Heading 1)
tracks location within numbered lists

subtractions:

no command-line interface
will only work with Python 3.8+

Installation

pip install docx2python

Use

docx2python opens a zipfile object and (lazily) reads it. Use context management (with ... as) to close this zipfile object or explicitly close with docx_content.close().

from docx2python import docx2python

# extract docx content
with docx2python('path/to/file.docx') as docx_content:
    print(docx_content.text)

docx_content = docx2python('path/to/file.docx')
print(docx_content.text)
docx_content.close()

# extract docx content, write images to image_directory
with docx2python('path/to/file.docx', 'path/to/image_directory') as docx_content:
    print(docx_content.text)

# extract docx content with basic font styles converted to html
with docx2python('path/to/file.docx', html=True) as docx_content:
    print(docx_content.text)

Note on html feature:

supports italic, bold, underline, <s>strike, superscript, subscript, small caps, all caps, highlighted, font size, colored text.
hyperlinks will always be exported as html (<a href="http:/...">link text</a>), even if html=False, because I couldn't think of a more canonical representation.
every tag open in a paragraph will be closed in that paragraph (and, where appropriate, reopened in the next paragraph). If two subsequenct paragraphs are bold, they will be returned as paragraph a, paragraph b. This is intentional to make each paragraph its own entity.
if you specify html=True, &, > and < in your docx text will be encoded as &amp, > and <

Return Value

Function docx2python returns a DocxContent instance with several attributes.

header (_runs, _pars) - contents of the docx headers in the return format described herein

footer (_runs, _pars) - contents of the docx footers in the return format described herein

body (_runs, _pars)- contents of the docx in the return format described herein

footnotes (_runs, _pars) - contents of the docx in the return format described herein

endnotes (_runs, _pars) - contents of the docx in the return format described herein

document (_runs, _pars) - header + body + footer (read only)

text - all docx text as one string, similar to what you'd get from python-docx2txt

properties - docx property names mapped to values (e.g., {"lastModifiedBy": "Shay Hill"})

images - image names mapped to images in binary format. Write to filesystem with

for name, image in result.images.items():
    with open(name, 'wb') as image_destination:
        write(image_destination, image)

# or

with docx2python('path/to/file.docx', 'path/to/image/directory') as docx_content:
    ...

# or

with docx2python('path/to/file.docx') as docx_content:
    docx_content.save_images('path/to/image/directory')

__docx_reader__ - a DocxReader (see docx_reader.py) instance with several methods for extracting xml portions.

Arguments

def docx2python(
    docx_filename: str | os.PathLike[str] | BytesIO,
    image_folder: str | os.PathLike[str] | None = None,
    *,
    html: bool = False,
    duplicate_merged_cells: bool = True
) -> DocxContent:
    """
    Unzip a docx file and extract contents.

    :param docx_filename: path to a docx file
    :param image_folder: optionally specify an image folder
        (images in docx will be copied to this folder)
    :param html: bool, extract some formatting as html
    :param duplicate_merged_cells: bool, duplicate merged cells to return a mxn
        nested list for each table (default True)
    :return: DocxContent object
    """

Return Format

(header, footer, body, footnotes, endnotes, document)

Some structure will be maintained. Text will be returned in a nested list, with paragraphs always at depth 4 (i.e., output.body[i][j][k][l] will be a paragraph).

If your docx has no tables, output.body will appear as one a table with all content in one cell:

[  # document
    [  # table
        [  # row
            [  # cell
                "Paragraph 1",
                "Paragraph 2",
                "-- bulleted list",
                "-- continuing bulleted list",
                "1)  numbered list",
                "2)  continuing numbered list"
                "    a)  sublist",
                "        i)  sublist of sublist",
                "3)  keeps track of indention levels",
                "    a)  resets sublist counters"
            ]
        ]
     ]
 ]

Table cells will appear as table cells. Text outside tables will appear as table cells.

A docx document can be tables within tables within tables. Docx2Python flattens most of this to more easily navigate within the content.

(header_runs, footer_runs, body_runs, footnotes_runs, endnotes_runs, document_runs)

Version2 intruduced _run attributes. Instead of a string for each paragraph, each run is a string. This is useful with html=True for picking out italic text or hyperlinks.

[  # document
    [  # table
        [  # row
            [  # cell
                [  # paragraph
                    "a text run", "<i>runs break when formatting changes</i>",
                    "--", "runs break with bullets and special insertions",
                ]
            ]
        ]
     ]
 ]

(header_pars, footer_pars, body_pars, footnotes_pars, endnotes_pars, document_pars)

Version3 introduced _par attributes. These return each paragraph as a Par instance. This is useful for extracting paragraph properties (e.g., Heading 1). See the Par Type heading.

[  # document
    [  # table
        [  # row
            [  # cell
                Par instance,
                Par instance,
                Par instance
            ]
        ]
     ]
 ]

Working with output

This package provides several documented helper functions in the docx2python.iterators module. Here are a few recipes possible with these functions:

from docx2python.iterators import enum_cells

def remove_empty_paragraphs(tables):
    for (i, j, k), cell in enum_cells(tables):
        tables[i][j][k] = [x for x in cell if x]

>>> tables = [[[['a', 'b'], ['a', '', 'd', '']]]]
>>> remove_empty_paragraphs(tables)
    [[[['a', 'b'], ['a', 'd']]]]

from docx2python.iterators import enum_at_depth

def html_map(tables) -> str:
    """Create an HTML map of document contents.

    Render this in a browser to visually search for data.

    :tables: value could come from, e.g.,
        * docx_to_text_output.document
        * docx_to_text_output.body
    """

    # prepend index tuple to each paragraph
    for (i, j, k, l), paragraph in enum_at_depth(tables, 4):
        tables[i][j][k][l] = " ".join([str((i, j, k, l)), paragraph])

    # wrap each paragraph in <pre> tags
    for (i, j, k), cell in enum_at_depth(tables, 3):
        tables[i][j][k] = "".join(["<pre>{x}</pre>".format(x) for x in cell])

    # wrap each cell in <td> tags
    for (i, j), row in enum_at_depth(tables, 2):
        tables[i][j] = "".join(["<td>{x}</td>".format(x) for x in row])

    # wrap each row in <tr> tags
    for (i,), table in enum_at_depth(tables, 1):
        tables[i] = "".join("<tr>{x}</tr>".format(x) for x in table)

    # wrap each table in <table> tags
    tables = "".join(['<table border="1">{x}</table>'.format(x) for x in tables])

    return ["<html><body>"] + tables + ["</body></html>"]

>>> tables = [[[['a', 'b'], ['a', 'd']]]]
>>> html_map(tables)
<html>
    <body>
        <table border="1">
            <tr>
                <td>
                    '(0, 0, 0, 0) a'
                    '(0, 0, 0, 1) b'
                </td>
                <td>
                    '(0, 0, 1, 0) a'
                    '(0, 0, 1, 1) d'
                </td>
            </tr>
        </table>
    </body>
</html>

Some fine print about checkboxes:

MS Word has checkboxes that can be checked any time, and others that can only be checked when the form is locked. The previous print as. \u2610 (open checkbox) or \u2612 (crossed checkbox). Which this module, the latter will too. I gave checkboxes a bailout value of ----checkbox failed---- if the xml doesn't look like I expect it to, because I don't have several-thousand test files with checkboxes (as I did with most of the other form elements). Checkboxes should work, but please let me know if you encounter any that do not.

access comments

You can access docx comments with the comments attribute of the output DocxContent object.

with docx2python('path/to/file.docx') as docx_content:
    print(docx_content.comments)

For each comment, this will return a tuple:

`(reference_text, author, date, comment_text)`

New in docx2python Version 2

merge consecutive runs with identical formatting

MS Word will break up text runs arbitrarily, often in the middle of a word.

<w:r>
    <w:t>work to im</w:t>
</w:r>
<w:r>
    <w:t>prove docx2python</w:t>
</w:r>

This makes things like algorithmic search-and-replace problematic. Docx2python does not currently write docx files, but I often use docx templates with placeholders (e.g., #CATEGORY_NAME#) then replace those placeholders with data. This won't work if your placeholders are broken up (e.g, #CAT, E, GORY_NAME#).

Docx2python v1 merges such runs together when exporting text. Docx2python v2 will merge such runs in the XML as a pre-processing step. This will allow saving such "repaired" XML later on.

merge consecutive links with identical hrefs

MS Word will break up links, giving each link a different rId, even when these rIds point to the same address.

<w:hyperlink r:id="rId13">  # rID13 points to https://github.com/ShayHill/docx2python
    <w:r>
        <w:t>docx2py</w:t>
    </w:r>
</w:hyperlink>
<w:hyperlink r:id="rId14">  # rID14 ALSO points to https://github.com/ShayHill/docx2python
    <w:r>
        <w:t>thon</w:t>
    </w:r>
</w:hyperlink>

This is similar to the broken-up runs, but the cause is a little deeper in. Docx2python v1 makes a mess of these.

<a href="https://github.com/ShayHill/docx2python">docx2py</a>
<a href="https://github.com/ShayHill/docx2python">thon</a>

Docx2python v2 will merge such links together in the XML as a pre-processing step. As above, this will allow saving such "repaired" XML later on.

correctly handle nested paragraphs

MS Word will nest paragraphs

<w:p>
    <w:r>
        <w:t>text</w:t>
    </w:r>
    <w:p>  # paragraph inside a paragraph
        <w:r>
            <w:t>text</w:t>
        </w:r>
    </w:p>
    <w:r>
        <w:t>text</w:t>
    </w:r>
</w:p>

I haven't been able to create such a paragraph, but I've found a few files that have them. Docx2pyhon v1 will omit closing html tags when a new paragraph is opened before the old paragraph is closed.

<b>outer par bold text

<i>This text is in nested par (not bold)</i>

outer par bold text</b>

Docx2python v2 will correctly handle such cases, but this will require substantial internal changes to the way docx2python opens and closes paragraphs.

<b>outer par bold text</b>

<i>This text is in nested par (not bold)</i>

</b>outer par bold text</b>

paragraph styles

The internal changes allow for easy access to paragraph styles (e.g., Heading 1). Docx2python v1 ignores these, even with html=True. Docx2python v2 will capture paragraph styles.

<h1>h1 is a paragraph style<b>bold is a run style</b></h1>

export xml

To allow above-described light editing (e.g., search and replace), docx2python v2 will give the user access to

1. extracted xml files
2. the functions used to write these files to a docx

The user can only go so far with this. A docx file is built from folders full of xml files. None of these xml files are self contained. But search and replace is enough to make document templates (documents with placeholders for data), and that's pretty useful in itself.

expose some intermediate functionality

Navigating through XML is straightforward with lxml. It is a separate step to take whatever you find and bring it out of the XML. For instance, you may want to iterate over a document, looking for paragraphs with a particular format, then pull the text out of those paragraphs. Docx2python v1 did not separate or expose "iter the document" and "pull the content". Docx2python v2 separates and exposes these steps. This will allow easier extension.

See the docx_reader.py module and simple examples in the utilities.py module.

ShayHill / docx2python

readme