From: "Mats Broberg" <mats.broberg@chello.se>
Subject: RE: Additional steps taken since the first e-mail
Date: Sun, 27 Feb 2005 10:48:36 +0100 [thread overview]
Message-ID: <000201c51cb1$823be680$cbddd850@DJCPX90J> (raw)
In-Reply-To: <42211578.2080507@tiscali.de>
Johannes,
Thanks for the info, but I eventually managed to get the system up and
running last night, and am playing around with it now by testing various
and sundry examples in Hans' manuals.
I have to say, ConTeXt seems very, very promising for my publication
projects. I lack some features and functions, but all listmembers seem
to be very helpful and hopefully I could eventually get help cooking up
those.
Best regards,
Mats Broberg
On Behalf Of Johannes Werner
> newinstaller,
> i struggled more than one day with installation of context.
> i'm using a
> different OS (redhat linux) and have a different
> tex-distribution on it
> (tetex), but maybe this hint is useful for you too:
> in the tetex-distro there is a file .../texmf/web2c/fmtutil.cnf . in
> this file the lines for context were commented by default -
> you have to
> uncomment them and run "fmtutil --missing" afterwards (or "fmtutil
> -all", if you have more time). maybe in miktex there's somthing
> similiar. at my first try i forget to run fmtutil, edited texexec.ini
> and run "texexec --make" which worked. but afterwards context
> had some
> "special features".
next prev parent reply other threads:[~2005-02-27 9:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 9:04 Mats Broberg
2005-02-26 11:14 ` Matthew Huggett
2005-02-26 13:21 ` Mats Broberg
2005-02-26 14:16 ` Matthew Huggett
2005-02-27 11:12 ` h h extern
2005-02-28 19:25 ` Mats Broberg
2005-02-28 20:19 ` h h extern
2005-02-27 0:34 ` Johannes Werner
2005-02-27 8:48 ` VnPenguin
2005-02-27 21:21 ` Johannes Werner
2005-02-27 9:48 ` Mats Broberg [this message]
2005-02-27 15:11 ` h h extern
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='000201c51cb1$823be680$cbddd850@DJCPX90J' \
--to=mats.broberg@chello.se \
--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).