ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <gip.bilotta@iol.it>
Subject: Re[2]: Not seeing the wood because of so many trees
Date: Wed, 18 Feb 2004 16:20:35 +0100	[thread overview]
Message-ID: <1835728886.20040218162035@iol.it> (raw)
In-Reply-To: <BD379133-6121-11D8-A4E7-000A95B9ADE2@uni-bonn.de>

Tuesday, February 17, 2004 Thomas A.Schmitz wrote:

> 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.?

Sorry for the delay. \textbraceleft and \textbraceright should
work ok if encodings are set up correctly.

-- 
Giuseppe "Oblomov" Bilotta

  parent reply	other threads:[~2004-02-18 15:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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-18 15:20   ` Giuseppe Bilotta [this message]
2004-02-19 17:21     ` Re[2]: " Thomas A.Schmitz
2004-02-20  8:36   ` Hans Hagen

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=1835728886.20040218162035@iol.it \
    --to=gip.bilotta@iol.it \
    --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).