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: bold versions of fonts
Date: Tue, 13 Feb 2007 12:19:05 +0100	[thread overview]
Message-ID: <DE5247CF-9167-45CB-A89D-663BB86700F9@uni-bonn.de> (raw)
In-Reply-To: <7E3A3376-74B8-4B43-8BCE-28DA786D853F@unibas.ch>


On Feb 13, 2007, at 12:05 PM, Jörg Hagmann wrote:

> Let me try again:
> After installing the LinLibertine and the Junicode fonts,  
> everything works (including bolditalic) except the bold version.
>
> - System: ubuntu, minimal tex/context installation
>
> - I followed the instructions by T. Schmitz (Practex Journal 2005:  
> Integrating TrueType Fonts into Context). I.e., using texfont.
>
> - After compiling the texfont-generated (texnansi-...-junicode.tex)  
> file, the pdf shows all the fonts (including bold).
>
> - A testfile stalled with the error message below.  After removing  
> the lines defining the bold version (typescript-file: see  
> attachment) everything except bold works. Testfile:  
> \usetypescriptfile[type-junicode] \usetypescript[Junicode]  
> \setupbodyfont[MyJunicode,12pt] \starttext etc.
>
> - Replacing the bold ttf, vf, and tfm fonts by those I found on the  
> fiee website didn't help.
>
>  I suspect that it will turn out to be an embarassing error, but I  
> couldn't spot it. Thanks for your help, Jörg
>
> <type-junicode.tex>
>
> Error message:
>
>> ConTeXt  ver: 2007.01.23 13:32 MKII  fmt: 2007.2.4  int: english/ 
>> english
>> .....
>>
>> ! Font \*MyJunicode7ptrmbfrm*:=[Junicode-Bold at 7.0pt not loadable:
>> Metric (TF
>> M) file not found.
>> <to be read again>
>>                     \relax
>> \xxdododefinefont ...tspec {#4}\newfontidentifier
>>                                                    \let
>> \localrelativefontsiz...
>>
>> \dodosettextfamilyB ...amily \fontsize \endcsname
>>                                                    \else \ifcsname
>> \fontclass...
>>
>> \dosettextfamily ...ttextfamily \scriptscriptfont
>>                                                    \let \fontbody
>> \scriptface...
>> <inserted text> ...y \c!tf \dosettextfamily \c!bf
>>                                                    \dosettextfamily
>> \c!sl \do...
>>
>> \synchronizetext ...athfonts \the \textstrategies
>>                                                    \fi
>> ...
>> l.4 \setupbodyfont[MyJunicode,12pt]
>

%\definefontsynonym [SerifBold] [[Junicode-Bold]%comment this line

There is one [ too many in this definition... Don't be too  
embarrassed, when you've looked at a file or a line for three hours,  
you don't see anything anymore.

Good luck

Thomas

  reply	other threads:[~2007-02-13 11:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 13:28 Jörg Hagmann
2007-02-13 11:05 ` Jörg Hagmann
2007-02-13 11:19   ` Thomas A. Schmitz [this message]
2007-02-14 10:34     ` Jörg Hagmann
2007-02-14 10:57       ` Janko Hauser
2007-02-14 11:03         ` Thomas A. Schmitz

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=DE5247CF-9167-45CB-A89D-663BB86700F9@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).