From: Carsten Dominik <dominik@science.uva.nl>
To: Emilio Garcia Cota <kota85@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: ~verbatim~ and =code= inconsistency exporting to Latex/HTML
Date: Tue, 17 Mar 2009 20:16:01 +0100 [thread overview]
Message-ID: <78A2A63F-E91F-4498-9F71-49C03CCF74E3@uva.nl> (raw)
In-Reply-To: <20090314192306.GA18749@t61>
On Mar 14, 2009, at 8:23 PM, Emilio Garcia Cota wrote:
> Carsten Dominik wrote:
>> The reason for this is that in LaTeX, inline pieces use
>>
>> \verb=[a-zA-Z_]=
>>
>> If "=" is part of the string, this construct fails. Whatever
>> character
>> I choose, it will fail for someone. I guess I could use the
>> paragraph symbol §, maybe this is the least likely one of them all?
>> it works in my LaTeX installation - could a few more people try this
>> on their systems?
>>
>> does
>>
>> \verb§bladibla§
>>
>> work in LaTeX?
>
> It works, but it would just move the problem somewhere else instead of
> solving it.
>
> More flexible solutions (yet more involved) could be:
> - Escape the characters ourselves (i.e. do not use \verb)
> - have a stack of suitable delimiter characters (i.e. any character
> except
> letters, * or space) and use the first one that's not in the region.
This is how it works now.
>
> A simpler solution would be to stick to '=' and '~' as delimiters,
> documenting this shortcoming when exporting to LaTeX.
>
>> Yes, I know this, both constructs use \verb in LateX. I'd say this
>> is
>> clearly good enough, though.
>
> Agreed.
>
>> Is there a non-monospaced, verbatim equivalent for \verb in LaTeX?
>
> AFAIK there isn't.
>
>> What should it influence? The standard LaTeX header we use
>> (maketitle)
>> does not list the email. You can build your own title, using
>> {{{email}}}
>> as a place holder.
>
> I was expecting it to generate something like this:
> \author{my Name $<$\href{mailto:e@ma.il}{e@ma.il}$>$
> Anyway yes, I could do it myself.
>
>
>
> By the way, using \verb inside other commands (such as \section) is
> forbidden in LaTeX; shall we include a warning in the manual, silently
> ignore ~~ and == in those places, or maybe just leave as it is (It'll
> break when compiling the.tex) ?
I think we can just have it break when compiling TeX. We cannot
possibly document TeX in the Org manual.
- Carsten
next prev parent reply other threads:[~2009-03-17 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 20:39 ~verbatim~ and =code= inconsistency exporting to Latex/HTML Emilio Garcia Cota
2009-03-13 17:46 ` Carsten Dominik
2009-03-14 2:23 ` Baoqiu Cui
2009-03-14 7:37 ` Carsten Dominik
2009-03-14 19:23 ` Emilio Garcia Cota
2009-03-17 19:16 ` Carsten Dominik [this message]
2009-03-14 19:31 ` Emilio Garcia Cota
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=78A2A63F-E91F-4498-9F71-49C03CCF74E3@uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=kota85@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).