From: Taco Hoekwater <taco@elvenkind.com>
Cc: Robin.Fairbairns@cl.cam.ac.uk
Subject: Re: Re: LaTeX2ConTeXt : external links not work after recompiled
Date: Sun, 5 Dec 2004 13:05:04 +0100 [thread overview]
Message-ID: <20041205130504.53b3db0e.taco@elvenkind.com> (raw)
In-Reply-To: <m2vfbht8gb.fsf@levana.de>
Hi,
Robin Fairbairns wrote:
>
> can someone please persuade hans to replace the context/current on his
> web site with something that works. what appears on context/current
> gets to ctan, and what gets to ctan appears in tetex. a mail to me
> would expedite the corrected stuff appearing on ctan.
A fix in the works, I assume. Meanwhile ...
> more serious is (i bet) that that context is also on the texlive tree,
> and that really _is_ about to ship.
The ISO named texlive2004-inst-20041127.iso on CTAN dated is the one that
is being burned, I assume? If so, then there is good news: TL does not
contain 2004.11.23 but version 2004.11.17, and that version works OK on
Patrick's example, using acroread 5.0.5 on linux.
It is a bit odd that a beta version of context was used for production TL and
does not have the bug whereas the tetex beta used the production version of
context and does have the bug. ;-)
Greetings, Taco
next prev parent reply other threads:[~2004-12-05 12:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 16:14 VnPenguin
2004-12-04 16:32 ` Patrick Gundlach
2004-12-04 16:39 ` VnPenguin
2004-12-04 18:47 ` Adam Lindsay
2004-12-04 18:56 ` Patrick Gundlach
2004-12-04 19:04 ` VnPenguin
2004-12-04 19:39 ` Patrick Gundlach
2004-12-04 20:25 ` VnPenguin
2004-12-04 19:02 ` VnPenguin
2004-12-04 23:13 ` Patrick Gundlach
2004-12-05 9:12 ` Patrick Gundlach
2004-12-05 12:05 ` Taco Hoekwater [this message]
2004-12-05 20:37 ` h h extern
2004-12-05 20:31 ` h h extern
2004-12-05 20:33 ` h h extern
2004-12-05 23:32 ` VnPenguin
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=20041205130504.53b3db0e.taco@elvenkind.com \
--to=taco@elvenkind.com \
--cc=Robin.Fairbairns@cl.cam.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).