From: gnwiii@gmail.com
Subject: Re: Problem with ConTeXt installation
Date: Mon, 2 Oct 2006 10:16:21 -0300 [thread overview]
Message-ID: <22af238a0610020616w78663152o9c8c6b686496958f@mail.gmail.com> (raw)
In-Reply-To: <6faad9f00610011241i8bdf704g5b0b911bae3ac688@mail.gmail.com>
On 10/1/06, Mojca Miklavec <mojca.miklavec.lists@gmail.com> wrote:
> On 9/29/06, Taco Hoekwater wrote:
> > Steve Peter wrote:
> > > There is now a MikTeX package manager for Linux.
> >
> > And it is best not to use it since it ships a context that
> > believes it is running on windows...
ConTeXt should adjust to the differences (see ruby/tex.rb), but
someone may need to
search out the bugs and report them.
> But then it has to be fixed, not thrown away ... I bet that the main
> reason is one of the many "if (MikTeX)" switches in the source code
> assuming that MikTeX is running on windows. Are there any MikTeX/Lunux
> users around? (I work on windows 99% of time, but if I manage to
> install MikTeX on the linux partition, I'll give it a try.)
>
> The other thing is: I have no idea how the executables are created. I
> sent quite a few requests, so that now finally the ruby scripts are
> used instead of the old perl-based ones. But I don't have the
> slightest idea how they work under Linux.
I have ConTeXt under MikTeX and also on Fedora Core 5 both using the
Aug. 8 release from a separate texmf-cont tree, so I didn't install
the MikTeX version at all (I did steal
texmfstart.exe from W32tex).
There were some problems in the MikTeX-2.5 betas due to different
command-line switches in linux (and W32TeX) versions of pdftex, but I
thought that had been fixed in the
final version. There are some system specific flags set in
base/tex.rb to deal with any lingering differences, so if there are
problems I'd compare the options for pdftex and see if they are
reflected in tex.rb.
--
George N. White III <aa056@chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia
prev parent reply other threads:[~2006-10-02 13:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 13:45 Jeremy Johnson
2006-09-29 17:35 ` John R. Culleton
2006-09-29 17:45 ` Steve Peter
2006-09-29 17:53 ` Taco Hoekwater
2006-09-29 21:27 ` Jeremy Johnson
2006-09-30 6:52 ` Taco Hoekwater
2006-09-30 13:55 ` Sanjoy Mahajan
2006-09-30 20:21 ` Jeremy Johnson
2006-09-30 21:02 ` Sanjoy Mahajan
2006-10-01 19:41 ` Mojca Miklavec
2006-10-01 20:49 ` Newbie question: Different PDF-output with pdftex versus tex - ghostscript Robert Kroon
2006-10-02 9:06 ` Martin Schröder
2006-10-02 13:16 ` gnwiii [this message]
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=22af238a0610020616w78663152o9c8c6b686496958f@mail.gmail.com \
--to=gnwiii@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).