From: Jean-Pierre Le Narzul <lenarzul@free.fr>
Subject: \setuptyping
Date: Wed, 17 Sep 2003 23:54:09 +0200 [thread overview]
Message-ID: <779D02B8-E959-11D7-8163-00039376C1B6@free.fr> (raw)
Hi,
For typing Java code in a context document, I use \starttyping ...
\stoptyping.
I have a problem when I configure \setuptyping in the following way :
\setuptyping[typing][color=black,style=\ss,escape=/,option=commands]
If I put characters like { or _ in my source (between \starttyping and
\stoptyping)
, they do not appear in the produced document
{ character is replaced by - character
_ character is replaced by ' character
etc....
If I configure setuptyping in the following way
\setuptyping[typing][color=black,style=\tt,escape=/,option=commands]
(just change \ss to \tt)
everything is ok !
Any idea ?
thanks in advance for any help
jp
next reply other threads:[~2003-09-17 21:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 21:54 Jean-Pierre Le Narzul [this message]
2003-09-17 22:18 ` \setuptyping Patrick Gundlach
2003-09-17 22:41 ` \setuptyping Jean-Pierre Le Narzul
2003-09-18 7:07 ` \setuptyping Patrick Gundlach
2003-09-18 12:50 ` Re: latin-modern font lenarzul
2003-09-19 9:35 ` Patrick Gundlach
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=779D02B8-E959-11D7-8163-00039376C1B6@free.fr \
--to=lenarzul@free.fr \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).