emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Rescaling #+INCLUDES / Not centering #+INCLUDE?
Date: Sat, 10 Sep 2022 18:22:37 +0700	[thread overview]
Message-ID: <tfhs1u$v75$1@ciao.gmane.io> (raw)
In-Reply-To: <87bkrny5hn.fsf@localhost>

On 10/09/2022 15:54, Ihor Radchenko wrote:
> Guillaume MULLER writes:
> 
>> My (unsuccessful) approaches so far to find a solution:
>> 1. remove the automatic \begin{center} inserted by #+INCLUDE
>>     => using :center nil in #+INCLUDE or in additional #+ATTR_LATEX added above #+INCLUDE does not work
>> 2. remove the use of \scalebox by using a more "org-mode"'s way of doing things
>>     => using :width in #+INCLUDE or in additional #+ATTR_LATEX or even passing options to dot have no effect (see previously attached file)
> 
> It is kind of late, but I think that the problem is not with Org. Rather
> with LaTeX. Org uses \begin{center}..\end{center} around the image,
> which cannot be used inside \scalebox. See
> https://tex.stackexchange.com/questions/67843/problem-resizing-an-itemize-environment-with-a-scalebox-somethings-wrong

I have not tried to reproduce the issue, but provided latex snippet is 
quite strange. Accordingly to ORG-NEWS, \scalebox was added in 9.3 for 
tikz and pdf, while \includegraphics appeared in the example. In this 
case scale should be applied through \includegraphics option.

Anyway I expect \begin{center} around \scalebox, not inside it.

Finally it should be possible to pass :center nil through ob-dot to the 
generated image.



      reply	other threads:[~2022-09-10 11:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 14:18 Rescaling #+INCLUDES / Not centering #+INCLUDE? Guillaume MULLER
2021-10-05 15:06 ` Eric S Fraga
2021-10-06 15:30   ` Guillaume MULLER
2021-10-07  7:24     ` Eric S Fraga
2022-09-10  8:54     ` Ihor Radchenko
2022-09-10 11:22       ` Max Nikulin [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='tfhs1u$v75$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --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).