emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Aaron Ecay <aaronecay@gmail.com>
To: Anders Johansson <mejlaandersj@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: org-entities: Another issue [was: org-entities: why \lang instead of \langle?]
Date: Tue, 25 Mar 2014 10:02:57 -0400	[thread overview]
Message-ID: <87y4zy9yhh.fsf@gmail.com> (raw)
In-Reply-To: <5331885D.4050702@gmail.com>

Hi Anders,

2014ko martxoak 25an, Anders Johansson-ek idatzi zuen:
>
> (I continue in the same thread as this is related)
>
> org-entities has:  ("slash" "/" nil "/" "/" "/" "/")
>
> A LaTeX user entering \slash would probably expect to have this exported
> as \slash (which produces a breaking "/", not the same thing as just
> entering "/" in LaTeX).
>
> So it should rather be:  ("slash" "\\slash" nil "/" "/" "/" "/")
>
> Could this be changed without breaking people's documents?

It’s important for LaTeX users to have a way to write “/” into the
output – sometimes it might not possible to use a literal “/” in org,
because of the /emphasis/ markup.

It seems to me (as a user of both latex and html export) that most of
the time I want “/” in the output, regardless of backend.  Maybe (org’s)
\slash should retain its meaning, and there should be a new entity which
obeys your proposal.

It also seems like \slash in latex has some odd properties
wrt. hyphenation:
<https://tex.stackexchange.com/questions/97310/slash-allows-for-hyphenation-of-only-the-word-on-its-left-how-to-fix-it-for-th>.
So maybe latex power users would rather write something more complicated
using the @@latex:\slash\hspace{0pt}@@ syntax.

Thanks,

--
Aaron Ecay

      reply	other threads:[~2014-03-25 14:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23  9:36 org-entities: why \lang instead of \langle? Anders Johansson
2014-03-13 15:46 ` Bastien
2014-03-25 13:45   ` org-entities: Another issue [was: org-entities: why \lang instead of \langle?] Anders Johansson
2014-03-25 14:02     ` Aaron Ecay [this message]

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=87y4zy9yhh.fsf@gmail.com \
    --to=aaronecay@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mejlaandersj@gmail.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).