Export HTML with Free Form Text

Export HTML with Free Form Text

[Esben Stien]

If I have a heading like this: 

** foo
bar

baz

..the export is fine, because the extra empty space between the lines
makes the export function treat them as two paragraphs, but if I have a
heading like this: 

** foo
bar
baz

..and I export it to html, it comes out like this:

** foo
bar baz

Is there any way to tell export that free form text like this is
allowed?

Many times I use a heading just to separate blocks of random text and
notes and I don't think I should have to tell it explicitly that this
text is free form.

-- 
Esben Stien is b0ef@e     s      a             
         http://www. s     t    n m
          irc://irc.  b  -  i  .   e/%23contact
           sip:b0ef@   e     e 
           jid:b0ef@    n     n

Re: Export HTML with Free Form Text

[Rick Frankel]

On 2014-05-13 11:03, Esben Stien wrote:
> If I have a heading like this:
> ** foo
> bar
> baz
> 
> ..and I export it to html, it comes out like this:
> 
> ** foo
> bar baz
> 
> Is there any way to tell export that free form text like this is
> allowed?

What you want is verbatim text, or "Literal examples", not really
free-form. HTML by definition treats runs of whitespace as a single
space, so you need to do something to get it to treat the text as
separate lines. You have (at least ;) two choices in org: example
blocks or verse block.

Here's an example:

---- 8< cut here 8< -----

* Literal text

#+BEGIN_VERSE
this
is
a
verse
#+END_VERSE

#+BEGIN_EXAMPLE
this
is
a
verse
#+END_EXAMPLE

And the html output:

#+BEGIN_HTML
<p class="verse">
this<br  />
&#xa0;&#xa0;is<br  />
&#xa0;&#xa0;&#xa0;&#xa0;a<br  />
verse<br  />
</p>

<pre class="example">
this
is
a
verse
</pre>
#+END_HTML

Re: Export HTML with Free Form Text

[Esben Stien]

Rick Frankel <rick@rickster.com> writes:

> You have (at least ;) two choices in org: example blocks or verse
> block.

How about a third choice, without blocks?

There's no underlying reason why text that is on separate lines should
be treated as text on one line.

I cannot create "blocks" every time I take a random note of something
inside a heading. They are on separate lines inside the heading, so it
doesn't make sense that they should be on the same line in an export of
a heading. 

I need a way to have html export treat these lines of text as lines of
text, not a single paragraph and I need it to do this without having me
mark it a block.

-- 
Esben Stien is b0ef@e     s      a             
         http://www. s     t    n m
          irc://irc.  b  -  i  .   e/%23contact
           sip:b0ef@   e     e 
           jid:b0ef@    n     n

Re: Export HTML with Free Form Text

[Eric Abrahamsen]

Esben Stien <b0ef@esben-stien.name> writes:

> Rick Frankel <rick@rickster.com> writes:
>
>> You have (at least ;) two choices in org: example blocks or verse
>> block.
>
> How about a third choice, without blocks?
>
> There's no underlying reason why text that is on separate lines should
> be treated as text on one line.
>
> I cannot create "blocks" every time I take a random note of something
> inside a heading. They are on separate lines inside the heading, so it
> doesn't make sense that they should be on the same line in an export of
> a heading. 
>
> I need a way to have html export treat these lines of text as lines of
> text, not a single paragraph and I need it to do this without having me
> mark it a block.

You can do it with the preserve-breaks export option set to t. Either
"\n:t" in the #+OPTIONS line, or permanently by setting
org-export-preserve-breaks to t.

E

Re: Export HTML with Free Form Text

[Esben Stien]

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> You can do it with the preserve-breaks export option set to t. Either
> "\n:t" in the #+OPTIONS line, or permanently by setting
> org-export-preserve-breaks to t.

Hehe, I knew this would somehow be there;). 

Really great; thanks;)

-- 
Esben Stien is b0ef@e     s      a             
         http://www. s     t    n m
          irc://irc.  b  -  i  .   e/%23contact
           sip:b0ef@   e     e 
           jid:b0ef@    n     n