From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Getting checkboxes in HTML output?
Date: Thu, 28 Nov 2013 22:26:53 +0100 [thread overview]
Message-ID: <86haawtdya.fsf@somewhere.org> (raw)
In-Reply-To: 87vbzc9rmj.fsf@Rainer.invalid
Achim Gratz wrote:
> Rick Frankel writes:
>> For xhtml compatibility, it would need to be 'checked="checked"'. I've
>> done a quick look at the html dtd, and i does look like input elements
>> are allowed outside of forms, but i would need to double
>> check... Also, the fallback to "[-]" for the partially checked state
>> is a bit inconsistent, perhaps changing background color or other
>> attributre of the checkbox would be better.
>
> I'd much prefer if you'd be using character entities for that since you
> can't do any input on the HTML anyway (WHITE MEDIUM SQUARE, SQUARE WITH
> LOWER RIGHT DIAGONAL BLACK and BLACK MEDIUM SQUARE look like good
> candidates). That probably makes it UTF-8 only since I don't think
> these symbols are defined for plain (X)HTML, so for other encodings
> things should probably stay as they are.
FWIW, here's what I do for the HTML export:
In JS:
#+begin_src js
$(function () {
$('li > code:contains("[X]")')
.parent()
.addClass('checked')
.end()
.remove();
$('li > code:contains("[-]")')
.parent()
.addClass('halfchecked')
.end()
.remove();
$('li > code:contains("[ ]")')
.parent()
.addClass('unchecked')
.end()
.remove();
});
#+end_src
In CSS:
#+begin_src css
li.checked {
list-style-image: url('../images/checked.png');
}
li.halfchecked {
list-style-image: url('../images/halfchecked.png');
}
li.unchecked {
list-style-image: url('../images/unchecked.png');
}
#+end_src
with 3 nice pictures of green V, red X, and blue || (line "pause" on
recorders).
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-11-28 21:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 15:45 Getting checkboxes in HTML output? Peter Davis
2013-11-27 16:03 ` Nick Dokos
2013-11-27 18:20 ` Peter Davis
2013-11-28 13:33 ` Rick Frankel
2013-11-28 13:55 ` Peter Davis
2013-11-28 16:08 ` Bastien
2013-11-28 17:03 ` Matt Price
2013-11-28 20:51 ` Achim Gratz
2013-11-28 21:26 ` Sebastien Vauban [this message]
[not found] ` <CAN_Dec9a5v2rqQSvAKpvgLWKsTY8YLoMSvKbtkgak77Bb=nbAg@mail.gmail.com>
2013-11-28 21:58 ` Matt Price
2013-11-29 16:11 ` Rick Frankel
2013-11-29 18:59 ` Peter Davis
2013-11-30 6:54 ` Carsten Dominik
2013-11-30 14:07 ` Rick Frankel
2013-12-01 6:46 ` Carsten Dominik
2013-12-02 8:44 ` Sebastien Vauban
2013-12-02 16:38 ` Peter Davis
2013-12-03 1:11 ` Nick Dokos
2013-12-03 12:29 ` Peter Davis
2013-12-03 15:03 ` Rick Frankel
2013-12-03 15:24 ` Sebastien Vauban
2013-12-03 16:56 ` Peter Davis
2013-12-03 15:14 ` Rick Frankel
2013-11-29 1:47 ` Eric Abrahamsen
2013-11-28 14:30 ` Waldemar Quevedo
2013-11-28 14:41 ` Waldemar Quevedo
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=86haawtdya.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.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).