emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Thibault Polge <thibault@thb.lt>
Cc: emacs-orgmode@gnu.org
Subject: Re: Different exporters behave differently re exporter-specific lines
Date: Tue, 29 Oct 2019 16:54:34 +0100	[thread overview]
Message-ID: <87imo735tx.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87a79jy99x.fsf@thb.lt> (Thibault Polge's message of "Tue, 29 Oct 2019 14:24:26 +0100")

Hello,

Thibault Polge <thibault@thb.lt> writes:

> I'm not sure how this feature is called, but in Org you can restrict a line
> to a given exporter by prepending it with, eg, #+latex:
>
> There's a bug with some exporters f treat these lines as paragraph breaks,
> some don't.  For example, the following input:

This is not a bug in the exporters. The discrepancy exists in the output
languages, in particular in paragraphs. Org uses a definition of
a paragraph close to LaTeX's, so an Org paragraph isn't quite a HTML
paragraph.

> Hello
>
> #+latex: \TeX{}
> World
>
> #+html: Wide Web
> !
>
> Is exported to LaTeX as a single line, 

I doubt it. There are 3 paragraphs, even for LaTeX, since there are
empty lines.

> "Hello TeX World !", but to HTML
> as separate paragraphs:
>
> <p>
> Hello
> </p>
> <p>
> World
> </p>
> Wide Web
> <p>
> !
> </p>
>
> I wouldn't except these lines to introduce any paragraphs break.

Of course they should. You should look at the definition of a paragraph,
per Org syntax. Keywords cannot belong to a paragraph.

Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2019-10-29 15:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 13:24 Different exporters behave differently re exporter-specific lines Thibault Polge
2019-10-29 15:54 ` Nicolas Goaziou [this message]
2019-10-29 16:22   ` Thibault Polge
2019-10-29 17:19     ` Nicolas Goaziou
2019-10-29 16:29   ` Fraga, Eric

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=87imo735tx.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=thibault@thb.lt \
    /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

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).