From: Peter Davis <pfd@pfdstudio.com>
To: emacs-orgmode@gnu.org
Subject: Re: Getting checkboxes in HTML output?
Date: Tue, 03 Dec 2013 11:56:50 -0500 [thread overview]
Message-ID: <529E0D52.1070902@pfdstudio.com> (raw)
In-Reply-To: <86wqjmrm8a.fsf@somewhere.org>
On 12/3/13, 10:24 AM, Sebastien Vauban wrote:
> Rick Frankel,
>
> Rick Frankel wrote:
>>> This is sort of close to using
>>> [ ] for unchecked
>>> [/] for partially checked
>>> [X] for checked
>>>
>>> To my aging eyes, the check in U#9745 looks almost like a forward
>>> slash. Certainly, though, this would be potentially confusing,
>>> especially if no [X] boxes were present, so that only [ ] or [/] were
>>> visible.
>> Right. I am going to make this a configurable option in ox-html,
>> although consensus is that trying to emulate the partial checkbox
>> ([-]) w/ other unicode symbols is too confusing, so we will simply use
>> an empty ballot box.
> You mean no difference between unchecked and partially checked? If yes, this
> is wrong IMO.
>
> I did not search for long, but there should be usable unicode characters. To
> name a few:
>
> - U+25EB White square with vertical bisecting line
> - U+25F1 White square with lower left quadrant
I think Rick's proposal of treating partially completed checkboxes as
empty is appropriate. It's kind of the graphical equivalent of the
"floor" function.
The problem is that we really need three symbols which clearly and
unambiguously represent three states of completion: none, partial and
full. Unicode doesn't seem to give us any triplets like that, and trying
to kludge otherwise unrelated symbols is not going to be satisfactory.
That said, one possibility that strikes me would be:
U+25A1 White square
U+25E7 Square with left half black
U+25A0 Black square
The drawback, as I see it, is that if only white squares or only black
squares appear, they would simply look like some kind of stylish bullet
characters.
-pd
--
Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com
next prev parent reply other threads:[~2013-12-03 17:04 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
[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 [this message]
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=529E0D52.1070902@pfdstudio.com \
--to=pfd@pfdstudio.com \
--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).