From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Problem following "OpenType installation basics for ConTeXt" article
Date: Thu, 08 Sep 2005 09:58:52 +0200 [thread overview]
Message-ID: <431FEF3C.9080002@wxs.nl> (raw)
In-Reply-To: <a76b05c1050907235156aef9cc@mail.gmail.com>
Gavin Sinclair wrote:
>On 9/8/05, Mojca Miklavec <mojca.miklavec.lists@gmail.com> wrote:
>
>
>>Gavin Sinclair wrote:
>>
>>
>>>Adam Lindsay wrote:
>>>
>>>
>>>>(This doesn't look like the problem here, but) Are you running the
>>>>latest ConTeXt? There was a bug in the OpenType support in TeXFont that
>>>>was fixed in the distribution as of a couple months ago.
>>>>
>>>>
>>>I believe so. I installed ConTeXt for the first time about 10 days
>>>ago. It was a MiKTeX package, so I'm relying on that being up to
>>>date.
>>>
>>>
>>Don't rely on it. MikTeX has just updated ConTeXt (after two months).
>>Once during the last weekend and once on Monday (5.9.). However, the
>>format is from 27.7., 6 official releases ago. Minimal ConTeXt
>>distribution (or replacing some files in teTeX for example) is the
>>best way if you want to keep up-to-date. (MikTeX has some other
>>advantages however.)
>>
>>
>
>Thanks for the tip. texexec --version tells me
>
> context : ver: 2005.06.27
> cont-en : ver: 2005.06.27 fmt: 2005.8.31 mes: english
>
>which is pretty uncool. I guess I'll give the mswincontext.zip a try.
> I've hesitated because I don't see any clear instructions anywhere
>and the directory structure in that zip file is unusual for a Windows
>distro. Also don't want to ditch MiKTeX entirely because I'm
>experimenting with LyX. Sigh...
>
>How about just installing ConTeXt myself on top of MiKTeX? Should work, right?
>
>
just unzip the file in some safe place, running 'setuptex' (in a dos box) should give you an isolated tex environment; it's on my agenda to provide a miktex bintree as well, but only for testing since miktex has a rather good update mechanism (no reason to duplicate that -)
[my main reason for putting the minimals on the web is that they provide isolated environments, which is somethign i need for projects]; they also demonstrate what is needed for context
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2005-09-08 7:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-03 5:42 Gavin Sinclair
2005-09-07 6:27 ` Adam Lindsay
2005-09-07 8:17 ` Gavin Sinclair
2005-09-07 8:37 ` Taco Hoekwater
2005-09-07 15:54 ` Mojca Miklavec
2005-09-08 6:51 ` Gavin Sinclair
2005-09-08 7:58 ` Hans Hagen [this message]
2005-09-08 15:13 ` Gavin Sinclair
2005-09-08 15:31 ` Hans Hagen
2005-09-09 15:29 ` Linux and Context on 64 bit luigi.scarso
2005-09-09 15:44 ` Taco Hoekwater
2005-09-09 16:41 ` luigi.scarso
2005-09-09 17:48 ` Taco Hoekwater
2005-09-12 21:03 ` Stuart Jansen
2005-09-14 12:43 ` luigi.scarso
2005-09-14 13:11 ` Taco Hoekwater
2005-09-09 22:09 ` VnPenguin
2005-09-12 7:24 ` luigi.scarso
2005-09-09 20:44 ` Problem following "OpenType installation basics for ConTeXt" article Mojca Miklavec
2005-09-10 10:50 ` Gavin Sinclair
2005-09-11 17:52 ` 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=431FEF3C.9080002@wxs.nl \
--to=pragma@wxs.nl \
--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).