ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: \bigr bracket missing in antykwa
Date: Tue, 18 Apr 2006 06:02:21 -0400 (EDT)	[thread overview]
Message-ID: <Pine.WNT.4.63.0604180555440.3068@nqvgln> (raw)
In-Reply-To: <4443BFE0.1020308@wxs.nl>

On Mon, 17 Apr 2006, Hans Hagen wrote:

> well, i traced back the way this brace ends up in the pdf file and this
> is what i observe:
>
> - the antt and cm ex tfm files have exactly the same values (although
> antt is 7 bit safe)
> - so the problem must be in the map file and/or encoding
> - and, surprise,
>
> encantt-ex[
> /parenleftbig
> /parenrightbig
> /bracketleftbig
> /bracketrightbig
> /floorleftbig
> /floorrightbig
> /ceilingleftbig
> /ceilingrightbig
> /braceleftbig
> /.notdef
> /angbracketleftbig
>
> the bracerightbig is undefined here
>
> i suspect that there is some bug in the scripts that generate these 
> files so let's feed this back to jacko/janusz; you need to patch:
>
> antt-ex.enc
> iwona.enc
> kurier.enc

So shall I send a bug report to them with a summary of this thread or
have you already done that?

> (maybe an intermediate patch in the tex live repository is ok for the moment)
>
> /braceleftbig
> /bracerightbig
>
> the fonts themselves are ok

For my document, I changed the sizes to \bigg (or normal size).

Aditya

-- 
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008

  reply	other threads:[~2006-04-18 10:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-14  2:22 Aditya Mahajan
2006-04-14  8:18 ` Hans Hagen
2006-04-14 12:10   ` Mojca Miklavec
2006-04-14 18:33     ` Hans Hagen
2006-04-16  0:56       ` Mojca Miklavec
2006-04-17 16:18         ` Hans Hagen
2006-04-18 10:02           ` Aditya Mahajan [this message]
2006-04-18 11:47             ` 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=Pine.WNT.4.63.0604180555440.3068@nqvgln \
    --to=adityam@umich.edu \
    --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).