ODT Document Inspector & Extractor
ODT Document Inspector & Extractor: Unzips ODT archive, parses `content.xml` `<text:p>` paragraph nodes, and extracts embedded `Pictures/` files.
About this odt document inspector & extractor
ODT Document Inspector & Extractor — browser-based utility.
How this tool works
Implements client-side ODT Document Inspector & Extractor operations. Unzips ODT archive, parses `content.xml` `<text:p>` paragraph nodes, and extracts embedded `Pictures/` files specifically designed for a linux libreoffice user inspects text and embedded images in an opendocument text (.odt) file.
- Container Unpacking & XML Navigation: Unpacks the EPUB/iCalendar file stream, parsing root XML structures and calendar VEVENT blocks.
- Metadata & Spine Extraction: Extracts Dublin Core book metadata, manifest items, and spine reading order, or parses recurrence rules (RRULE).
- Content Transformation: Strips HTML formatting from XHTML book chapters to produce clean Markdown, or maps vCard contact fields to QR codes.
- Diagnostic Reporting: Reports broken manifest links, missing spine references, and calendar timezone offsets.
Worked example
Scenario: A Linux LibreOffice user inspects text and embedded images in an OpenDocument Text (.odt) file.
Sample input:
Processing: Unzips ODT archive, parses `content.xml` `<text:p>` paragraph nodes, and extracts embedded `Pictures/` files.
Illustrative output:
Limits and verification
DRM-encrypted EPUB books (protected by Adobe Adept or FairPlay) must have encryption removed before inspecting contents. iCalendar parser supports standard recurrence rules (RRULE); complex EXDATE exclusions are noted.
Examples demonstrate an expected workflow; they do not prove every input or every branch of an external specification. Check important results with an independent source before using them for money, security, compliance, safety, or irreversible file changes.
Browser processing boundary
Tool input is processed by code running in the browser and is not intentionally sent to a CZOA processing API. The page can still request ordinary site assets, analytics, or advertising when those services are enabled. Browser extensions and managed-device software remain outside this tool's control.
Relevant references
These references govern or help explain the format, protocol, or calculation used here. Listing a reference does not claim certification or complete implementation of every optional feature.
Content owner: CZOA Tools · Last reviewed: 2026-09-15 · Review methodology
How to use it
- Enter, paste, or select your input data into the ODT Document Inspector & Extractor workspace controls.
- Review available parameter fields, units, formats, or options configured for your task.
- Click the action button or observe immediate live calculations rendered in your browser runtime.
- Inspect the resulting output and any diagnostic messages, then copy or download the result if needed.
Frequently asked questions
How does ODT Inspector inspect an archive?+
It unzips the selected archive, counts all entry names, decodes content.xml as text or an empty byte array when missing, returns the decoded JavaScript string length as contentBytes, and counts literal <table:table followed by whitespace or >.
Which controls and output are available?+
The page offers one local file chooser and Process locally. Its JSON contains files, contentBytes, tables, and a note. It has no text extraction, word or paragraph count, image export, style or metadata viewer, XML tree, namespace choice, encryption, repair, or validation control.
What interpretation limits apply?+
contentBytes is the decoded character-string length, not package or XML byte length. Table counting is a regular-expression match, not XML parsing; it does not inspect document text, formulas, styles, pictures, metadata, namespaces, content validity, XML escapes, encryption, or corrupted-package recovery.
What did isolated browser verification establish?+
A local browser run inspected an independently authored ZIP with three entries and content.xml containing two table:table start tags. It returned files 3, the independently computed decoded string length, and tables 2; recorded requests had no fixture payload.