Skip to content

Fix PPTX OCR converter emitting literal backslash-n instead of newlines - #2405

Closed
SpongeBob (As9xm) wants to merge 1 commit into
microsoft:mainfrom
As9xm:fix-pptx-ocr-newlines
Closed

SpongeBob (As9xm) wants to merge 1 commit into
microsoft:mainfrom
As9xm:fix-pptx-ocr-newlines

Conversation

@As9xm

Copy link
Copy Markdown
Contributor

_pptx_converter_with_ocr.py used escaped \\n literals in slide headers, text frames, notes, tables, and charts, so output contained literal \n text instead of line breaks.
This change replaces all 10 occurrences with real \n newlines to restore correct markdown formatting.

@As9xm

Copy link
Copy Markdown
Contributor Author

@microsoft-github-policy-service agree

@afourney

Copy link
Copy Markdown
Member

Thank you for identifying and fixing the literal backslash-n output paths.

#2506, included in v0.1.8, replaced the duplicated PPTX OCR formatting code with the core presentation pipeline. The affected slide, notes, table, and chart formatting now comes from that implementation, superseding these replacements.

Closing this PR with thanks. Please use markitdown==0.1.8 with markitdown-ocr==0.1.1. Please reopen this PR if it still addresses a case that the current implementation misses, with a reproduction or a description of the remaining difference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants