From: Aaron Ecay <aaronecay@gmail.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug] new beamer exporter always adds default width to graphics
Date: Tue, 12 Mar 2013 22:55:34 -0400 [thread overview]
Message-ID: <87txogatzt.fsf@gmail.com> (raw)
In-Reply-To: <20130312221726.GG8127@kuru.dyndns-at-home.com>
Hi Suvayu,
2013ko martxoak 12an, Suvayu Ali <fatkasuvayu+-ek idatzi zuen:
>
> That is understandable, but if the aim is to support other kinds of
> graphics that support :width, I expect the change to not interfere with
> graphics that do not support it. I think there are two cases here:
>
> 1. the author targets the document for a specific backend that does not
> support :width
>
> 2. the author expects to export to multiple backends and wants to be as
> general as possible so uses and expects :width to work.
:width is an ATTR_LATEX keyword, as is :options. So they only apply to
the LaTeX backend – and those which derive from it, such as beamer. If
document authors wish to also export to e.g. HTML, they will have to
make separate arrangements.
>
> So now the question is, is it reasonable to expect the author in case
> (1) is aware of this subtlety and use :width even though her/his backend
> does not support it, or would it be better to handle these deficient
> cases "specially" and help the author by not clobbering their :options
> argument.
Eliminating subtleties is precisely the point of this change. All(-ish)*
backends now use :width.
* As far as I’ve checked, HTML(+ derived backends) and LaTeX(+derived
backends). If there are any that don’t, they should probably be patched
to do so as well.
--
Aaron Ecay
next prev parent reply other threads:[~2013-03-13 2:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 13:25 [bug] new beamer exporter always adds default width to graphics James Harkins
2013-03-12 14:38 ` Jay Kerns
2013-03-12 14:59 ` Suvayu Ali
2013-03-12 18:40 ` Aaron Ecay
2013-03-12 22:17 ` Suvayu Ali
2013-03-13 2:55 ` Aaron Ecay [this message]
2013-03-13 8:30 ` James Harkins
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=87txogatzt.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.