docs(templating): explain which image formats a deliverable can carry - #147
Merged
yacinekahlerras-turbodocx merged 1 commit intoAug 14, 2026
Merged
Conversation
Only PNG and JPEG can be stored inside a generated document or presentation. Any
other format is replaced in the output with a short message naming the format, the
file, and what to use instead:
[Image not supported: SVG — use PNG or JPEG (diagram.svg)]
That message was undocumented, so someone who met it had nothing to search for.
Adds a troubleshooting section covering the supported formats, the message, and how
to fix it — plus the part that actually confuses people: the rich text editor
previews SVG, GIF and WebP perfectly well, because a browser can display formats a
Word or PowerPoint file cannot store. An image can therefore look correct while
editing and still be replaced in the finished deliverable.
Also adds it to the Quick Troubleshooting Steps and to the page keywords, so the
message is findable by searching the text it prints.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
yacinekahlerras-turbodocx
marked this pull request as ready for review
August 14, 2026 14:57
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Only PNG and JPEG can be stored inside a generated document or presentation. Any other
format is replaced in the output with a short message:
That message was documented nowhere, so someone who met it in a deliverable had nothing to
search for.
What this adds
A new troubleshooting section, "Images Must Be PNG or JPEG", covering:
perfectly well, because a browser can display formats a Word or PowerPoint file cannot store.
An image can look correct while you're editing and still be replaced in the finished
deliverable. Called out in a
:::cautionso it isn't missed.Also adds it to Quick Troubleshooting Steps and to the page keywords, so searching the
text the product prints actually lands here.
Why the troubleshooting page
"Why did my image turn into text?" is a troubleshooting question, and the page already collects
the other "your variable looks fine but isn't" traps — naming rules, own-line placement,
paragraph markers. This is the same shape of problem, so it belongs beside them rather than in a
new page nobody would find.
Notes
developper the repo's branching rule.