From: Thomas Redelberger <redetho-Mmb7MZpHnFY@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: PowerPoint output - SVG image aspect ratio - BOM issue?
Date: Fri, 7 Apr 2023 16:07:46 +0200 [thread overview]
Message-ID: <cf86aee2-1704-0bbf-102c-2be2c02be7c5@gmx.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
Hi,
Regards PowerPoint output:
When linking SVG images, pandoc scales to the available space on a slide, while preserving the aspect ratio.
The aspect ratio seems to change a bit, when the SVG file starts with an UTF-8 BOM (=3 special bytes at the beginning of the file), which IMHO should not happen.
Command line (pandoc 3.1 for Windows):
> pandoc -t pptx -o testbom.pptx testbom.txt
I attach here a testbom.txt markdown input file plus two test SVG files, one with BOM, the other without.
I had started with org-mode input rather than markdown. Same result.
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/cf86aee2-1704-0bbf-102c-2be2c02be7c5%40gmx.de.
[-- Attachment #2: blind_400x300.svg --]
[-- Type: image/svg+xml, Size: 639 bytes --]
[-- Attachment #3: blind_400x300_UTF-8-BOM.svg --]
[-- Type: image/svg+xml, Size: 642 bytes --]
[-- Attachment #4: testbom.txt --]
[-- Type: text/plain, Size: 184 bytes --]
% Test Title
% Test Author
% 2023-04-07
# Test Heading 1
![test image w. BOM](./blind_400x300_UTF-8-BOM.svg)
# Test Heading 2
![test image wo. BOM](./blind_400x300.svg)
next reply other threads:[~2023-04-07 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 14:07 Thomas Redelberger [this message]
[not found] ` <cf86aee2-1704-0bbf-102c-2be2c02be7c5-Mmb7MZpHnFY@public.gmane.org>
2023-04-07 16:03 ` John MacFarlane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cf86aee2-1704-0bbf-102c-2be2c02be7c5@gmx.de \
--to=redetho-mmb7mzphnfy@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).