At 09:01 AM 2/8/01 +0100, Taco Hoekwater wrote:
>Giuseppe Bilotta wrote:
>> 
>> Well, I find TeXShow a good source of information for quick references;
>> I'd like to point a couple of facts, though:
>> 
>> 1) the tws files seem a little outdated to me; maybe they need to be
>> regenerated ... and generally speaking, how do you create the tws files
>> relative to formats not already provided? [esp. the experimental ones]
>
>I think Hans has a perl script that creates the tws files from the
>same setup files that define the commands in the manual (setupb & 
>mult-con/mult-com).

No. Just the undocumented crap file setup.d.tex (attached). Run it with 

  texexec --interface=.. setupd 

and you will get the file. When i have a 4.5 gig pentium 6 laptop, i will
start generating them automatically. 

>As a side note: I'd be very happy with a version that uses the
>internal macro names. ConTeXt internals are a mixture of dutch 

should be doable; i'll have a look at it when i start patching texshow (i
managed to get perl/tk working again so i will pick up that thread). 

>No. I'm not even sure Tk allows that kind of trickery.

i think that you're right; i also found out that there have been some
changes in font sizes, function key handling and alike, sigh. 

>> 3) the kind of information displayed by TeXShow is extremely compat---
>> I would dare to say too compact: in some cases it's difficult to say
>> which parameter does what---ok, TeXShow is intended for quick-reference,
>> so the user should already know what does what, but still ... I prefere
>> browsing the commands using it, rather than the interactive [or printable]
>> reference manual.
>
>Agree. Some sort of comment field within the \startsetup \stopsetup
>would be
>very helpful.
>
>TeXshow also has a number of speed issues ;)

I know -) and have the list of patches. [maybe i should start using texshow
myself; actually, texshow was written to be part of texwork, which i will
finish some day soon too] 

Hans