ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Font problems with latest minimals on Linux
Date: Thu, 14 Aug 2008 11:06:33 +0200	[thread overview]
Message-ID: <3482B312-288C-408D-BC1D-DC378659D263@uni-bonn.de> (raw)
In-Reply-To: <48A3F151.9040304@wxs.nl>


On Aug 14, 2008, at 10:48 AM, Hans Hagen wrote:

> the order is just one factor. what actually happens is that there is a
> compensation for buggy font names (as happens often in afm files) so  
> in
> practice one entry might become three entries; taco noticed that one  
> of
> the fallbacks create this way will then obscure a following one
>
> in your case it might be order on disk (although the current  
> mechanisms
> do some sorting) but on our machines more likely is that a bugged afm
> font obscures later otf's (with similar names)
>
> anyhow, we'll cook up a patch
>
> Hans

Very funny - I was following this thread with interest, yet had never  
encountered this problem. This morning, I played around with the  
minimals on my linux eeepc (had always used TeXLive, but saving some  
space seemed like a good idea) and got exactly the same problem:  
instead of bold, I get bold italic. If I typeset the same file with my  
TeXLive installation, I get proper bold. So Vasile is on to something  
here...

Thomas
___________________________________________________________________________________
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://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-08-14  9:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12 11:50 Vasile Gaburici
2008-08-13  7:43 ` Taco Hoekwater
2008-08-13  8:31   ` Hans Hagen
2008-08-13  9:21     ` Vasile Gaburici
2008-08-13 10:04       ` Hans Hagen
2008-08-13 10:05   ` Vasile Gaburici
2008-08-13 11:20     ` Hans Hagen
2008-08-13 11:47       ` Vasile Gaburici
2008-08-13 13:46         ` Wolfgang Schuster
2008-08-13 15:49           ` Vasile Gaburici
2008-08-13 16:19             ` Hans Hagen
2008-08-13 17:00             ` Taco Hoekwater
2008-08-14  4:33               ` Vasile Gaburici
2008-08-14  5:48                 ` Vasile Gaburici
2008-08-14  8:33                   ` Taco Hoekwater
2008-08-14  8:48                   ` Hans Hagen
2008-08-14  9:06                     ` Thomas A. Schmitz [this message]
2008-08-13 12:29 ` Taco Hoekwater

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=3482B312-288C-408D-BC1D-DC378659D263@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.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).