Latex export colouring and properties

Latex export colouring and properties

[Simon Brown]

Hi all,

Is it possible to colour the output in pdf export in the same way it is 
done in html export? The colouring of tags and timestamps is very 
useful.

Also is it possible to include properties in the output? I'm adding 
effort estimates to the tasks which I'd like to be included in the 
exported pdf.

Thanks,

Simon

Re: Latex export colouring and properties

[Carsten Dominik]

On Apr 22, 2009, at 6:04 PM, Simon Brown wrote:

> Hi all,
>
> Is it possible to colour the output in pdf export in the same way it  
> is
> done in html export? The colouring of tags and timestamps is very
> useful.

I guess this could be implemented, but for me, LaTeX is still mainly
used for B&W text, so it never occurred to me.  I guess we could wrap  
some
kind of macro around it, and you would be responsible to define that  
macro....

>
> Also is it possible to include properties in the output? I'm adding
> effort estimates to the tasks which I'd like to be included in the
> exported pdf.

Directly exporting drawers usually looks bad, so we don't really have  
this.

- Carsten

>
> Thanks,
>
> Simon
>
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Latex export colouring and properties

[Simon Brown]

* Carsten Dominik (carsten.dominik@gmail.com) wrote:
> I guess this could be implemented, but for me, LaTeX is still mainly
> used for B&W text, so it never occurred to me.  I guess we could wrap  
> some
> kind of macro around it, and you would be responsible to define that  
> macro....
I've thought about this some more and although I love colour
everywhere what I'm after is actually quite simple. Firstly on
reflection I agree exporting draws would be bad. 
	   Where I work there are a lot of network restrictions which
means many documents are exchanged in printed form. Highlighting the
todo state red or green as it is within org-mode, makes important
points obvious. Some sort of colouring for the date stamps for scheduled,
deadline and closed would be nice as well

Simon
-- 
Simon Brown

Re: Latex export colouring and properties

[Carsten Dominik]

On May 7, 2009, at 8:17 PM, Simon Brown wrote:

> * Carsten Dominik (carsten.dominik@gmail.com) wrote:
>> I guess this could be implemented, but for me, LaTeX is still mainly
>> used for B&W text, so it never occurred to me.  I guess we could wrap
>> some
>> kind of macro around it, and you would be responsible to define that
>> macro....
> I've thought about this some more and although I love colour
> everywhere what I'm after is actually quite simple. Firstly on
> reflection I agree exporting draws would be bad.
> 	   Where I work there are a lot of network restrictions which
> means many documents are exchanged in printed form. Highlighting the
> todo state red or green as it is within org-mode, makes important
> points obvious. Some sort of colouring for the date stamps for  
> scheduled,
> deadline and closed would be nice as well

Hi,

I am not going to make this happen by default, but you can now  
configure things (with the latest git version:

In the Org file:

#+LATEX_HEADER: \usepackage{color}
#+LATEX_HEADER: \def\todo#1{{\color{red}#1}}
#+LATEX_HEADER: \def\done#1{{\color{green}#1}}



In .emacs

(setq org-export-latex-todo-keyword-markup '("\\todo{%s}" . "\ 
\done{%s}"))


It is also possible to use different colors for each keyword.

See also the variables

  org-export-latex-timestamp-keyword-markup
  org-export-latex-timestamp-markup


HTH

- Carsten

Latex export colouring and properties

[Simon Brown]

Hi all,

Is it possible to colour the output in pdf export in the same way it is 
done in html export? The colouring of tags and timestamps is very 
useful.

Also is it possible to include properties in the output? I'm adding 
effort estimates to the tasks which I'd like to be included in the 
exported pdf.

Thanks,

Simon