From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: font-syn.lua error
Date: Wed, 25 Nov 2009 08:15:48 +0100 [thread overview]
Message-ID: <fe8d59da0911242315i46bb88afjfa4becc48c909c6a@mail.gmail.com> (raw)
In-Reply-To: <0A1A466E-ADDA-4AE1-804D-198EB194BA4D@uni-bonn.de>
On Wed, Nov 25, 2009 at 8:05 AM, Thomas A. Schmitz
<thomas.schmitz@uni-bonn.de> wrote:
>
> On Nov 22, 2009, at 10:19 PM, Hans Hagen wrote:
>
>> that line says
>>
>> data_state = resolvers.data_state(),
>>
>> so resolvers has no data_state entry which in turn means that you run an old mtxrun, so maybe you need top copy mtxrun.lua manually to where it currently sits in yout path (as mtxrun)
>
> Just an afterthought to this problem: I discovered yesterday that the same file behaved quite differently in different viewers. It was a file compiled with the latest beta under linux, luatex 0.44, and with my own fonts.
>
> 1. In evince under linux, the file looked fine, no problems were apparent.
what about xpdf and ghostscript?
Can you also try with mupdf ?
--
luigi
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-11-25 7:15 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 18:49 Andreas Harder
2009-11-21 22:02 ` Tim Wraight
2009-11-22 12:16 ` Hans Hagen
2009-11-22 12:19 ` Andreas Harder
2009-11-22 13:14 ` Hans Hagen
2009-11-22 14:00 ` Khaled Hosny
2009-11-22 21:19 ` Hans Hagen
2009-11-22 21:26 ` Thomas A. Schmitz
2009-11-22 22:55 ` Hans Hagen
2009-11-25 7:05 ` Thomas A. Schmitz
2009-11-25 7:15 ` luigi scarso [this message]
2009-11-25 7:48 ` Thomas A. Schmitz
2009-11-25 8:40 ` Taco Hoekwater
2009-11-25 8:58 ` luigi scarso
2009-11-25 9:00 ` Taco Hoekwater
2009-11-25 9:04 ` luigi scarso
2009-11-25 10:02 ` Taco Hoekwater
2009-11-25 17:26 ` luigi scarso
2009-11-25 8:54 ` luigi scarso
2009-11-25 10:59 ` Alan BRASLAU
2009-11-25 11:06 ` Hans Hagen
2009-11-25 11:35 ` luigi scarso
2009-11-25 12:04 ` Martin Schröder
2009-11-25 9:34 ` Hans Hagen
2009-11-25 7:51 ` Alan BRASLAU
2009-11-25 8:37 ` Taco Hoekwater
2009-11-25 11:09 ` Alan BRASLAU
2009-11-25 11:19 ` Taco Hoekwater
2009-11-25 12:15 ` Hans Hagen
2009-11-25 14:23 ` luigi scarso
2009-11-25 12:19 ` Hans Hagen
2009-11-25 17:30 ` luigi scarso
2009-11-25 17:44 ` Hans Hagen
2009-11-25 18:18 ` Taco Hoekwater
2009-11-25 18:22 ` Hans Hagen
2009-11-25 19:27 ` luigi scarso
2009-11-26 10:33 ` Hans Hagen
2009-11-26 23:50 ` luigi scarso
2009-11-25 7:20 ` Taco Hoekwater
2009-11-25 7:46 ` Thomas A. Schmitz
2009-11-25 9:36 ` Hans Hagen
2009-11-22 14:04 ` Andreas Harder
2009-11-22 13:41 ` Mojca Miklavec
2009-11-22 13:59 ` Khaled Hosny
2009-11-22 14:09 ` Andreas Harder
2009-11-22 14:15 ` Wolfgang Schuster
2009-11-22 14:26 ` Andreas Harder
2009-11-22 14:51 ` Bernhard Rosensteiner
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=fe8d59da0911242315i46bb88afjfa4becc48c909c6a@mail.gmail.com \
--to=luigi.scarso@gmail.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).