Re: LaTeX export

[Xiao-Yong Jin <xj2106@columbia.edu>]

Daniel Dehennin <dad@baby-gnu.org> writes:

> Le 5175 Septembre 1993, Bastien a tapoté:
>> Daniel Dehennin <dad@baby-gnu.org> writes:
>>
>>> I have 2 problems:
>>>
>>> - the underscore "_" is not escaped,
>>
>> Can you provide an example with context for both the input and the
>> output?  Maybe the #+OPTIONS: line could be useful as well.
>
> Well, having "_" in my ORG file was litteraly a "_" in my LaTeX source
> and compiling the LaTex source complains about missing $.
>
> I'm not able to reproduce this I don't understand what happend :-/
>
> But now, how can I have some\_thing in my LaTeX source ?
>
> I write many documents with something like:
>
> variable_name
>
>  and I don't want them to become:
>
> $variable_{name}$
>
> in my LaTeX source.

I've also spotted this.  I guess it's hard to make it right.
By default, org-mode doesn't require `$'s to recognize
certain region as math environment.  See info page

: 10.2 Subscripts and Superscripts
: ================================
: 
: Just like in LaTeX, `^' and `_' are used to indicate super- and
: subscripts.  Again, these can be used without embedding them in
: math-mode delimiters.  To increase the readability of ASCII text, it is
: not necessary (but OK) to surround multi-character sub- and superscripts
: with curly braces.  For example
: 
:      The mass if the sun is M_sun = 1.989 x 10^30 kg.  The radius of
:      the sun is R_{sun} = 6.96 x 10^8 m.
: 
:    To avoid interpretation as raised or lowered text, you can quote `^'
: and `_' with a backslash: `\_' and `\^'.
: 
:    During HTML export (*note HTML export::), subscript and superscripts
: are surrounded with `<sub>' and `<sup>' tags, respectively.

But I would like to propose a work-around.  How about make
`^' and `_' in those regions marked as =this_code= or
something similar not be interpreted as super- and
subscripts?


Xiao-Yong
-- 
    c/*    __o/*
    <\     * (__
    */\      <