From: Drazen Baic <dpeterx@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Unable to generate fonts
Date: Mon, 20 Apr 2009 15:03:29 +0200 [thread overview]
Message-ID: <6607a2f30904200603l4faea503x122f46036fda35d@mail.gmail.com> (raw)
In-Reply-To: <68DB196D-E58A-415D-807B-DBD7975F7B43@uni-bonn.de>
>> I've been running into trouble in both the alpha and beta versions of
>> Mark IV when trying to work with the fonts script:
>>
>> $ mtxrun --script fonts --list
>> MTXrun | font table: accessing the data table failed
>> MTXrun | font table: accessing the data table failed
>> ...text/tex/texmf-context/tex/context/base/font-syn.lua:333: attempt to
>> index field 'data' (a nil value)
>>
>> Also, using the "reload" option does nothing (it prints a blank line and
>> immediately exits). Without the fonts script I can't install or use any
>> custom fonts.
>
> I'm experiencing the same problem here.
>
> context version: 2009.04.18 13:47
>
> LuaTeX, Version snapshot-0.39.0-2009042009 luatex.web >= v2329
>
> None of my custom fonts work; I get errors
>
> define font | font with name texgyretermesregular is not found
> define font | unknown font texgyretermesregular, loading aborted
> define font | unable to define texgyretermesregular as \**dummy**
> define font | font with name texgyretermesregular is not found
> define font | unknown font texgyretermesregular, loading aborted
> define font | unable to define texgyretermesregular as \**dummy**
> define font | font with name texgyretermesregular is not found
> define font | unknown font texgyretermesregular, loading aborted
> define font | unable to define texgyretermesregular as \**dummy**
> define font | font with name texgyretermesregular is not found
> define font | unknown font texgyretermesregular, loading aborted
> define font | unable to define texgyretermesregular as \**dummy**
>
> Thomas
I had the same problem with LuaTeX, Version snapshot-0.39.0-2009041623, ConTeXt
ver: 2009.04.18 13:47 MKIV and mtxrun Version 1.20 after a new installation.
After copying the files name.tma and names.tmc from my old
installation directory to
tex/texmf-cache/luatex-cache/context/..../fonts/data/ it worked again.
Regards,
Drazen
___________________________________________________________________________________
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:[~2009-04-20 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 7:48 Thomas A. Schmitz
2009-04-20 7:58 ` Hans Hagen
2009-04-20 8:01 ` Thomas A. Schmitz
2009-04-20 13:03 ` Drazen Baic [this message]
2009-04-20 13:26 ` Thomas A. Schmitz
2009-04-20 15:41 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2009-04-18 8:52 Patrick Walton
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=6607a2f30904200603l4faea503x122f46036fda35d@mail.gmail.com \
--to=dpeterx@googlemail.com \
--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).