ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Tim Steenvoorden <tim.steenvoorden@gmail.com>
To: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Primes far too high in Lucida Type1
Date: Tue, 31 Mar 2020 16:35:48 +0200	[thread overview]
Message-ID: <CAJjcFnLP816HeW0cfrMqa6huTBpuZujVSYgoG73jjZ8SnU9VVg@mail.gmail.com> (raw)
In-Reply-To: <4e039137-c351-4df9-64db-79735d8d3219@gmail.com>

Hi Wolfgang,

That 's a pity indeed. I played around a bit and found a dirty hack
using catcodes. Maybe not the best solution, but it works for me.
Posting it here for future reference.

```
\define\textprime{'}
\makecharacteractive '
\define'{\lowerbox{0.3ex}\hbox{\math{\textprime}}}
```

Cheers,
Tim

Op zo 29 mrt. 2020 om 21:04 schreef Wolfgang Schuster
<wolfgang.schuster.lists@gmail.com>:
>
> Tim Steenvoorden schrieb am 22.03.2020 um 12:10:
> > Hi all,
> >
> > I’m trying to typeset a document using Lucida Type1 fonts. Primes are
> > put way too high. Also, kerning with punctuation characters placed after
> > a prime are too wide. This can be seen in attached rendering of below
> > example.
> >
> > $e,\sigma \rightarrow e',\sigma’$
> >
> > Is there a quick way to fix this? I don’t have access tot the OTF
> > unfortunately. Running ConTeXt TeXlive 2019 on macOS 10.15.3.
>
> I'm sorry for the bad news but without a patch for the font (which can
> probably applied with a goodies file) there is nothing which can be
> done. As the Type 1 version of the Lucida fonts had a few problems in
> the last few years with ConTeXt MkIV I don't think Hans has much
> interest to fix them again (especially when you can expect new problems
> in the future).
>
> The best way here is to use another font or spend the money for the
> OpenType version.
>
> Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2020-03-31 14:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a55af57a-eb3d-43c6-9c90-df8151efa8c4@Spark>
2020-03-22 11:10 ` Tim Steenvoorden
2020-03-22 11:14   ` Tim Steenvoorden
2020-03-25  9:32     ` Tim Steenvoorden
2020-03-29 19:04   ` Wolfgang Schuster
2020-03-31 14:35     ` Tim Steenvoorden [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=CAJjcFnLP816HeW0cfrMqa6huTBpuZujVSYgoG73jjZ8SnU9VVg@mail.gmail.com \
    --to=tim.steenvoorden@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=wolfgang.schuster.lists@gmail.com \
    /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).