emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Maxim Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Comments break up a paragraph when writing one-setence-per-line
Date: Wed, 21 Jul 2021 23:13:14 +0700	[thread overview]
Message-ID: <sd9h2q$t9a$1@ciao.gmane.io> (raw)
In-Reply-To: <87bl6vy9mw.fsf@ucl.ac.uk>

On 21/07/2021 22:22, Eric S Fraga wrote:
> On Wednesday, 21 Jul 2021 at 21:48, Maxim Nikulin wrote:
>> It is at least fragile. HTML export results in separate paragraphs:
> Yes, I said "if exporting to LaTeX"... ;-)
>> I am unsure, but "#+latex:" probably belongs to "Keywords" that are
>> elements, so it should end a paragraph. If such interpretation is
>> correct than either LaTeX exporter has a bug or syntax description
>> should be justified.
> No, I don't think of it as a keyword and it cannot end a paragraph as it
> would then break any document that uses such constructs.  Not sure what
> to call it but it falls into the same category as inline directives like
> @@latex:...@@.  And, in fact, this would work as well as the first
> example, again failing for HTML export:
> (untested) :-)

"@@backend:@@" aka Export Snippet is an "object", not "element"
thus is should not start paragraph

Though... With LaTeX you should be careful

---- >8 ----
One sentence is here.
@@html:inline HTML@@
Second sentence.
---- 8< ----

Export to LaTeX:
---- >8 ----
One sentence is here.

Second sentence.
---- 8< ----

"@@latex:@@" line in HTML export generates empty line but does not break 
the paragraph. "#+html:" construct splits paragraphs:

One sentence is here.
#+html: <!-- HTML -->
Second sentence.

One sentence is here.
<!-- HTML -->
Second sentence.

I find behavior of HTML exporter more consistent but partially the 
difference originates in distinct interpretation of empty lines.

P.S. There are two types of comments: ones that should be exported as 
comments and that should be completely removed. "#+latex: %" comments 
leak to LaTeX, though they will be stripped during generation of PDF. So 
depending of what format you should provide, such behavior may be 
acceptable or not.

  reply	other threads:[~2021-07-21 16:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16 16:06 Comments break up a paragraph when writing one-setence-per-line William Denton
2021-07-16 16:34 ` Bruce D'Arcus
2021-07-16 18:10   ` Kaushal Modi
2021-07-17  1:50     ` Samuel Wales
2021-07-18  8:21 ` Maxim Nikulin
2021-07-19 14:03 ` Eric S Fraga
2021-07-21 14:48   ` Maxim Nikulin
2021-07-21 15:22     ` Eric S Fraga
2021-07-21 16:13       ` Maxim Nikulin [this message]
2021-10-02 17:57         ` Tom Gillespie
2021-10-03 11:34           ` Max Nikulin

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:

  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='sd9h2q$t9a$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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