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

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

[Rasmus]

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
    %% ...

Expected result 

    %% ...
    \date{a\_b}
    %% ...
    \section{test}
    a\_b
    %% ...

Perhaps I'm misunderstanding how a parsed keyword is supposed to do...

Thanks,
Rasmus

-- 
And I faced endless streams of vendor-approved Ikea furniture. . .

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

[Nicolas Goaziou]

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.

Regards,

-- 
Nicolas Goaziou

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

[Rasmus]

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!

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

[Nicolas Goaziou]

Hello,

Rasmus <rasmus@gmx.us> 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 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)

Of course. Done.

Thank you.

Regards,

-- 
Nicolas Goaziou