emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: #+ATTR_LaTeX no longer honoured
Date: Mon, 20 May 2013 10:05:33 +0800	[thread overview]
Message-ID: <87r4h276du.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87a9nq4spq.fsf@gmail.com

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Paul Stansell <paulstansell@gmail.com> writes:
>>
>>> Hello,
>>>
>>> I've noticed that #+ATTR_LaTeX seems to be no longer honoured (I'm
>>> using release_8.0.3-133-ga5872)
>>>
>>> This is demonstrated for the attached org file.  It's the exact
>>> example from http://orgmode.org/manual/Images-in-LaTeX-export.html.
>>>
>>> I expect the exported latex file (C-c C-e l l) to contain something like
>>>
>>>   \includegraphics[width=5cm,angle=90]{./dummy.png}
>>>
>>> but I instead it contains
>>>
>>>   \includegraphics[width=.9\linewidth]{./dummy.png}
>>>
>>> Thanks,
>>>
>>> Paul
>>>
>>> PS. I'm using Emacs 24.2.1 and I tested with the minimal org-mode
>>> set-up from http://orgmode.org/manual/Feedback.html.
>>
>> I won't even attempt to give an overview of how attribute syntax has
>> changed/is changing, or explain why and how the manual is out of date,
>> but while we're waiting for someone else to do that, here's the line
>> you're looking for:
>>
>> #+ATTR_LaTeX: :width 5cm :options angle=90
>
> The manual is up-to-date (sections about HTML and ODT export may lag
> a bit behind), but the URL isn't. In particular, see:
>
>   http://orgmode.org/org.html#LaTeX-specific-attributes
>
>> Very briefly, I think attributes that may be common to multiple backends
>> are now given as eg :width or :height (with no equals sign before the
>> value), while attributes that are rarer or likely backend-specific are
>> stuffed into one :options attribute, with the keys/values written more
>> literally.
>
> AFAIK, :options is specific to latex back-end. Common attributes are set
> the usual way, i.e. with ":attribute value" syntax. Though it's
> impossible to recognize them all. So :options is handy to add raw
> arguments.
>
> Anyway, all attributes should be documented in the manual.

Sure enough, I should have just stopped with the working example!

  reply	other threads:[~2013-05-20  2:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-19 11:18 #+ATTR_LaTeX no longer honoured Paul Stansell
2013-05-19 13:27 ` Eric Abrahamsen
2013-05-19 20:31   ` Nicolas Goaziou
2013-05-20  2:05     ` Eric Abrahamsen [this message]
2013-05-20 18:05     ` Daniel F
2013-05-23 19:42   ` Paul Stansell
2013-05-24  0:15     ` Rasmus

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=87r4h276du.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).