From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/1995 Path: main.gmane.org!not-for-mail From: Uwe Koloska Newsgroups: gmane.comp.tex.context Subject: texexec: usage, bugs and more Date: Wed, 10 May 2000 15:36:48 +0200 Sender: owner-ntg-context@let.uu.nl Message-ID: <00051015593102.05828@leonore> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1035392790 4991 80.91.224.250 (23 Oct 2002 17:06:30 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:06:30 +0000 (UTC) Original-To: ntg-context@ntg.nl Xref: main.gmane.org gmane.comp.tex.context:1995 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:1995 Hello all, by answering "URLs in PDFTeX" the E-Mail grows and grows, so I decided to start a new thread on texexec and texshow: 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) Some times later: by starting texexec withouth the extension it produces the documentation: texexec --pdf --module texshow with a tex-file this works without cutting the extension off: texexec --pdf --module s-pre-01.tex Don't understand this behaviour, because in texexec RumModule() there is an if-statement asking wether filename plus extension (tex, mp, pl, pm) and only then processing it. Why does this work with ".tex" and not ".pl"? Isn't it better to test for the pure filename too? 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 ... texshow starts with a shebang line. This line shows up in the typeset documentation on two mostly empty pages before the titlepage ... Is it possible to change the output language while processing a module to say german? (My dutch is rather basic, to say the least) 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. Is the information used for texshow consistent with the newest commands? Uwe P.S.: While playing with texshow I noticed an error in the german frontend (besides that texshow is rather slow): the command "\about" is translated "\euber". I think this has to be "\ueber". -- mailto:koloska@rcs.urz.tu-dresden.de http://rcswww.urz.tu-dresden.de/~koloska/ -- -- right now the web page is in german only but this will change as time goes by ;-)