Hello,
Jambunathan K writes:
> In the context of the example below (i.e., the way #+ATTR_ODT are used
> /within/ the list) is it fair to say this:
>
> A #+ATTR_ODT: can be attached only to a plain-list - Visually they
> come before the first item of the top-level list or a nested list.
>
Nicolas
In the context of the example below (i.e., the way #+ATTR_ODT are used
/within/ the list) is it fair to say this:
A #+ATTR_ODT: can be attached only to a plain-list - Visually they
come before the first item of the top-level list or a nested list.
Using an #+ATTR_ODT line be
Tim writes:
> At Mon, 26 Aug 2013 12:16:53 +0200,
> Nicolas Goaziou wrote:
>> > Is there any way to have carriage returns within the text of the
>> > macro ?
>>
>> No, there isn't. Macros target small substitutions.
>>
>> > I have already tried using the #+BEGIN_ODT...#+END_ODT construct, but t
Hello,
Tim writes:
> If I put several lines into an #+BEGIN_ODT..#+END_ODT block, all whitespace
> formating is lost. A list like
>
> - List one
> - List two
> - List three
>
> becomes
>
> - List one - List two - List three
I don't quite understand. You are expected to put valid odt code wit
At Mon, 26 Aug 2013 12:16:53 +0200,
Nicolas Goaziou wrote:
> > Is there any way to have carriage returns within the text of the
> > macro ?
>
> No, there isn't. Macros target small substitutions.
>
> > I have already tried using the #+BEGIN_ODT...#+END_ODT construct, but that
> > *really* messes
Hello,
Timothy Aldrich writes:
> I have a simple macro defined to simplify the inclusion of a style for
> odt-export. It looks like this:
>
> #+MACRO: HEADING #+ODT:$1
>
> and then to add this style to any text within the document, I simply call it
> like this:
>
> {{{HEADING( A really great h
