emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: n.goaziou@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: [patch][ox-latex] context-aware subscript
Date: Wed, 28 Aug 2013 13:55:52 +0200	[thread overview]
Message-ID: <87r4deqbav.fsf@gmx.us> (raw)
In-Reply-To: <87tximt7bb.fsf@gmail.com> (Nicolas Goaziou's message of "Mon, 19 Aug 2013 10:26:32 +0200")

Hi Nicolas,

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Thanks for the patch. Here are some comments about it.

Sorry about the late reply

> Rasmus <rasmus@gmx.us> writes:
>
>> Currently one can't write something like \beta_t and get a nice
>> result
>> in org when exporting to LaTeX (where nice result := $\beta_t$).
>> This
>> patch tries to fix it.
>
> Translating \beta_t into $\beta$$_\text{t}$ and \beta_bar into
> $\beta$$ \text{bar}$ is intended.

I know it's intended but I dislike it.  In earlier version of
ox-latex.el it didn't use the \text-macro.

> Unless you explicitly ask for math mode, Org defaults to text
> mode. The
> fact that it needs to go through math mode to insert some entities is
> not relevant. 

I disagree that it is irrelevant.  Even so, the spacing is wrong
cf. below.

> IOW, there's a difference between \beta_{$t$} and \beta_t.

No doubt.

> Also, merging consecutive subscript and superscript is fragile (and
> the
> code in `org-latex--script-size' could be improved in that area), as
> it
> also depends on user's filters. Here is a contrived example:
>
> Let's assume I have a filter which removes any subscript with the
> letter
> "a" in it. With the following code:
>
>   \beta_a
>
> Trying to merge both the entity and the subscript will return
>
>   $\beta
>
> which is wrong.

OK.  Perhaps it can be made less fragile.

>> As is evident from the pdf output
>>
>>   $\alpha$$\beta$$_{\text{t}}$ ≠ $\alpha$$\beta$$_{{t}}$ ≠
>> $\alpha\beta_{t}$
>>
>> There seems to be no difference between $\alpha$$\beta$ and
>> $\alpha\beta$ in the pdf, but the latter is more aesthetically
>> pleasing in the source.
>
> Beautifying LaTeX code is fine, unless it means adding yet another
> variable, and making some assumptions about user's configuration. If
> it ain't broken, don't fix it.

But it is broken, since even 

(*)    $\beta$$_{\text{t}}$

doesn't produce the correct output (spacing is wrong; compare to
$\beta_{\text{t}}$).  In LaTeX, (*) represents two "math elements",
although the intention was to get only one.

To sum up, my (implicit) claim and what I intended to fix with the
patch, was

  1. Fixing the bug that subscripts produce wrong output.
  2. Try to make the type of subscript configurable.  Previously,
     "math subscripts" were forced, now \text subscripts are forced.
     
Please let me know whether either 1. or 2. is up for discussion or
whether the current state is to be accepted.

–Rasmus

-- 
⠠⠵

  reply	other threads:[~2013-08-28 11:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-18  1:29 [patch][ox-latex] context-aware subscript Rasmus
2013-08-19  8:26 ` Nicolas Goaziou
2013-08-28 11:55   ` Rasmus [this message]
2013-08-28 13:38     ` Nicolas Goaziou
2013-08-28 13:46       ` Rasmus
2013-08-28 19:21         ` Nicolas Goaziou
2013-08-29 10:50           ` Rasmus
2013-08-31  8:11             ` Nicolas Goaziou
2013-08-31 13:59               ` Rasmus
2013-08-31 14:46                 ` Nicolas Goaziou

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=87r4deqbav.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@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).