ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Module documentation
Date: Tue, 15 Apr 2008 01:26:30 +0200	[thread overview]
Message-ID: <6faad9f00804141626g655a6966n3032c52d233a4aaa@mail.gmail.com> (raw)
In-Reply-To: <115224fb0804140127u198ea6e1vcc36d0e488114d7c@mail.gmail.com>

On Mon, Apr 14, 2008 at 10:27 AM, Wolfgang Schuster wrote:
>
> On Fri, Apr 11, 2008 at 4:25 PM,  <richard.stephens@converteam.com> wrote:
>  >
>  > Hello all,
>  >
>  > I have been using Context for a while now and have learnt a lot from the
>  > manuals and wiki.  I now want to start to use features that are not
>  > documented.  On the wiki
>  > (http://wiki.contextgarden.net/Official_ConTeXt_Documentation#ConTeXt_Sources)
>  > I found the following command for producing a pdf output for a module:
>  >
>  > texmfstart texexec --module kpse:core-tab.tex
>  >
>  > which seems ideal for learning more.  When I run the above command line it
>  > creates a .ted file but then complains:
>  >
>  > "I can't find the format file 'cont-en.fmt'!"
>  >
>  > On Luigi Scarso's page
>  > (http://wiki.contextgarden.net/User:Luigi.scarso/modules.pdf) he suggests
>  > the following:
>  >
>  > texexec --module --pdf core-tab.tex
>  >
>  > but this returns no output at all, and no pdf.
>  >
>  > I am working on Windows.  I installed (this week) from the
>  > context/install/mswincontext.zip on the Pragma site and normally build from
>  > the Scite editor.
>  >
>  > Can anyone suggest what I'm doing wrong?
>
>  The mswincontext package use local settings for the paths and you can
>  use them only with scite or the setup script. You could try to add the path
>  for the setuptext script to the global path variables to use LuaTeX etc.
>  systemwide or you use the command line from scite.

You need to run something like (single line!!!):

C:\Programs\context\usr\local\context\tex\setuptex.bat
C:\Programs\context\usr\local\context\tex

in command prompt. For "texexec --module --pdf core-tab.tex" to work
you need to be in context base folder (tex/context/base; kpse makes
sure that you find & take the proper file automatically), and you
probably need to report a few problems in the source to be able to
compile that particular source file :)

Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2008-04-14 23:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11 14:25 richard.stephens
2008-04-14  8:27 ` Wolfgang Schuster
2008-04-14 23:26   ` Mojca Miklavec [this message]
2008-04-15 14:47 ` luigi scarso
  -- strict thread matches above, loose matches on Subject: below --
2008-04-15  8:13 richard.stephens
2001-01-02 17:40 Hans Hagen
2000-12-30 17:29 Giuseppe Bilotta

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=6faad9f00804141626g655a6966n3032c52d233a4aaa@mail.gmail.com \
    --to=mojca.miklavec.lists@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).