public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Eelco Vriezekolk <eelco-GsmfYmMHemE@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: ODT with some, but not all, graphics aligned on the right margin
Date: Tue, 7 Feb 2023 08:12:31 -0800 (PST)	[thread overview]
Message-ID: <d6ae917b-a037-4e03-a442-a050fdb7d368n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1211 bytes --]

Hello,

From Markdown I want to create a manual in various formats, including HTML 
and ODT (OpenDocument).
My manual contains images. Most are figures (in their own paragraph), but 
others should appear inside a paragraph, with text flowing around it. For 
HTML this works:

[image: Screenshot 2023-02-07 at 17.07.25.png]

The .float-class is defined in a CSS-stylesheet, and works fine:


However, I cannot get this to work right in the ODT output. I define a 
'float' graphics style in the reference file, but it is not being picked up 
in the ODT-output. No amount of experimenting and searching the web have 
helped so far.
I can get *all* figures to be right-aligned, but that is not what I want. I 
want to be able to indicate that some selected images appear inline.

Can this be done? How?


-- 
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/d6ae917b-a037-4e03-a442-a050fdb7d368n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 55070 bytes --]

[-- Attachment #2: Screenshot 2023-02-07 at 17.07.25.png --]
[-- Type: image/png, Size: 33356 bytes --]

             reply	other threads:[~2023-02-07 16:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 16:12 Eelco Vriezekolk [this message]
     [not found] ` <d6ae917b-a037-4e03-a442-a050fdb7d368n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-07 16:53   ` John MacFarlane
     [not found]     ` <2D74B45D-A8A8-439D-9B60-F7711A1E6139-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-02-07 21:04       ` Eelco Vriezekolk
     [not found]         ` <a556d276-429e-b2db-2e83-7d89d26a74c7-GsmfYmMHemE@public.gmane.org>
2023-02-08 11:10           ` Günter Dannoritzer

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=d6ae917b-a037-4e03-a442-a050fdb7d368n@googlegroups.com \
    --to=eelco-gsmfymmheme@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).