TeXshow

TeXshow

[Giuseppe Bilotta]

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]
2) is there a way to call TeXShow from the command line in such a way
that it reuses exisisting windows (if present)?
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.

Giuseppe Bilotta

[got rid of my signature because of possible
 misinterpretation of the mailing list]

Re: TeXshow

[Taco Hoekwater]

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

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 
and english. While writing modules, I want the module to work in 
every language, so I quite often need the internal name of the command 
instead of the interface specific one. Example: \blank is internally 
defined as \blanko (dutch), but \setupbodyfont is defined as 
\setupbodyfont (english).

> 2) is there a way to call TeXShow from the command line in such a way
> that it reuses exisisting windows (if present)?

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

> 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 ;)

-- 
groeten,

Taco

Re: TeXshow

[Hans Hagen]

[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]

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

[-- Attachment #2: setupd.tex --]
[-- Type: text/plain, Size: 5188 bytes --]

%D \module
%D   [       file=setupa,
%D        version=1998.07.20,
%D          title=\CONTEXT\ Setup Definitions,
%D       subtitle=Help Generation,
%D         author=Hans Hagen,
%D           date=\currentdate,
%D      copyright={PRAGMA / Hans Hagen \& Ton Otten}]
%C
%C This module is part of the \CONTEXT\ macro||package and is
%C therefore copyrighted by \PRAGMA. See mreadme.pdf for 
%C details. 

\let\wait\relax

\input setupa

\unprotect
\f
% keys 

\def\copymessage#1#2#3%
  {\dogetmessage{setup}{#3}\edef#1{#2\currentmessagetext}}

\copymessage \c!command!        *      {command}
\copymessage \c!dimension!      *      {dimension}
\copymessage \c!filename!       *      {file}
\copymessage \c!identifier!     *      {name}
\copymessage \c!character!      *      {character}
\copymessage \c!marker!         *      {mark}
\copymessage \c!number!         *      {number}
\copymessage \c!reference!      *      {reference}
\copymessage \c!plural!         *      {plural}
\copymessage \c!singular!       *      {singular}
\copymessage \c!text!           *      {text}
\copymessage \c!formula!        *      {formula}
\copymessage \c!font!           *      {file}
\copymessage \c!matrix!         *      {matrix}
\copymessage \c!list!           *      {list}
\copymessage \c!section!        *      {section}
\copymessage \c!noargument!     \empty {command}
\copymessage \c!oneargument!    \empty {command}
\copymessage \c!twoarguments!   \empty {command}
\copymessage \c!threearguments! \empty {command}

\edef\c!noargument!    {*\@EA\string\csname\c!noargument!    \endcsname}
\edef\c!oneargument!   {*\@EA\string\csname\c!oneargument!   \endcsname\string#1}
\edef\c!twoarguments!  {*\@EA\string\csname\c!twoarguments!  \endcsname\string#1\string#2}
\edef\c!threearguments!{*\@EA\string\csname\c!threearguments!\endcsname\string#1\string#2\string#3}

\def\subsetup#1{/#1}
\f
\beginTEX 

\def\getinterfaceconstant#1%
  {\ifinterfacetranslation
     \ifx\csname\x!prefix!#1\endcsname\relax
       #1%
     \else
       \csname\x!prefix!#1\endcsname
     \fi
   \else
     #1%
   \fi}

\def\getinterfacevariable#1%
  {\ifinterfacetranslation
     \ifx\csname\y!prefix!#1\endcsname\relax
       #1%
     \else
       \csname\y!prefix!#1\endcsname
     \fi
   \else
     #1%
   \fi}

\endTEX

\beginETEX \ifcsname

\def\getinterfaceconstant#1%
  {\ifinterfacetranslation
     \ifcsname\x!prefix!#1\endcsname
       \csname\x!prefix!#1\endcsname
     \else
       #1%
     \fi
   \else
     #1%
   \fi}

\def\getinterfacevariable#1%
  {\ifinterfacetranslation
     \ifcsname\y!prefix!#1\endcsname
       \csname\y!prefix!#1\endcsname
     \else
       #1%
     \fi
   \else
     #1%
   \fi}

\endETEX
\f
\def\c!repeat! {repeat/} % {n*}
\def\c!arg!    {arg/}    % {{...}:}
\def\c!args!   {args/}   % {{..,...,..}:}
\def\c!dis!    {dis/}    % {$$...$$:}
\def\c!idx!    {idx/}    % {{...}:}
\def\c!idxs!   {idxs/}   % {{..+...+..}:}
\def\c!mat!    {mat/}    % {$...$:}
\def\c!nop!    {nop/}    % {...:}            
\def\c!fil!    {fil/}    % {...:}            
\def\c!pos!    {pos/}    % {(...):}
\def\c!poss!   {poss/}   % {(...,...):}
\def\c!sep!    {sep/}    % {\string\\:}
\def\c!ref!    {ref/}    % {[ref]:}
\def\c!refs!   {refs/}   % {[ref,..]:}
\def\c!val!    {val/}    % {[...]:}
\def\c!vals!   {vals/}   % {[..,...,..]:}
\def\c!var!    {var/}    % {[..=..]:} 
\def\c!vars!   {vars/}   % {[..,..=..,..]:}
\def\c!cmd!    {cmd/}    % {\string\xxx:}
\def\c!dest!   {dest/}   % {[..ref]:}
\def\c!dests!  {dests/}  % {[..,..refs,..]:}
\def\c!trip!   {trip/}   % {[x:y:z=]:}
\def\c!trips!  {trips/}  % {[x:y:z=,..]:}
\def\c!wrd!    {wrd/}    % {{...}:}
\def\c!wrds!   {wrds/}   % {{.. ... ..}:}
\def\c!par!    {par/}    % {\string\par:}
\def\c!stp!    {stp/}    % {stop:}
\def\c!tex!    {tex/}    % {\string\cs:}

\def\c!or!     {}        % tzt or 

\def\c!opt!    {}        %
\def\c!optint! {}        %
\def\c!alwint! {}        %

% wrapper 

\def\startsetupfile
  {\immediate\openout\scratchwrite=cont-\currentlanguage.tws }

\def\stopsetupfile
  {\immediate\closeout\scratchwrite}

\let\documenteduntilhere\relax

\long\def\startsetup#1\stopsetup % the :'s serve as breakpoints
  {\bgroup
   \long\def\command         [##1]%
     {\immediate\write\scratchwrite{com:##1:}}%
   \long\def\type            [##1]%
     {\immediate\write\scratchwrite{typ:##1:}}%
   \long\def\value           [##1]##2[##3]%
     {\immediate\write\scratchwrite{val:##1:##3:}}%
   \long\def\variable        [##1]##2[##3]##4[##5]%
     {\convertsetupdata{##5}\ascii
      \edef\temp{\getinterfaceconstant{##1}}%
      \immediate\write\scratchwrite{var:\temp:##3:\ascii:}}%
   \long\def\inheritvalues   [##1]##2[##3]%
     {\immediate\write\scratchwrite{ivl:##1:##3:}}%
   \long\def\inheritvariables[##1]##2[##3]%
     {\convertsetupdata{##3}\ascii
      \immediate\write\scratchwrite{ivr:##1:\ascii:}}%
   \immediate\write\scratchwrite{startsetup}%
   #1%
   \immediate\write\scratchwrite{stopsetup}%
   \immediate\write\scratchwrite{}%
   \egroup}

\let\stopsetup\relax

\def\convertsetupdata#1#2% only accept #1=\v!whatever
  {\doifsystemconstantelse{#1}{\edef#2{#1}}{\let#2\empty}}

\input setupb 

\protect

\end

[-- Attachment #3: Type: text/plain, Size: 370 bytes --]

-------------------------------------------------------------------------
                                  Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: TeXshow

[Giuseppe Bilotta]

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

Done. Works.

Well, except that whatever interface I choose I always get
cont-en.tws (even if the contents are the correct ones; I just need
to rename it to cont-[interface].tws).

Btw, playing with TeXShow I found a bug related to commands having
the same names in all languages: the first language with that command
is selected! An example:

\mar is \mar in de, nl, en, it but \okr in cz

If I'm browsing the italian interface and select \mar I get the
correct description; but if I then want to change interface
(e.g. to know how "\mar" is called in english) I end up
in the german interface, which I don't want.

Also, if I run "texshow mar it" I end up in cont-de again
(I assume that the same routine is causing the error)

And one more: I created cont-it.tws, it works fine, but it still says
"command", "dimension" etc instead of the italian forms; which file should
I localize? [and btw, Hans, did you receive my mail with the localizations
bug fixes for italian?]

Giuseppe Bilotta

Using Microsoft products is like 
having sex without condoms---but
much less pleasurable

Re: TeXshow

[Ed L Cashin]

Hans Hagen <pragma@wxs.nl> writes:

> At 09:01 AM 2/8/01 +0100, Taco Hoekwater wrote:
> >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] 

I'm curious: what do you mean by the list of patches?  

-- 
--Ed Cashin                    integrit file verification system
  ecashin@coe.uga.edu          http://integrit.sourceforge.net/

Re: TeXshow

[Hans Hagen]

At 09:29 AM 2/8/01 -0500, Ed L Cashin wrote:
>Hans Hagen <pragma@wxs.nl> writes:
>
>> At 09:01 AM 2/8/01 +0100, Taco Hoekwater wrote:
>> >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] 
>
>I'm curious: what do you mean by the list of patches?  

taco an tobias send me some mails about texshow with suggestions (which are
still sitting somewhere in the 300 todo mailbox). 

Hans
-------------------------------------------------------------------------
                                  Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: TeXshow

[Hans Hagen]

At 03:11 PM 2/7/01 +0100, 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]
>2) is there a way to call TeXShow from the command line in such a way
>that it reuses exisisting windows (if present)?
>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.

I will pick up the interface documentation thread as soon as i have xml
support stable, which is needed to process the multilingual mixed interface
documentaion. 

Hans  
-------------------------------------------------------------------------
                                  Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: TeXshow

[Giuseppe Bilotta]

> I will pick up the interface documentation thread as soon as i have xml
> support stable, which is needed to process the multilingual mixed interface
> documentaion. 

By the way, what about ConTeXt-documentation? Dead? Or simply
no more news on that front, still?

Giuseppe Bilotta

Using Microsoft products is like 
having sex without condoms---but
much less pleasurable

Re: TeXshow / status context

[Hans Hagen]

At 01:45 PM 2/8/01 +0100, Giuseppe Bilotta wrote:
>
>> I will pick up the interface documentation thread as soon as i have xml
>> support stable, which is needed to process the multilingual mixed interface
>> documentaion. 
>
>By the way, what about ConTeXt-documentation? Dead? Or simply
>no more news on that front, still?

Not dead. Ton is finishing the update of the beginners manual (after that
it can be translated to other languages). Concerning interface
documentation, we want to do that in xml, so there i need some decent xml
support in the core first. Ths basics are already there, but as a testcase
i implement mathml, which in turn demands manuals and examples (halfway
done). [for those interested: i make the manual in good old tex code while
all math is entered as mathml, so one can mix tex and xml, and so far the
math comes out quite well].  

My rough schedule for the next couple of months is (goes in parallel with
some projects that need it): 

- basic xml support + mathml 
- named glyphs and unicode (needed for central european pdf, chinese and
omega farsi etc) 
- multiple otr support combined with dtp like column/float handling 
- additional font support

also on the todo list: 

- computer language typesetting (for bzyl) 
- more metafun 
- some styles 
- more documentation
- texwork cum suis  

Hans
-------------------------------------------------------------------------
                                  Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

TeXCalc

[Taco Hoekwater]

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

Hi all,

For those who want to play with a little new program,
here is TeXCalc, version 0.1.

TeXCalc is a program that can convert and do calculus with TeX units. 

You know the  "how much is (21cm-28pc)/2" problems you have when you
design a new layout? TeXCalc can (or should) solve these problems!

All of TeX's normal units are supported, conversion is quite accurate
(most calculations use scaled points), and input is fairly fast.
The expression can be entered from the keyboard as "21c28p-2/", and
you need only one keystroke to get the result in a different unit
(like alt-t for points)

Let me know what you think.

Greetings, Taco

[-- Attachment #2: texcalc.zip --]
[-- Type: application/x-zip-compressed, Size: 4535 bytes --]

Re: TeXCalc

[Frans Goddijn]

Hi Taco,

how should the program be used? It looks like a PERL script so I renamed it
rexcalc.pl and on the command prompt I said "perl texcalc.pl" but then perl
says it misses some "tk" stuff somewheres.

Groet!

Frans

> For those who want to play with a little new program,
> here is TeXCalc, version 0.1.

Re: TeXCalc

[Taco Hoekwater]

Hi Frans,

The program needs perlTk, a set of Perl extension modules that allows 
one to define windows with buttons, dropdown-lists etc. It's the same
extension set that texshow uses, so I assumed most people on the list
would have it installed. :)

Installation depends on your perl & operating system. 

I'm guessing you are using ActiveState perl, so you probably 
need to execute this command in a shell:

    ppm install Tk

(you have to be online for this to work)

Groetjes, Taco

> how should the program be used? It looks like a PERL script so I renamed it
> rexcalc.pl and on the command prompt I said "perl texcalc.pl" but then perl
> says it misses some "tk" stuff somewheres.

Re: TeXCalc

[Frans Goddijn]

I suppose this is something for gurus...

I don't know what "execute in a shell" is but I did it on a command line and
got the response that ppm is not a filename or something like that.. I am
online, so that's not it.

Okay, I'll just wait untill it's all much simpler, so don't worry and forget
it.

> need to execute this command in a shell:
>
>     ppm install Tk