From: Rasmus <rasmus@gmx.us>
To: mail@nicolasgoaziou.fr
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug, ox-latex] Parsed keywords and export with subscript
Date: Thu, 23 Mar 2017 16:23:08 +0100 [thread overview]
Message-ID: <87h92kqaoz.fsf@gmx.us> (raw)
In-Reply-To: <878to7ixu0.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Tue, 14 Mar 2017 18:15:35 +0100")
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Rasmus <rasmus@gmx.us> writes:
>
>> It would seem that parse doesn't behave correctly when
>> org-export-with-sub-superscripts is turned off via #+options.
>>
>> Example:
>>
>> #+options: ^:nil
>> #+date: a_b
>>
>> * test
>> a_b
>>
>> Exported result with ox-latex:
>>
>> %% ...
>> \date{a\(\_b\)}
>> %% ...
>> \section{test}
>> a\_b
>> %% ...
>>
>> Expected result
>>
>> %% ...
>> \date{a\_b}
>> %% ...
>> \section{test}
>> a\_b
>> %% ...
>
> Fixed. Thank you.
Backend-specific keywords are still an issue. E.g. try this example with
ox-latex or ox-koma-letter.
#+options: ^:nil
#+author: 2017_03_23
#+subject: 2017_03_23
#+title: 2017_03_23
#+subtitle: 2017_03_23
In patch 6cd42b08f9347a8d6084ec23548b754f9e02b2a1 you used
(dolist (entry org-export-options-alist)
in ‘org-export-as’ Would it be possible to use this list instead?
(append (org-export-get-all-options backend) org-export-options-alist)
Thanks,
Rasmus
--
Enough with the blah blah!
next prev parent reply other threads:[~2017-03-23 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 10:05 [bug, ox-latex] Parsed keywords and export with subscript Rasmus
2017-03-14 17:15 ` Nicolas Goaziou
2017-03-23 15:23 ` Rasmus [this message]
2017-03-23 15:47 ` 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=87h92kqaoz.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).