Nicolas Goaziou <n.goaz...@gmail.com> wrote:
> Hello,
>
> Nick Dokos <nicholas.do...@hp.com> writes:
>
> > Yes, you can indeed - except for the [-] which is hardcoded. Try the
> > following:
> >
> > #LATEX_HEADER: \setbox0=\hbox{\large$\square$}
> >
> > #+BIND: org-export-latex-list-parameters (:cbon
> > "[{\\parbox[][][c]{\\wd0}{\\large$\\boxtimes$}}]" :cboff
> > "[{\\parbox[][][c]{\\wd0}{\\large$\\square$}}]")
> >
> > * DONE Organize party [3/4]
> > - [ ] call people
> > - [X] order food
> > - [-] think about what music to play
> > - [X] talk to the neighbors
> >
> > So the question is: why is the [-] hardcoded?
>
> Historical reasons, I guess.
>
> I've now pushed a patch introducing the new property `:cbtrans' for
> those check-boxes.
As expected :-) Thanks.
> Sadly, it will only work with exporters making use of
> list parsing, that is only the LaTeX exporter so far.
>
> Btw, is there any consensus on better default values for :cbon, :cboff
> and :cbtrans? Configurability isn't an excuse for ugly standards.
>
I don't think so - not yet in any case. I didn't even know about the
box stuff until Skip brought it up. I would have thought that the
default ones should be the simplest thing possible: [ ], [X] and [-]
in a monospaced font, something that does not need any help from
additional LaTeX packages, the kind of thing that org-list-to-latex
does.
Nick
