From: Bastien <bzg@altern.org>
To: Daniel Clemente <n142857@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: XHTML export - etc.
Date: Mon, 12 Nov 2007 05:22:39 +0000 [thread overview]
Message-ID: <87k5oo11i8.fsf@bzg.ath.cx> (raw)
In-Reply-To: <ae9590aa0711091151lb1db9f8t4e0cfdbe7b77693e@mail.gmail.com> (Daniel Clemente's message of "Fri, 9 Nov 2007 20:51:36 +0100")
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
next prev parent reply other threads:[~2007-11-12 4:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 12:13 XHTML export - customizing via local variables Adam Spiers
2007-11-02 12:20 ` XHTML export - etc Adam Spiers
2007-11-02 15:26 ` Bastien
2007-11-02 15:19 ` Adam Spiers
2007-11-02 15:33 ` Daniel Clemente
2007-11-02 15:34 ` Daniel Clemente
2007-11-02 19:21 ` Bastien
2007-11-02 18:50 ` William Henney
2007-11-02 20:20 ` Daniel Clemente
2007-11-03 0:06 ` Bastien
2007-11-04 0:00 ` Daniel Clemente
2007-11-04 12:45 ` Bastien
2007-11-07 16:09 ` Daniel Clemente
2007-11-07 17:39 ` Bastien
2007-11-07 18:04 ` Daniel Clemente
2007-11-08 0:48 ` Bastien
2007-11-09 19:51 ` Daniel Clemente
2007-11-09 19:59 ` Daniel Clemente
2007-11-09 22:37 ` Eddward DeVilla
2007-11-09 23:40 ` Xiao-Yong Jin
2007-11-12 5:07 ` Bastien
2007-11-12 5:22 ` Bastien [this message]
2007-11-03 6:10 ` William Henney
2007-11-03 13:51 ` Bastien
2007-11-03 14:23 ` William Henney
2007-11-03 15:51 ` Bastien
2007-11-03 16:46 ` William Henney
2007-11-03 0:04 ` Bastien
2007-11-02 18:46 ` Bastien
2007-11-02 15:45 ` XHTML export - customizing via local variables Bastien
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=87k5oo11i8.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=n142857@gmail.com \
/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).