emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: John Hendy <jw.hendy@gmail.com>, "Thomas S. Dye" <tsd@tsdye.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Confusion about attr_latex and new exporter
Date: Tue, 19 Mar 2013 09:49:17 -0500	[thread overview]
Message-ID: <CA+M2ft91-bnwJ=FRny3NGU63up87ngp1sJNm8y6UT4pZTBHWGg@mail.gmail.com> (raw)
In-Reply-To: <87ehfcvuyq.fsf@gmail.com>

On Tue, Mar 19, 2013 at 12:07 AM, Aaron Ecay <aaronecay@gmail.com> wrote:
> Hi again,
>
> 2013ko martxoak 19an, Aaron Ecay-ek idatzi zuen:
>> I’m sorry, that was a mistake.  I sent a patch to the HTML backend to
>> enable this behavior, but forgot all about it.  Then when I checked the
>> code, it looked like the functionality was already there!  I’ll follow
>> up with Bastien about the patch, and see what its status is...
>
> I was very confused when I wrote this.  The patches I had in mind were
> for a different issue.  If
> #+ATTR_HTML: :width 200
> ever worked for me, it was only because of me hacking org into a
> chimeric state.  I guess you should continue to use
> #+ATTR_HTML: width=200
> or whatever the working incantation for HTML has traditionally been.
>

Thanks for the clarification, though regardless of the current
state... what is the consensus on what it *should* be? The old lingo
was:
- #+attr_latex: width=Xcm
- #+attr_html: width="Xpx"

That made sense to me since that's how they appear in
\blah[width=Xcm]{file.png} or <img src="" width="Xpx" />.

With the move to :width value, I guess I'd rather see them work the
same or have it be obviously backend-specific vs. having :width Xcm
for LaTeX, and width=200 for html. At least make it identical to the
actual backend syntax (quotes around the 200 for html) or in pure
babel-esque language to unify (:width value, no quotes) for all.

At least that's my thought from a user's perspective.


Thanks!
John


> Sorry for the noise,
>
> --
> Aaron Ecay

  reply	other threads:[~2013-03-19 14:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-17 21:57 Confusion about attr_latex and new exporter John Hendy
2013-03-17 22:09 ` John Hendy
2013-03-17 22:22 ` Thomas S. Dye
2013-03-18  0:28   ` John Hendy
2013-03-18  0:38     ` Thomas S. Dye
2013-03-19  4:51     ` Aaron Ecay
2013-03-19  5:07       ` Aaron Ecay
2013-03-19 14:49         ` John Hendy [this message]
2013-03-19 18:49           ` Bastien
2013-03-20 17:17             ` John Hendy
2013-03-19 17:52 ` Bastien

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='CA+M2ft91-bnwJ=FRny3NGU63up87ngp1sJNm8y6UT4pZTBHWGg@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.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 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).