emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>, "Thomas S. Dye" <tsd@tsdye.com>
Subject: Re: Problem with org-entities-user
Date: Wed, 19 Sep 2012 16:55:25 +0200	[thread overview]
Message-ID: <7CC1FB98-B071-429C-A230-B91D461104FD@gmail.com> (raw)
In-Reply-To: <87sjaeduh5.fsf@gmail.com>

On 19 sep. 2012, at 15:15, Nicolas Goaziou <n.goaziou@gmail.com> wrote:

> Hello,
> tsd@tsdye.com (Thomas S. Dye) writes:
>> I'm not sure about support for \hfill{}, etc.  The new latex and html
>> exporters pass \hfill{} through unchanged, which might be what the latex
>> author wants, or what the html author writing about latex commands
>> wants.
> It would not change anything for the HTML author, since \hfill{} would
> be exported as-is in any exporter. Though, it would be a less convenient
> for the LaTeX author, who would have to type @@latex:\hfill{}@@.
> On the other hand, I see at lest 3 reasons to remove support for such
> constructs:
> - consistency :: it's not possible to write raw HTML in an Org buffer,
>                 nor raw Texinfo. LaTeX shouldn't be treated
>                 differently.
> - clarity :: Recently, an user expected the \cite{} command to work in
>             a backend different from LaTeX.
> - ecumenism :: Removing LaTeXisms will make Org documents easier to
>               export to various back-ends.

These are all valid arguments.  However, I did design
Org-mode to be LaTeX-near to make sure that it becomes
easy and fast to type as a notes environment.  In my mind, a user
expecting \cite{...} to work in other backends is not necessarily
a wrong expectation, and if we introduce a syntax for doing citations
in HTML, why not using the LaTeX syntax for it?

So actually, it seems I do not fully agree with your *consistency*
argument.  While you are right that it is the logical and clean thing
if you view Org as a markup language created for export, it is not
necessarily the right solution for a convenience point of view.

Just my 5c, of course...

- Carsten

  reply	other threads:[~2012-09-19 14:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17  2:32 Problem with org-entities-user Thomas S. Dye
2012-09-17  6:41 ` Nicolas Goaziou
2012-09-17 16:37   ` Thomas S. Dye
2012-09-19 13:15     ` Nicolas Goaziou
2012-09-19 14:55       ` Carsten Dominik [this message]
2012-09-19 15:55         ` Nicolas Goaziou
2012-09-19 17:00           ` Bastien
2012-09-19 19:23             ` Thomas S. Dye
2012-09-20  7:33           ` Carsten Dominik
2012-09-20 11:57             ` Nicolas Goaziou
2012-09-20 13:36               ` Carsten Dominik
2012-09-22  8:52                 ` Nicolas Goaziou
2012-09-22 14:57                   ` Carsten Dominik
2012-09-22 16:52                     ` Thomas S. Dye
2012-09-23  8:30                     ` Nicolas Goaziou
2012-09-23 10:01                       ` Carsten Dominik
2012-09-23 18:18                         ` Thomas S. Dye

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=7CC1FB98-B071-429C-A230-B91D461104FD@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    --cc=tsd@tsdye.com \


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