ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: update
Date: Fri, 3 Jun 2005 09:14:42 +0200	[thread overview]
Message-ID: <DE8D25E9-8D77-4C75-A30C-A764D0F39D3B@uni-bonn.de> (raw)
In-Reply-To: <429FF6AD.8010407@elvenkind.com>

Thanks Taco! No, I'm using pdfetex, not XeTeX. Here's the line:

% pdfetex --version
pdfeTeX 3.141592-1.21a-2.2 (Web2C 7.5.4)
kpathsea version 3.5.4
Copyright (C) 1997-2004 Peter Breitenlohner (eTeX)/Han The Thanh  
(pdfTeX).
Kpathsea is copyright (C) 1997-2004 Free Software Foundation, Inc.
There is NO warranty.  Redistribution of this software is
covered by the terms of both the pdfeTeX copyright and
the GNU General Public License.
For more information about these matters, see the files
named COPYING and the pdfeTeX source.
Primary author of pdfeTeX: Peter Breitenlohner (eTeX)/Han The Thanh  
(pdfTeX).
Kpathsea written by Karl Berry and others.

And as I wrote: the rest of ConTeXt seems to be working alright, my  
documents compile fine, so don't spend too much time on it. I still  
have to see for my linux installation, I haven't been able to upgrade  
ConTeXt under linux for quite a few releases now.

Best

Thomas

On Jun 3, 2005, at 8:20 AM, Taco Hoekwater wrote:

> Thomas A. Schmitz wrote:
>
>> Hi Hans,
>> sorry to rain on your parade, but I'm not sure that the latest   
>> version is working as it should. I tried on OS X + gwtex. After   
>> unzipping in texmf.local and regenerating the formats, I get this   
>> output (even after rerunning mktexlsr):
>> % texexec --version
>>
>
> texexec --version can be broken independant of the rest of  
> texexec. :-)
>
> From your comments I believe that the actual format generation is
> correct now, and it is just the version report that cannot keep up
> with the changes. Not a big thing, but of course it should be fixed.
>
> Since that is my code, I will can a patch for (Hans to apply).
> Are you using XeTeX? If yes, can you (or someone else) send me XeTeX's
> banner line(s)? I mean the line you get if you only start the
> executable.  For instance, my pdfetex has:
>
>   This is pdfeTeX, Version 3.141592-1.21b-2.2 (Web2C 7.5.4)
>   **
>
> This is needed for the tex discovery line:
>
>                    tex : unknown
>
>
> Greetings, Taco
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>

  reply	other threads:[~2005-06-03  7:14 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02 20:49 update Hans Hagen
2005-06-02 21:24 ` update Thomas A. Schmitz
2005-06-03  6:20   ` update Taco Hoekwater
2005-06-03  7:14     ` Thomas A. Schmitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-20 16:28 update Hans Hagen via ntg-context
2023-02-23 21:07 update Hans Hagen via ntg-context
2023-02-24  9:30 ` update Otared Kavian via ntg-context
2022-08-05  9:52 update Hans Hagen via ntg-context
2022-08-05 14:37 ` update Aditya Mahajan via ntg-context
2022-08-05 15:23   ` update Hans Hagen via ntg-context
2022-08-05 14:48 ` update Henning Hraban Ramm via ntg-context
2022-08-05 22:26 ` update Jeong Dal via ntg-context
2021-09-13  8:07 update Hans Hagen via ntg-context
2021-09-13  8:37 ` update Henning Hraban Ramm via ntg-context
2021-09-13  9:12   ` update Hans Hagen via ntg-context
2021-09-13 20:14     ` update Henning Hraban Ramm via ntg-context
2021-09-14  5:50       ` update Hans Hagen via ntg-context
2021-09-13 19:51 ` update Garulfo via ntg-context
2020-06-25  9:34 update Hans Hagen
2020-06-19  9:42 update Hans Hagen
2008-01-28 20:36 update Hans Hagen
2008-01-29  8:04 ` update Johannes Graumann
2008-01-29  8:22   ` update Hans Hagen
2008-01-29 17:01 ` update Johannes Graumann
2008-01-29 17:04   ` update Hans Hagen
2006-04-23 22:07 update Hans Hagen
2006-04-25  4:30 ` update Aditya Mahajan
2006-04-25  6:52   ` update Hans Hagen
2005-11-30 16:56 update Hans Hagen
2004-06-18 16:33 update Hans Hagen
2004-06-18 20:00 ` update Willi Egger
2004-06-18 20:15   ` update Henning Hraban Ramm
2004-06-19 11:54     ` update Willi Egger
2004-06-19 22:05       ` update Hans Hagen Outside
2004-06-19 14:41   ` update Gary Pajer
2004-06-19 14:47     ` update Gary Pajer
2004-06-19 22:10     ` update Hans Hagen Outside
2004-06-19 21:56   ` update Hans Hagen Outside
2004-06-20 20:49     ` update Willi Egger
2004-06-21 19:31       ` update Willi Egger
2004-06-20 15:07 ` update Patrick Gundlach
2004-06-17  0:09 update Hans Hagen
2001-07-11 15:05 update Hans Hagen
2001-07-13  8:00 ` update Giuseppe Bilotta
2001-07-13 12:53   ` update Hans Hagen
2000-05-11 10:49 update Hans Hagen
     [not found] ` <000901bfbb8c$bc388720$9b4461c3@chris>
2000-05-12 12:20   ` update Hans Hagen
1999-07-20 16:34 update Hans Hagen
1999-06-20 16:26 update Hans Hagen
1999-03-25 16:43 update Hans Hagen
1999-03-26 13:15 ` update Taco Hoekwater
1999-01-29 12:40 update 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=DE8D25E9-8D77-4C75-A30C-A764D0F39D3B@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.de \
    --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).