Re: Can't use char ">" in TODO state

["Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>]

Hi Nicolas and Bastien,

> Nicolas Goaziou wrote:
>> Bastien <bzg-whniv8GeeGkdnm+yROfE0A@public.gmane.org> writes:
>>> Michael Brand <michael.ch.brand-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>>
>>>> It works with this patch
>>>> http://patchwork.newartisans.com/patch/964
>>>> from Nicolas which I am still using to test it.
>>
>>> If so, then Nicolas please apply it.  It really simplifies
>>> the way headlines are matched in many places in the code.
>>
>> I've applied it.
>
> This works as expected from my point of view. Thanks a lot...

... with this exception (when using TODO states from Dan Davison):

#+OPTIONS:   ^:nil
#+SEQ_TODO: DOESN'T_WORK DOESN'T-WORK | WORKS

* WORKS Marche

In HTML, class is "WORKS" and word in the heading is "WORKS" as well.

* DOESN'T_WORK Marche pas

The HTML class is "DOESN'T_WORK" (the real name of the state) and
"DOESN_T_WORK" in the heading.

In LaTeX, the status "DOESN'T_WORK" is kept as-is in the heading, hence
provoking a layout bug in the PDF.

This is true, whatever the value of the option ^ for interpreting sub- and
super-scripts: setting it to =t= or to =nil= makes no difference.

* DOESN'T-WORK Marche pas

In this last case, the real name "DOESN'T-WORK" is conserved as HTML class,
but translated to "DOESN_T_WORK" in the heading.

No problem in LaTeX.

Best regards,
  Seb

-- 
Sebastien Vauban