From: "\"Höppner, Dierk\"" <Dierk.Hoeppner@tib.uni-hannover.de>
Subject: RE: Not seeing the wood because of so many trees
Date: Wed, 18 Feb 2004 07:43:32 +0100 [thread overview]
Message-ID: <F15A23A5EBA5D411A38400D0B7B9EB5F021AAFFC@nts3040.tib.uni-hannover.de> (raw)
I would second that. I can use it in computer program documentation for many
different things.
Greetings
Dierk
> -----Original Message-----
> From: Thomas A.Schmitz [mailto:thomas.schmitz@uni-bonn.de]
> Sent: Tuesday, February 17, 2004 9:18 AM
> To: ntg-context@ntg.nl
> Subject: Re: [NTG-context] Not seeing the wood because of so
> many trees
>
>
> Sorry for going back to an older thread, but I don't think
> the question
> was answered properly. Alexander Klink wanted to know how to typeset
> "{" and "}". Suggestions were "\type|{| and \type|}|" or "$\{$ and
> $\}$". Neither of which is satisfactory, because it will typeset them
> either in typewriter or in math font. We had a discussion
> about similar
> questions a while ago. I still think we should have "\{" and
> "\}" for
> this kind of thing. As long as this isn't available, I see no better
> solution than "\getglyph{Serif}{123}" and
> "\getglyph{Serif}{125}" vel.
> sim. For those of us working in the humanities, these curly
> braces are
> sometimes necessary (e.g., in critical editions), and having them in
> typewriter or math fonts isn't acceptable. So may I continue my rally
> for \{ etc.?
>
> All best
>
> Thomas
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
next reply other threads:[~2004-02-18 6:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 6:43 "Höppner, Dierk" [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-17 11:41 "Höppner, Dierk"
2004-02-16 14:26 How to setup german documents? Stefan Wachter
2004-02-17 8:17 ` Not seeing the wood because of so many trees Thomas A.Schmitz
2004-02-18 6:24 ` Johannes Hüsing
2004-02-18 7:50 ` Hans Hagen
2004-02-20 8:36 ` Hans Hagen
2004-02-13 10:09 "Höppner, Dierk"
2004-02-13 12:29 ` Alexander Klink
2004-02-13 15:04 ` Tobias Burnus
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=F15A23A5EBA5D411A38400D0B7B9EB5F021AAFFC@nts3040.tib.uni-hannover.de \
--to=dierk.hoeppner@tib.uni-hannover.de \
--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).