From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Re: Getting { in the input.
Date: Tue, 01 Jun 2004 20:50:55 +0200 [thread overview]
Message-ID: <6.1.1.1.2.20040601204641.07d57180@server-1> (raw)
In-Reply-To: <20040529095939.GB4113@puritan.pcp.ath.cx>
At 11:59 29/05/2004, you wrote:
>* in enco-def.tex this is
> \definecharacter textbraceleft {\mathematics{\{}}
>which means wrapping {\tt ...} around it doesn't give a teletyped brace
>but a nice mathematics one.
>
> > \type-{-
the problem is in (1) not all fonts having all chars [esp cmr have gaps]
and (2) handling catcodes when args are passed around,
in tables this is very nasty (and related to typeset tex in its own
language; compare xml where you have to escape < > " to do the same)
\tttf\string{
works quite well unless the scanner wants matching {}'s
as do \texescape \leftargument \rightargument
Hans
prev parent reply other threads:[~2004-06-01 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 11:13 Nikolai Weibull
2004-05-28 11:22 ` Patrick Gundlach
2004-05-29 9:59 ` Nikolai Weibull
2004-06-01 18:50 ` Hans Hagen [this message]
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=6.1.1.1.2.20040601204641.07d57180@server-1 \
--to=pragma@wxs.nl \
--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).