From: "Vasile Gaburici" <vgaburici@gmail.com>
To: "Hans Hagen" <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Font problems with latest minimals on Linux
Date: Wed, 13 Aug 2008 14:47:31 +0300 [thread overview]
Message-ID: <bef0d710808130447s468b4a26oca7ea4f02c6410bb@mail.gmail.com> (raw)
In-Reply-To: <48A2C384.6020808@wxs.nl>
On Wed, Aug 13, 2008 at 2:20 PM, Hans Hagen <pragma@wxs.nl> wrote:
> Vasile Gaburici wrote:
>>
>> As for the missing bold, it seems there's a bug in the naming scheme:
>> Ii the bold italic file gets read from the disk before the bold, then
>> you don't get the right entries. It so happens that most of the fonts
>> in that dir had bold before bold italic, e.g.
>>
>> fontnames | identifying ttf font /usr/share/fonts/vista/Verdanai.ttf
>> fontnames | identifying ttf font /usr/share/fonts/vista/Verdana.ttf
>> fontnames | identifying ttf font /usr/share/fonts/vista/Verdanaz.ttf
>> fontnames | identifying ttf font /usr/share/fonts/vista/Verdanab.ttf
>>
>> fontnames | identifying otf font
>> /usr/share/fonts/vista/C-series/Calibri Bold Italic.otf
>> fontnames | identifying otf font
>> /usr/share/fonts/vista/C-series/Calibri.otf
>> fontnames | identifying otf font
>> /usr/share/fonts/vista/C-series/Calibri Italic.otf
>> fontnames | identifying otf font
>> /usr/share/fonts/vista/C-series/Calibri Bold.otf
>>
>> So, I've added some extra code (patch attached) to print the names it
>> adds to the hash. As you can see there is a clash: both bold italic
>> and bold want to "own" bold...
>
> how do you define the font; don't use spaces!
??? If your're complaining that Calibri has spaces in the file name,
it's a non-issue here. Verdana has the same "bold not listed" problem,
even though there are no spaces in the file name...
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
> | www.pragma-pod.nl
> -----------------------------------------------------------------
>
>
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-08-13 11:47 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 [this message]
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
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=bef0d710808130447s468b4a26oca7ea4f02c6410bb@mail.gmail.com \
--to=vgaburici@gmail.com \
--cc=gaburici@cs.umd.edu \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.nl \
--cc=taco@elvenkind.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).