Hi all, Nobody a clue on this? Cheers, Tim On 22 Mar 2020, 12:14 +0100, Tim Steenvoorden , wrote:

P.S. Same thing happens with math placed on top of arrows, like here

 $e,\sigma \xrightarrow{i} e',\sigma’$

Like to fix that too.

Cheers, Tim

On 22 Mar 2020, 12:10 +0100, Tim Steenvoorden , wrote:

...

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.

Cheers, Tim

––––

context --version mtx-context     | ConTeXt Process Management 1.02 mtx-context     | mtx-context     | main context file: /usr/local/texlive/2019basic/texmf-dist/tex/context/base/mkiv/context.mkiv mtx-context     | current version: 2019.03.21 21:39

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 :

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