From: Guillaume MULLER <guillaume.muller@univ-st-etienne.fr>
To: emacs-orgmode@gnu.org
Subject: Re: #+include vs. resizing & centrering [SOLUTION]
Date: Wed, 30 Mar 2022 11:26:38 +0200 [thread overview]
Message-ID: <74e3985e-3236-e54e-66e1-7749cbd05929@univ-st-etienne.fr> (raw)
In-Reply-To: <95330d48-9234-7259-db34-25eac3d99840@univ-st-etienne.fr>
[-- Attachment #1.1: Type: text/plain, Size: 1827 bytes --]
Sorry, I finally found a solution by myself :)
Using a minipage instead of a scalebox tolerates the \begin{center} that is automatically inserted:
#+LATEX: \center \begin{minipage}[c]{.85\textwidth}
#+INCLUDE: ./test.dot src dot :file test.png
#+LATEX: \end{minipage}
However, if someone has a pure/clean org-mode solution, I would love to learn it :)
On 3/30/22 11:07, Guillaume MULLER wrote:
> Dear all,
>
> Thanks for org-mode, it is so perfect :)
>
> I'm currently fighting with a problem that I cannot find a solution to (either on my own or with help on the web). If someone could help me, I would be very thankful.
>
> I have an org-mode file that "includes" ane xternally generated image, like so:
>
> #+INCLUDE: ./test.dot src dot :file test.png
>
> The thing is the resulting image is too big. So I want to resize it.
>
> I've tried several things that did not work:
> - add #+ATTR_LATEX: :width xxx before the #+INCLUDE
> - add :width xxx or :scale xxx on the #+INCLUDE line itself
> - ...
>
> Thus I resolved to use plain LaTeX code with something like:
> #+LATEX: \center \scalebox{.85}{%
> #+INCLUDE: ./test.dot src dot :file test.png
> #+LATEX: }
>
> Then the problem is that #+INCLUDE adds a \begin{center}\end{center} around the image inclusion, and \scalebox{} does not like that, making the resulting .tex file not compile ("perhaps missing \item").
>
> Again, I've tried several unsuccessful things :
> - add #+ATTR_LATEX: :center nil before the #+INCLUDE
> - add :center nil on the #+INCLUDE line itself
> - ...
>
> If anyone has an idea how a can solve the problem of resizing a #+INCLUDE'd image, either in plain org or with a LaTeX "warkaround", I would be very grateful.
>
> Thanks !
>
> Guillaume MULLER, PhD
--
Guillaume MULLER, PhD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2022-03-30 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 9:07 #+include vs. resizing & centrering Guillaume MULLER
2022-03-30 9:26 ` Guillaume MULLER [this message]
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=74e3985e-3236-e54e-66e1-7749cbd05929@univ-st-etienne.fr \
--to=guillaume.muller@univ-st-etienne.fr \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).