From: Carsten Dominik <carsten.dominik@gmail.com>
To: katepano <katepano@gmail.com>
Cc: emacs-orgmode@gnu.org, mail@christianmoe.com,
Jambunathan K <kjambunathan@gmail.com>
Subject: Re: Re: what happened to the #+OPTIONS: \n:t ?
Date: Tue, 5 Apr 2011 10:09:43 +0200 [thread overview]
Message-ID: <BB26D094-18BA-4FF8-9E51-4C87ED4E9932@gmail.com> (raw)
In-Reply-To: <4D9ACB15.4010805@gmail.com>
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
next prev parent reply other threads:[~2011-04-05 8:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 14:42 what happened to the #+OPTIONS: \n:t ? katepano
2011-04-04 17:44 ` Nick Dokos
2011-04-05 7:07 ` katepano
2011-04-05 7:18 ` Jambunathan K
2011-04-05 7:31 ` katepano
2011-04-05 7:52 ` Christian Moe
2011-04-05 7:56 ` katepano
2011-04-05 8:09 ` Carsten Dominik [this message]
2011-04-04 17:47 ` Bernt Hansen
2011-04-04 17:57 ` Nick Dokos
2011-04-04 18:44 ` Carsten Dominik
2011-04-04 18:02 ` Bernt Hansen
2011-04-04 23:28 ` Bastien
2011-04-05 8:04 ` Carsten Dominik
2011-04-05 8:15 ` katepano
2011-04-05 8:26 ` Carsten Dominik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BB26D094-18BA-4FF8-9E51-4C87ED4E9932@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=katepano@gmail.com \
--cc=kjambunathan@gmail.com \
--cc=mail@christianmoe.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).