what happened to the #+OPTIONS: \n:t ?

what happened to the #+OPTIONS: \n:t ?

[katepano]

what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it 
does not work????

By the way nobody responded to my message!!!

http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html

why? is it a stupid question or it can't be implemented?

Regards

katepano

Re: what happened to the #+OPTIONS: \n:t ?

[Nick Dokos]

katepano <katepano@gmail.com> wrote:

> what happen to the #+OPTIONS: \n:t ? we need it back please!!!

Why? what's the use case?

> why it
> does not work????
> 
> By the way nobody responded to my message!!!
> 
> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html
> 
> why? is it a stupid question or it can't be implemented?
> 

[the question in that message is about exporting to a file with a different
file name than the default, in particular consisting partly of a datestamp]

Neither - but it is not the way it works currently. Again, if you can
present a compelling use case, maybe somebody will implement it (but
maybe not). You are always free to implement it yourself.

Nick

Re: what happened to the #+OPTIONS: \n:t ?

[katepano]

Thanks all for your responses, let me clarify a bit . . .

First of all I need <#+OPTIONS: \n:t>  because when I export an org file 
which has song lyrics in it I want to preserve the lines but accept css 
for nice printing (and singing afterwards).

Regarding, the other question, that of exporting, I need it because some 
software like blosxom can use a date stamp in the filename to present in 
a "timely" hierarchical manner the content (due to plugin 
http://www.enilnomi.net/download.html#permtimez ). If it could be done, 
a whole blog site (based on blosxom or derivatives) could be written as 
source org files and published automatically. I know probably blosxom is 
not good for bloging publicly but for personal use in ones PC is 
excellent (I use it for journal, tips and hacks database, study notes, 
book notes, songs database etc etc)

But do not bother, if it can't be done, ok. Actually I tried to do 
something myself, either through the org-publish.el or 
org-export-generic.el without much success :(

Well, thanks again

Katepano

On 04/04/2011 08:44 PM, Nick Dokos wrote:
> katepano<katepano@gmail.com>  wrote:
>
>> what happen to the #+OPTIONS: \n:t ? we need it back please!!!
> Why? what's the use case?
>
>> why it
>> does not work????
>>
>> By the way nobody responded to my message!!!
>>
>> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html
>>
>> why? is it a stupid question or it can't be implemented?
>>
> [the question in that message is about exporting to a file with a different
> file name than the default, in particular consisting partly of a datestamp]
>
> Neither - but it is not the way it works currently. Again, if you can
> present a compelling use case, maybe somebody will implement it (but
> maybe not). You are always free to implement it yourself.
>
> Nick
>
>

Re: what happened to the #+OPTIONS: \n:t ?

[Jambunathan K]

Hello 

> First of all I need <#+OPTIONS: \n:t>  because when I export an org
> file which has song lyrics in it I want to preserve the lines but
> accept css for nice printing (and singing afterwards).

Can you give an example of an org file, the html export as it is today,
the html export as you want it to be and may be the css file?

Jambunathan K.

Re: what happened to the #+OPTIONS: \n:t ?

[katepano]

[-- Attachment #1: Type: text/plain, Size: 583 bytes --]

Actually it is very simple . . . it misses the <br /> at the end of the 
lines
check the attachments (the song is in greek but I think will give you 
the idea)
Katepano


On 04/05/2011 10:18 AM, Jambunathan K wrote:
> Hello
>
>> First of all I need<#+OPTIONS: \n:t>   because when I export an org
>> file which has song lyrics in it I want to preserve the lines but
>> accept css for nice printing (and singing afterwards).
> Can you give an example of an org file, the html export as it is today,
> the html export as you want it to be and may be the css file?
>
> Jambunathan K.
>

[-- Attachment #2: 5-006-tsigaro-ateleiwto.org --]
[-- Type: text/plain, Size: 1561 bytes --]

#+STARTUP: showall
#+TITLE: 5-006 Τσιγάρο ατέλειωτο
#+OPTIONS:   H:3 num:nil toc:nil \n:t

*Συνθέτης:* Σωκράτης Μάλαμας
*Στιχουργός:* Γιώργος Αθανασόπουλος
*Έτος:* 1993  

#+BEGIN_QUOTE
Θα περπατήσω μοναχός κι αυτό το βράδυ
μήπως και βρω της λησμονιάς σου το νερό
και σε υπόγεια σκοτεινά θα βρω σημάδι
μ' ένα ποτήρι ως της αυγής τον πανικό

Τσιγάρο ατέλειωτο βαρύ η μοναξιά μου
μοιάζει γυναίκα κουρασμένη απ' το δρόμο
ρίχνει το γέλιο της και κάθεται κοντά μου
κερνάει τα επόμενα και με χτυπάει στον ώμο

Σ' ένα ποτήρι με φυτίλι αναμμένο
βλέπω τα μάτια σου και κλαίω σιωπηλά
και το μυαλό μου που είναι πάλι θολωμένο
στριφογυρνά των τραγουδιών σου τη θηλιά

Τσιγάρο ατέλειωτο βαρύ η μοναξιά μου
μοιάζει γυναίκα κουρασμένη απ' το δρόμο
ρίχνει το γέλιο της και κάθεται κοντά μου
κερνάει τα επόμενα και με χτυπάει στον ώμο
#+END_QUOTE

*Σημειώσεις:* 
Πρώτη εκτέλεση: Σωκράτης Μάλαμας  

*mp3:* 
[[../../mp3/tsigaro-ateleiwto.mp3]] 

#endofall

[-- Attachment #3: 5-006-tsigaro-ateleiwto_7.5.html --]
[-- Type: text/html, Size: 3191 bytes --]

[-- Attachment #4: 5-006-tsigaro-ateleiwto.html --]
[-- Type: text/html, Size: 3147 bytes --]

Re: Re: what happened to the #+OPTIONS: \n:t ?

[Christian Moe]

You just need BEGIN_VERSE ... END_VERSE instead of _QUOTE.

cm

On 4/5/11 9:31 AM, katepano wrote:
> Actually it is very simple . . . it misses the <br /> at the end of
> the lines
> check the attachments (the song is in greek but I think will give you
> the idea)
> Katepano
>
>
> On 04/05/2011 10:18 AM, Jambunathan K wrote:
>> Hello
>>
>>> First of all I need<#+OPTIONS: \n:t> because when I export an org
>>> file which has song lyrics in it I want to preserve the lines but
>>> accept css for nice printing (and singing afterwards).
>> Can you give an example of an org file, the html export as it is today,
>> the html export as you want it to be and may be the css file?
>>
>> Jambunathan K.
>>

Re: Re: what happened to the #+OPTIONS: \n:t ?

[katepano]

thanks for the tip, this is true, but not entirely the same . . .
Katepano

On 04/05/2011 10:52 AM, Christian Moe wrote:
> You just need BEGIN_VERSE ... END_VERSE instead of _QUOTE.
>
> cm
>
> On 4/5/11 9:31 AM, katepano wrote:
>> Actually it is very simple . . . it misses the <br /> at the end of
>> the lines
>> check the attachments (the song is in greek but I think will give you
>> the idea)
>> Katepano
>>
>>
>> On 04/05/2011 10:18 AM, Jambunathan K wrote:
>>> Hello
>>>
>>>> First of all I need<#+OPTIONS: \n:t> because when I export an org
>>>> file which has song lyrics in it I want to preserve the lines but
>>>> accept css for nice printing (and singing afterwards).
>>> Can you give an example of an org file, the html export as it is today,
>>> the html export as you want it to be and may be the css file?
>>>
>>> Jambunathan K.
>>>
>
>

Re: Re: what happened to the #+OPTIONS: \n:t ?

[Carsten Dominik]

On Apr 5, 2011, at 9:56 AM, katepano wrote:

> thanks for the tip, this is true, but not entirely the same . . .

In what way is it not the same?  Of cause it is not the same because it
does preserve line breaks.  Why do you not like this solution as much?
I would argue that in fact it is a *much better* solution than a dumb
preserve-all-linebreaks setting because

  - it allows you to have normal text before and after the poem
  - it wraps the output into a paragraph with class "verse",
    so you can add CSS styling to it without changing
    other formatting
  - it is cleaner in every possible way.

- Carsten

> Katepano
> 
> On 04/05/2011 10:52 AM, Christian Moe wrote:
>> You just need BEGIN_VERSE ... END_VERSE instead of _QUOTE.
>> 
>> cm
>> 
>> On 4/5/11 9:31 AM, katepano wrote:
>>> Actually it is very simple . . . it misses the <br /> at the end of
>>> the lines
>>> check the attachments (the song is in greek but I think will give you
>>> the idea)
>>> Katepano
>>> 
>>> 
>>> On 04/05/2011 10:18 AM, Jambunathan K wrote:
>>>> Hello
>>>> 
>>>>> First of all I need<#+OPTIONS: \n:t> because when I export an org
>>>>> file which has song lyrics in it I want to preserve the lines but
>>>>> accept css for nice printing (and singing afterwards).
>>>> Can you give an example of an org file, the html export as it is today,
>>>> the html export as you want it to be and may be the css file?
>>>> 
>>>> Jambunathan K.
>>>> 
>> 
>> 
> 

- Carsten

Re: what happened to the #+OPTIONS: \n:t ?

[Bernt Hansen]

katepano <katepano@gmail.com> writes:

> what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it
> does not work????

Something happened to it?  This feature was not removed intentionally.
I don't use this feature so I can't verify if it works or not without
more information.

Please provide an example org source file for export and instructions
with sample output from a previous release where it did work and what
you get now so we can understand the problem.

Please also provide the version of org-mode and Emacs that you are
using.

It is possible there's a bug that needs to be fixed.

> By the way nobody responded to my message!!!
>
> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html
>
> why? is it a stupid question or it can't be implemented?

No it's not a stupid question.  I don't think the functionality to
export documents with a date in the filename currently exists.

We all deal with the org-mode mailing list in our spare time.  I expect
lots of people (including me) saw your original post but nobody had
anything constructive to add.

Regards,
Bernt

Re: Re: what happened to the #+OPTIONS: \n:t ?

[Nick Dokos]

Bernt Hansen <bernt@norang.ca> wrote:

> katepano <katepano@gmail.com> writes:
> 
> > what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it
> > does not work????
> 
> Something happened to it?  This feature was not removed intentionally.
> I don't use this feature so I can't verify if it works or not without
> more information.

It's marked "DOES NOT WORK" in the manual. And git blame found this.

Nick

,----
| commit 0776eab890a7352144dd6c56523dbf3ab3f1b71d
| Author: Carsten Dominik <carsten.dominik@gmail.com>
| Date:   Wed Dec 9 22:27:38 2009 +0100
| 
|     Preserving line breaks for export no longer works
|     
|     ASCII export always preserves them - no other export format does.
| 
| diff --git a/doc/org.texi b/doc/org.texi
| index 1ba4352..8866704 100644
| --- a/doc/org.texi
| +++ b/doc/org.texi
| @@ -8926,7 +8926,7 @@ you can:
|  H:         @r{set the number of headline levels for export}
|  num:       @r{turn on/off section-numbers}
|  toc:       @r{turn on/off table of contents, or set level limit (integer)}
| -\n:        @r{turn on/off line-break-preservation}
| +\n:        @r{turn on/off line-break-preservation (DOES NOT WORK)}
|  @@:         @r{turn on/off quoted HTML tags}
|  ::         @r{turn on/off fixed-width sections}
|  |:         @r{turn on/off tables}
| diff --git a/lisp/ChangeLog b/lisp/ChangeLog
| index 025079e..0f23b9a 100755
| --- a/lisp/ChangeLog
| +++ b/lisp/ChangeLog
| @@ -1,5 +1,7 @@
|  2009-12-09  Carsten Dominik  <carsten.dominik@gmail.com>
|  
| +	* org-latex.el (org-export-latex-make-header): Remove \obeylines.
| +
|  	* org.el (org-make-link-regexps): Use John Gruber's regexp for
|  	urls.
|  
| diff --git a/lisp/org-latex.el b/lisp/org-latex.el
| index ce697a3..62f9a80 100644
| --- a/lisp/org-latex.el
| +++ b/lisp/org-latex.el
| @@ -1027,9 +1027,7 @@ OPT-PLIST is the options plist for current buffer."
|  	      (format "\\setcounter{tocdepth}{%s}\n\\tableofcontents\n\\vspace*{1cm}\n"
|  		      (min toc (plist-get opt-plist :headline-levels))))
|  	     (toc (format "\\setcounter{tocdepth}{%s}\n\\tableofcontents\n\\vspace*{1cm}\n"
| -			  (plist-get opt-plist :headline-levels)))))
| -     (when (plist-get opt-plist :preserve-breaks)
| -       "\\obeylines\n"))))
| +			  (plist-get opt-plist :headline-levels))))))))
|  
|  (defun org-export-latex-first-lines (opt-plist &optional beg end)
|    "Export the first lines before first headline.
`----

Re: Re: what happened to the #+OPTIONS: \n:t ?

[Carsten Dominik]

On 4.4.2011, at 19:57, Nick Dokos wrote:

> Bernt Hansen <bernt@norang.ca> wrote:
> 
>> katepano <katepano@gmail.com> writes:
>> 
>>> what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it
>>> does not work????
>> 
>> Something happened to it?  This feature was not removed intentionally.
>> I don't use this feature so I can't verify if it works or not without
>> more information.
> 
> It's marked "DOES NOT WORK" in the manual. And git blame found this.

Also, some information about the reasoning behind this decision is
in this thread:

http://thread.gmane.org/gmane.emacs.orgmode/20636

- Carsten

> 
> Nick
> 
> ,----
> | commit 0776eab890a7352144dd6c56523dbf3ab3f1b71d
> | Author: Carsten Dominik <carsten.dominik@gmail.com>
> | Date:   Wed Dec 9 22:27:38 2009 +0100
> | 
> |     Preserving line breaks for export no longer works
> |     
> |     ASCII export always preserves them - no other export format does.
> | 
> | diff --git a/doc/org.texi b/doc/org.texi
> | index 1ba4352..8866704 100644
> | --- a/doc/org.texi
> | +++ b/doc/org.texi
> | @@ -8926,7 +8926,7 @@ you can:
> |  H:         @r{set the number of headline levels for export}
> |  num:       @r{turn on/off section-numbers}
> |  toc:       @r{turn on/off table of contents, or set level limit (integer)}
> | -\n:        @r{turn on/off line-break-preservation}
> | +\n:        @r{turn on/off line-break-preservation (DOES NOT WORK)}
> |  @@:         @r{turn on/off quoted HTML tags}
> |  ::         @r{turn on/off fixed-width sections}
> |  |:         @r{turn on/off tables}
> | diff --git a/lisp/ChangeLog b/lisp/ChangeLog
> | index 025079e..0f23b9a 100755
> | --- a/lisp/ChangeLog
> | +++ b/lisp/ChangeLog
> | @@ -1,5 +1,7 @@
> |  2009-12-09  Carsten Dominik  <carsten.dominik@gmail.com>
> |  
> | +	* org-latex.el (org-export-latex-make-header): Remove \obeylines.
> | +
> |  	* org.el (org-make-link-regexps): Use John Gruber's regexp for
> |  	urls.
> |  
> | diff --git a/lisp/org-latex.el b/lisp/org-latex.el
> | index ce697a3..62f9a80 100644
> | --- a/lisp/org-latex.el
> | +++ b/lisp/org-latex.el
> | @@ -1027,9 +1027,7 @@ OPT-PLIST is the options plist for current buffer."
> |  	      (format "\\setcounter{tocdepth}{%s}\n\\tableofcontents\n\\vspace*{1cm}\n"
> |  		      (min toc (plist-get opt-plist :headline-levels))))
> |  	     (toc (format "\\setcounter{tocdepth}{%s}\n\\tableofcontents\n\\vspace*{1cm}\n"
> | -			  (plist-get opt-plist :headline-levels)))))
> | -     (when (plist-get opt-plist :preserve-breaks)
> | -       "\\obeylines\n"))))
> | +			  (plist-get opt-plist :headline-levels))))))))
> |  
> |  (defun org-export-latex-first-lines (opt-plist &optional beg end)
> |    "Export the first lines before first headline.
> `----
> 

Re: what happened to the #+OPTIONS: \n:t ?

[Bernt Hansen]

Bernt Hansen <bernt@norang.ca> writes:

> katepano <katepano@gmail.com> writes:
>
>> what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it
>> does not work????
>
> Something happened to it?  This feature was not removed intentionally.

Actually I stand corrected.  Carsten added the "DOES NOT WORK" text to
the info manual for this feature.

-\n:        @r{turn on/off line-break-preservation}
+\n:        @r{turn on/off line-break-preservation (DOES NOT WORK)}

so it seems this functionality has been orphaned (over a year ago)

--8<---------------cut here---------------start------------->8---
commit 0776eab890a7352144dd6c56523dbf3ab3f1b71d
Author: Carsten Dominik <carsten.dominik@gmail.com>
Date:   Wed Dec 9 22:27:38 2009 +0100

    Preserving line breaks for export no longer works
    
    ASCII export always preserves them - no other export format does.
--8<---------------cut here---------------end--------------->8---

Regards,
Bernt

Re: what happened to the #+OPTIONS: \n:t ?

[Bastien]

Hi Katepano,

katepano <katepano@gmail.com> writes:

> By the way nobody responded to my message!!!
>
> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html

Please be patient -- I have been busier than expected lately and
I could not read/reply all emails.  If nobody else replied to it,
it doesn't mean it's stupid or irrelevant, it just means this is
not a question that someone on this list can answer in less than
5 minutes -- but it's surely on someone's TODO list.

Thanks,

-- 
 Bastien

Re: what happened to the #+OPTIONS: \n:t ?

[Carsten Dominik]

Dear katepano,

as you can see, it has taken 11 emails on a high volume email list
to get the answer to your simple question.  More than 1100 people have
subscribed to this mailing list, an unknown number of people
read it on aggregators like gmane.  That is a lot of time and energy
spent unnecessarily.

Please take more care when formulating a question to the list
and try to give all necessary information from the start.
Here is an example on how you *could* have formulated your
initial mail:



----------------------------------------------------------------

Dear Org- mode people,

I am trying to write a poem in Orgmode, but when I am exporting
the poem to LaTeX or HTML, all the line breaks are lost!  I would like
to export the poem with the line break preserved.

I have studied the manual and have found that

   #+OPTIONS: \n:t

might be a way to achieve what I want.  But the feature is marked as
DOES NOT WORK in the manual.  Does anyone know why this is the case?
I have also search for "preserve breaks" in the mailing list archive:

http://search.gmane.org/?query=preserve+breaks&author=&group=gmane.emacs.orgmode&sort=relevance&DEFAULTOP=and&xP=org%09mode

and found a number of threads which match this query, but the results
have been confusing to me.  So I am wondering if someone here could
enlighten me what the best way is to achieve my goal.

Here is an example Org-file:

#+STARTUP: showall
#+TITLE: 5-006 Τσιγάρο ατέλειωτο
#+OPTIONS:   H:3 num:nil toc:nil \n:t

*Συνθέτης:* Σωκράτης Μάλαμας
*Στιχουργός:* Γιώργος Αθανασόπουλος
*Έτος:* 1993 

#+BEGIN_QUOTE
Θα περπατήσω μοναχός κι αυτό το βράδυ
μήπως και βρω της λησμονιάς σου το νερό
και σε υπόγεια σκοτεινά θα βρω σημάδι
μ' ένα ποτήρι ως της αυγής τον πανικό
#+END_QUOTE
----------------------------------------------------------------------------------------

I guess you would have gotten the right reply immediately.


On Apr 4, 2011, at 4:42 PM, katepano wrote:

> what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it does not work????
> 
> By the way nobody responded to my message!!!
> 
> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html

> why? is it a stupid question or it can't be implemented?


That was actually a much better message, and, as Bastien indicates,
there is no simple answer/solution at this time.

Regards

- Carsten


> 
> Regards
> 
> katepano
> 

- Carsten

Re: what happened to the #+OPTIONS: \n:t ?

[katepano]

Dear Dominik.
I see your point and it is accepted, of course. I admit, I should write 
my email more clearly. Anyway, thanks for your time.

On the other hand I really would like to see #+OPTIONS: \n:t working, if 
this possible and do not cause much frustration.

thanks anyway

Katepano

On 04/05/2011 11:04 AM, Carsten Dominik wrote:
> Dear katepano,
>
> as you can see, it has taken 11 emails on a high volume email list
> to get the answer to your simple question.  More than 1100 people have
> subscribed to this mailing list, an unknown number of people
> read it on aggregators like gmane.  That is a lot of time and energy
> spent unnecessarily.
>
> Please take more care when formulating a question to the list
> and try to give all necessary information from the start.
> Here is an example on how you *could* have formulated your
> initial mail:
>
>
>
> ----------------------------------------------------------------
>
> Dear Org- mode people,
>
> I am trying to write a poem in Orgmode, but when I am exporting
> the poem to LaTeX or HTML, all the line breaks are lost!  I would like
> to export the poem with the line break preserved.
>
> I have studied the manual and have found that
>
>     #+OPTIONS: \n:t
>
> might be a way to achieve what I want.  But the feature is marked as
> DOES NOT WORK in the manual.  Does anyone know why this is the case?
> I have also search for "preserve breaks" in the mailing list archive:
>
> http://search.gmane.org/?query=preserve+breaks&author=&group=gmane.emacs.orgmode&sort=relevance&DEFAULTOP=and&xP=org%09mode
>
> and found a number of threads which match this query, but the results
> have been confusing to me.  So I am wondering if someone here could
> enlighten me what the best way is to achieve my goal.
>
> Here is an example Org-file:
>
> #+STARTUP: showall
> #+TITLE: 5-006 Τσιγάρο ατέλειωτο
> #+OPTIONS:   H:3 num:nil toc:nil \n:t
>
> *Συνθέτης:* Σωκράτης Μάλαμας
> *Στιχουργός:* Γιώργος Αθανασόπουλος
> *Έτος:* 1993
>
> #+BEGIN_QUOTE
> Θα περπατήσω μοναχός κι αυτό το βράδυ
> μήπως και βρω της λησμονιάς σου το νερό
> και σε υπόγεια σκοτεινά θα βρω σημάδι
> μ' ένα ποτήρι ως της αυγής τον πανικό
> #+END_QUOTE
> ----------------------------------------------------------------------------------------
>
> I guess you would have gotten the right reply immediately.
>
>
> On Apr 4, 2011, at 4:42 PM, katepano wrote:
>
>> what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it does not work????
>>
>> By the way nobody responded to my message!!!
>>
>> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html
>> why? is it a stupid question or it can't be implemented?
>
> That was actually a much better message, and, as Bastien indicates,
> there is no simple answer/solution at this time.
>
> Regards
>
> - Carsten
>
>
>> Regards
>>
>> katepano
>>
> - Carsten
>
>
>
>

Re: what happened to the #+OPTIONS: \n:t ?

[Carsten Dominik]

On Apr 5, 2011, at 10:15 AM, katepano wrote:

> Dear Dominik.
> I see your point and it is accepted, of course. I admit, I should write my email more clearly. Anyway, thanks for your time.
> 
> On the other hand I really would like to see #+OPTIONS: \n:t working, if this possible and do not cause much frustration.

If you read the threads I have linked to you will see that
this is not at all simple.  An option like this would always
be a dirty hack that forces a backend into a state it was not
made for.  Using special markup and environments for code, poems,
you name it, on the other hand, is perfectly fine.

- Carsten

> 
> thanks anyway
> 
> Katepano
> 
> On 04/05/2011 11:04 AM, Carsten Dominik wrote:
>> Dear katepano,
>> 
>> as you can see, it has taken 11 emails on a high volume email list
>> to get the answer to your simple question.  More than 1100 people have
>> subscribed to this mailing list, an unknown number of people
>> read it on aggregators like gmane.  That is a lot of time and energy
>> spent unnecessarily.
>> 
>> Please take more care when formulating a question to the list
>> and try to give all necessary information from the start.
>> Here is an example on how you *could* have formulated your
>> initial mail:
>> 
>> 
>> 
>> ----------------------------------------------------------------
>> 
>> Dear Org- mode people,
>> 
>> I am trying to write a poem in Orgmode, but when I am exporting
>> the poem to LaTeX or HTML, all the line breaks are lost!  I would like
>> to export the poem with the line break preserved.
>> 
>> I have studied the manual and have found that
>> 
>>    #+OPTIONS: \n:t
>> 
>> might be a way to achieve what I want.  But the feature is marked as
>> DOES NOT WORK in the manual.  Does anyone know why this is the case?
>> I have also search for "preserve breaks" in the mailing list archive:
>> 
>> http://search.gmane.org/?query=preserve+breaks&author=&group=gmane.emacs.orgmode&sort=relevance&DEFAULTOP=and&xP=org%09mode
>> 
>> and found a number of threads which match this query, but the results
>> have been confusing to me.  So I am wondering if someone here could
>> enlighten me what the best way is to achieve my goal.
>> 
>> Here is an example Org-file:
>> 
>> #+STARTUP: showall
>> #+TITLE: 5-006 Τσιγάρο ατέλειωτο
>> #+OPTIONS:   H:3 num:nil toc:nil \n:t
>> 
>> *Συνθέτης:* Σωκράτης Μάλαμας
>> *Στιχουργός:* Γιώργος Αθανασόπουλος
>> *Έτος:* 1993
>> 
>> #+BEGIN_QUOTE
>> Θα περπατήσω μοναχός κι αυτό το βράδυ
>> μήπως και βρω της λησμονιάς σου το νερό
>> και σε υπόγεια σκοτεινά θα βρω σημάδι
>> μ' ένα ποτήρι ως της αυγής τον πανικό
>> #+END_QUOTE
>> ----------------------------------------------------------------------------------------
>> 
>> I guess you would have gotten the right reply immediately.
>> 
>> 
>> On Apr 4, 2011, at 4:42 PM, katepano wrote:
>> 
>>> what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it does not work????
>>> 
>>> By the way nobody responded to my message!!!
>>> 
>>> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html
>>> why? is it a stupid question or it can't be implemented?
>> 
>> That was actually a much better message, and, as Bastien indicates,
>> there is no simple answer/solution at this time.
>> 
>> Regards
>> 
>> - Carsten
>> 
>> 
>>> Regards
>>> 
>>> katepano
>>> 
>> - Carsten
>> 
>> 
>> 
>> 

- Carsten