PPT: Legacy PowerPoint 97
A pitch-deck slide set saved as legacy binary .ppt (PowerPoint 97-2003, OLE compound file) via LibreOffice. For testing legacy-Office parsers and PPT→PPTX conversion.
Rendered preview of the ppt file (643 KB). Download above for the original.
Specifications
- Format
- MS PowerPoint 97-2003 (.ppt)
- Source
- pitch-deck.pptx
- Converter
- LibreOffice
Testing contract
Expected to pass- Scenario
- Exercise PPT: Legacy PowerPoint 97 in its presentation workflow. A pitch-deck slide set saved as legacy binary .ppt (PowerPoint 97-2003, OLE compound file) via LibreOffice.
- Expected result
- 7 OLE compound streams; CompObj: 57 bytes; Ole: 20 bytes; Current User: 44 bytes; Pictures: 0 bytes; PowerPoint Document: 58662 bytes; SummaryInformation: 590164 bytes; DocumentSummaryInformation: 392 bytes. Declared feature checks: source=pitch-deck.pptx; converter=LibreOffice.
What is a .ppt file?
A .ppt file is the legacy binary Microsoft PowerPoint format (97–2003) built on the OLE2 compound-file structure, distinct from the modern .pptx. Legacy decks and templates still use it.
How to use this file
Use an example .ppt file to test legacy PowerPoint parsers (LibreOffice), OLE2 handling, and PPT-to-PPTX conversion.
How to use this file for testing
“PPT: Legacy PowerPoint 97” is a deterministic Testaroo fixture for Conversion testing. The same content exported across many formats and linked as a group, so you can convert one and diff against the expected twin.
Documented properties for this file: MS PowerPoint 97-2003 (.ppt). Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.
Document fixtures list their internal structure (pages, fields, tracked changes, embedded objects) in the spec table. Test extractors, converters, and OCR against that known structure, and compare searchable↔scanned or format-twin companions when present.
Code examples
soffice --headless --convert-to pptx legacy.pptGenerated by generation/docs_legacy.py. Free for any use, no attribution required, license.
Related files
- odpODP: OpenDocument PresentationA three-slide OpenDocument Presentation with titles and body text, for testing ODP readers and slide converters. Original content, free to use.
- pptxPPTX with Speaker NotesA four-slide presentation where every slide carries speaker notes in the notes pane, for testing notes extraction and whether converters preserve the notes alongside the slides.
- ediAlder Table Bistro: ANSI X12 810 invoiceANSI X12 810 invoice for Alder Table Bistro. Version 004010 transaction set 810 for invoice INV-BST-5002, control number 810002. 3 IT1 segments, a TXI segment stating GST of 15.69, and a TDS segment of 32953 in implied-decimal cents, which is 329.53 CAD. SE declares 13 segments and 13 are present.
- ediAlder Table Bistro: ANSI X12 810 invoice with a wrong SE segment countANSI X12 810 invoice with a wrong SE segment count for Alder Table Bistro. Identical to edi-810-invoice.edi except for one element: SE declares 11 segments where 13 are present between ST and SE inclusive. The ISA, GS, GE and IEA control numbers, every data segment and the TDS total of 32953 are unchanged, so a parser that checks only syntax accepts the file and only a parser that recounts segments rejects it.
- ediAlder Table Bistro: ANSI X12 850 purchase orderANSI X12 850 purchase order for Alder Table Bistro. Version 004010 transaction set 850 for PO-BST-1002, control number 850002. 3 PO1 segments carry quantity, X12 unit code, unit price, the supplier item code (VP) and the buyer item code (BP); CTT declares 3 line items and SE declares 14 segments, which is the number actually present between ST and SE inclusive.
- ediAlder Table Bistro: ANSI X12 856 despatch adviceANSI X12 856 despatch advice for Alder Table Bistro. Version 004010 transaction set 856 for supplier delivery note DN-BST-3002 against PO-BST-1002, control number 856002. The shipment, order and item hierarchy uses HL segments, and the SN1 quantities are the quantities actually delivered, so line 2 reports 16 where the 850 ordered 20.
