From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Christian Moe <mail@christianmoe.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: Attributes on HTML tables?
Date: Thu, 11 Apr 2013 12:55:10 +0200 [thread overview]
Message-ID: <87hajds5f5.fsf@gmail.com> (raw)
In-Reply-To: <m28v4pwjxa.fsf@christianmoe.com> (Christian Moe's message of "Thu, 11 Apr 2013 10:28:17 +0200")
Hello,
Christian Moe <mail@christianmoe.com> writes:
> Nicolas Goaziou writes:
>> Caveat: `org-html-table-tag' is now named
>> `org-html-table-default-attributes' and expect a plist as its value.
>> Also, a nil value will remove the property from the attributes.
>>
>> Could you test it and confirm this is now behaving in a desirable way?
>
> I've run some tests and confirm it works as I'd like it to. Thanks, I
> really like this and I hope others like the plist syntax as well.
Great. Thank you again.
> Late thought, sorry: If we can have this plist syntax as a general rule,
> perhaps we should nevertheless keep the :options tag just as a fallback,
> to ease the transition for users with a lot of legacy attr_html lines?
> It's easier and less catastrophe-prone to do a quick search/replace from
>
> : ^#\+attr_html:
>
> to
>
> : #+attr_html: :options
>
> than it is to automatically replace verbatim attribute code with plists,
> especially if there are all sorts of html irregularities in there.
I prefer not to mix the two methods as it would be fragile (e.g. what
happens if an attribute is defined both outside and inside the :options
keyword?).
> PS. Though if everything is nice and conforming to xhtml, one should be
> able to batch convert files from verbatim html attributes to plist syntax with
> something like the following -- USE AT OWN RISK, NO WARRANTY IMPLIED:
>
> : perl -i.bak -pe 's/([a-z]+)=([\"\'])(.*?)\2/:\1 \2/g if /^#\+attr_html/i' *.org
Would you mind adding it to Worg section about the migration to
Org 8.0? It would be quite useful.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-04-11 10:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 2:55 Attributes on HTML tables? François Pinard
2013-04-07 6:27 ` Bastien
2013-04-07 14:42 ` Christian Moe
2013-04-07 18:46 ` Nicolas Goaziou
2013-04-07 20:39 ` Christian Moe
2013-04-07 20:48 ` Nicolas Goaziou
2013-04-08 21:09 ` Christian Moe
2013-04-10 17:44 ` François Pinard
2013-04-12 2:06 ` Eric Abrahamsen
2013-04-12 5:42 ` Bastien
2013-04-12 6:01 ` Eric Abrahamsen
2013-04-12 8:46 ` Bastien
2013-04-12 14:36 ` François Pinard
2013-04-13 3:38 ` Eric Abrahamsen
2013-04-13 5:31 ` Eric Abrahamsen
2013-04-13 20:42 ` Rick Frankel
2013-04-14 10:13 ` Eric Abrahamsen
2013-04-14 18:01 ` Rick Frankel
2013-04-15 18:03 ` Rick Frankel
2013-04-13 17:10 ` Rick Frankel
2013-04-14 8:41 ` Bastien
2013-04-10 19:37 ` Nicolas Goaziou
2013-04-11 8:28 ` Christian Moe
2013-04-11 10:55 ` Nicolas Goaziou [this message]
2013-04-11 12:14 ` Christian Moe
2013-04-11 15:34 ` Bastien
2013-04-11 17:29 ` Nicolas Goaziou
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=87hajds5f5.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.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).