Re: [O] [bug, ox-latex] Parsed keywords and export with subscript

Hello, Rasmus writes: > 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

Re: [O] [bug, ox-latex] Parsed keywords and export with subscript

Nicolas Goaziou writes: > Hello, > > Rasmus 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

Re: [O] [bug, ox-latex] Parsed keywords and export with subscript

Hello, Rasmus 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: > > %% ... >

[O] [bug, ox-latex] Parsed keywords and export with subscript

Hi, 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 %%