ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: [XeTeX] Re: Is context working in XeTeX?
Date: Thu, 2 Dec 2004 15:19:48 +0000	[thread overview]
Message-ID: <20041202151948.26892@news.comp.lancs.ac.uk> (raw)
In-Reply-To: <73F97F05-4473-11D9-91D9-000D932DAC24@mac.com>

Dalyoung said this at Fri, 3 Dec 2004 00:04:24 +0900:

Hi, Dalyoung.

I'm cc'ing to the ConTeXt list, because I don't see why a context.fmt
file (or its equivalent) would be created. 

>Thank you for your reply. The command
>sudo texexec --xtx --make --alone en  creates a format 
>file-context.xfmt.

I was fairly certain cont-en.xfmt would have been created, and not
context.xfmt. Anyone in ConTeXt land know why?

>However, I still don't have an output.
>
>I tested a short file, after a long line of display, it stoped.
>But there is no pdf output.

Okay, that log looks like texexec didn't find the cont-en format, and it
tried making one. Most likely my patches to texexec didn't cover this
error condition (and I'll look at revising it), but really, you should be
creating a cont-en file with that command listed above.

Anyone else have a clue?

In the meantime, what does this return?:
 sudo texexec --xtx --make --alone cont-en

adam

>This is the last few lines of log.
>
>**********************************************
>ConTeXt  ver: 2004.11.23  fmt: 2004.12.2  int: english  mes: english
>
>  ) )
>(\end occurred when \unless\ifcsname on line 568 was incomplete)
>Beginning to dump on file cont-en.fmt
>  (format=cont-en 2004.12.2)
>35162 strings of total length 558625
>426688 memory locations dumped; current usage is 190&425628
>32984 multiletter control sequences
>\font\nullfont=nullfont
>0 words of font info for 0 preloaded fonts
>102 hyphenation exceptions
>Hyphenation trie of length 42714 has 1727 ops out of 35111
>   265 for language 11
>   265 for language 10
>   35 for language 9
>   35 for language 8
>   76 for language 7
>   88 for language 6
>   88 for language 5
>   235 for language 4
>   235 for language 3
>   224 for language 2
>   181 for language 1
>No pages of output.
>Transcript written on cont-en.log.
>fmtutil: /usr/local/teTeX/share/texmf.local/web2c/cont-en.fmt installed.
>/usr/local/teTeX/share/texmf/web2c/mktexupd: 
>/usr/local/teTeX/share/texmf.local/ls-R unwritable.
>(Fatal format file error; I'm stymied)
>
>            return code : 256
>               run time : 8 seconds
>
>         total run time : 9 seconds
>**********************************************

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept.     atl@comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

       reply	other threads:[~2004-12-02 15:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <73F97F05-4473-11D9-91D9-000D932DAC24@mac.com>
2004-12-02 15:19 ` Adam Lindsay [this message]
2004-12-02 16:59   ` Hans Hagen

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=20041202151948.26892@news.comp.lancs.ac.uk \
    --to=atl@comp.lancs.ac.uk \
    --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).