Re: XHTML export -   etc.

[Bastien <bzg@altern.org>]

About escaping characters in LaTeX, here is the rule I'm trying to stick
to: 

1. If a character is a special character in LaTeX, org-export-latex.el
   will escape it (so that this character will be correctly displayed in
   the resulting .dvi.)

2. If you escape such a character in the Org source file, then this
   character won't be escaped in the LaTeX source file, meaning that you
   want to refer to the special meaning of this character in LaTeX.

I don't use any notion of "Org's special character".

As long as this approach handles 99% of the special characters issues, I
think it's better not to try to invent any new specific Org syntax or to
impose new writing conventions...

I will work on the relevant code for that this week, let's see what
happen then.

Thanks,

"Daniel Clemente" <n142857@gmail.com> writes:

>>
>    Yes
>
>> >    Sometimes the \ means „don't escape", sometimes not.
>>
>> Are you okay with this:
>>
>>  Org  =>  LaTeX
>> ----------------
>>   \~  =>  ~
>>   \%  =>  %
>>   \#  =>  #
>>   \{  =>  {
>>   \}  =>  }
>>   \&  =>  &
>>   \_  =>  _
>>   \^  =>  ^
>>
>> (i.e. preventing special characters from being converted.)
>
>    Mmm... some of those characters /can/ already be written directly
> and they won't be interpreted, so you suggest adding a second method
> (ex: \# besides # ). Maybe some users find this confusing and prefer
> just one way to write each sign.
>    What do other people think? Should both # and \# write # ?
>
>    But your proposal would convert \ into the generic escaping character.
>    This is good since then you can always write \% (or with any
> character of the list) and you know it will be escaped.
>    But this is bad because this would only work on the characters you
> proposed, not on all. Ex \[ would probably write \[ and not [
>
>    I would suggest:
>  1.  Using \# just for signs that are part of org's syntax: _ ^
>  2.  Developing a general way to include a literal text without
> processing of org's syntax. For instance, the string *word* where both
> asterisks should be visible at the exported text (instead of a bold
> word). That can be implemented with start-end markers (ex:
> <literal>some *unprocessed* text</literal>) or with a marker before
> each sign: (ex: some \*unprocessed\* text).
>
>   1 and 2 can be combined if \# works with exactly all syntax
> elements, that means, all elements which would otherwise change the
> meaning and processing of the text. For instance:
> \*
> \/
> \[
> \]
> \#
> \|
> \=
> etc.
>   Of course, also \\ must be present to write a literal \
>   For the signs which are not part of org's syntax, you wouldn't need
> to write \  Ex: \( is unnecesary since ( has no meaning in org.
>
>
>    Sorry for starting anothed discussion :-)
>
>
> Daniel
>

-- 
Bastien