From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Sebastien Vauban
<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: Align argument in #+attr_latex for tabular env. is whitespace sensitive
Date: Fri, 15 Feb 2013 20:44:03 +0100 [thread overview]
Message-ID: <877gm98irg.fsf@gmail.com> (raw)
In-Reply-To: <86bobll88j.fsf@somewhere.org> (Sebastien Vauban's message of "Fri, 15 Feb 2013 19:53:00 +0100")
Hello,
"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
> For my information (and not only for me, I guess), is there a fundamental
> reason (I guess yes) why width is a first-class parameter for tables and an
> option among others for images?
>
> Looking from a 50 ft perspective, I would even imagine the opposite: images
> will have to be scales in almost all cases (that is: have their image
> attribute set), while tables will often take the space they need to.
>
> Is there a reason why images can't have their own attributes as well? I would
> find that much, much more easy to apply, if we don't have to write the same
> "functional" request in two different manners, depending on the
> context.
It's LaTeX's fault!
In tables, width is an argument between curly brackets. In other words,
it has a specific location among the command arguments. On the other
hand, in images, width is just an option between square brackets. And
the same brackets can contain other options.
So, the easiest implementation was to follow LaTeX's conventions. An
argument within curly brackets gets its own keyword. Optional arguments
are stuffed within an `:options' keyword.
With care[fn:1], "width" option could be extracted from `:options'
keyword and get its own `:width' keyword. Do you want to give it a try?
Regards,
[fn:1] By deciding what to do when width is specified in both :options
and :width keyword, for example.
--
Nicolas Goaziou
prev parent reply other threads:[~2013-02-15 19:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 17:30 Align argument in #+attr_latex for tabular env. is whitespace sensitive John Hendy
2013-02-12 19:22 ` Nicolas Goaziou
2013-02-12 19:40 ` John Hendy
2013-02-12 19:44 ` Nicolas Goaziou
2013-02-12 19:51 ` John Hendy
2013-02-15 10:05 ` Sebastien Vauban
2013-02-15 13:08 ` Nicolas Goaziou
2013-02-15 18:53 ` Sebastien Vauban
2013-02-15 19:44 ` Nicolas Goaziou [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=877gm98irg.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.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).