ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: texexec: usage, bugs and more
Date: Thu, 11 May 2000 01:01:31 +0200	[thread overview]
Message-ID: <3.0.6.32.20000511010131.008fc510@pop.wxs.nl> (raw)
In-Reply-To: <00051015593102.05828@leonore>

At 03:36 PM 5/10/2000 +0200, Uwe Koloska wrote:

>I have found texshow.pl that uses the tws-files directly (or generates them
>from the source ???).   To understand what's going on, I tried to typeset
>texshow.pl but
>    texexec --pdf --module texshow.pl
>did nothing ...  (no errors and no useful information with --verbose)

texexec --pdf --modu texshow 

(texexec sorts out the suffix itself)

Did you get texshow running? You need to install perl/tk, using the perl
module manager (windows) or your linux install. [btw, active state does a
pretty good job on perl updating].   

>Why does this work with ".tex" and not ".pl"?
>Isn't it better to test for the pure filename too?

This has to do with the fact that tex is natural for context and the others
are kind of special and need dedicated pretty printing routines. Also, I
needed it -) then. Some day I'll make a more clever sub.  

>The next action in texexec is to call RunPerlScript with
>    "--documents $FileName.pl $FileName.pm $FileName.mp $FileName.tex"
>maybe there only has to be the actual filename and not the other zombies. 
>I don't understand this to the ground, but ...

When I clean up the perl scripts I'll have a look. In the mean time, you
may make me a list of todo's, based on this discussion. Maybe others have
wishes too.   

>texshow starts with a shebang line.  This line shows up in the typeset
>documentation on two mostly empty pages before the titlepage ...

Yes. I still have to filter that one out. 

>Is it possible to change the output language while processing a module to
>say german?  (My dutch is rather basic, to say the least)

I still have to make these files international. Actually making these
public was against my principle of only making documented stuff public.
They used to be at the private task force page.  

>And is there a possibility to make interactive coloured module
>documentations?  With an index of the defined commands, colour instead
>of greyscale and a screen layout -- because most of the docu will be shown
>on screen for information purposes.

--mode=color

>Is the information used for texshow consistent with the newest commands?

Probably a bit out of date but not that old. [The new commands are
undocumented anyway]. 

>P.S.: While playing with texshow I noticed an error in the german
>  frontend (besides that texshow is rather slow):

Hm. Somehow tk is slower on linux than on windows. Maybe a memory problem. 

>  the command "\about" is translated "\euber".
>  I think this has to be "\ueber".

Ok. Changed. 

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.nl
-----------------------------------------------------------------


  reply	other threads:[~2000-05-10 23:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-10 13:36 Uwe Koloska
2000-05-10 23:01 ` Hans Hagen [this message]
2000-05-11  9:21   ` Taco Hoekwater

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=3.0.6.32.20000511010131.008fc510@pop.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).