20021022 pretest

2002-10-22 Thread Thomas Esser
Hi,

I just have uploaded a new teTeX-beta release which will soon appear on ctan, e.g.
  ftp://ftp.dante.de/tex-archive/systems/unix/teTeX-beta/teTeX-src-beta-20021022.tar.gz
  
ftp://ftp.dante.de/tex-archive/systems/unix/teTeX-beta/teTeX-texmf-beta-20021022.tar.gz
  
ftp://ftp.dante.de/tex-archive/systems/unix/teTeX-beta/teTeX-texmfsrc-beta-20021022.tar.gz
or
  ftp://cam.ctan.org/tex-archive/systems/unix/teTeX-beta/teTeX-src-beta-20021022.tar.gz
  
ftp://cam.ctan.org/tex-archive/systems/unix/teTeX-beta/teTeX-texmf-beta-20021022.tar.gz
  
ftp://cam.ctan.org/tex-archive/systems/unix/teTeX-beta/teTeX-texmfsrc-beta-20021022.tar.gz

This release contains the just released web2c-7.3.9 and I quote from
Olaf Weber's announcement about it:

I've put web2c 7.3.9 sources up on tug.org in ~ftp/tex.  Thus they'll
appear on CTAN in due course.

The sources contain preliminary versions of pdftex and omega.  Omega
has been hacked to use a different extension for its format files:
 .oft instead of .fmt, as the latter clashes with TeX's default.  I'd
much prefer to use .ofmt, but am not convinced that would be a good
idea, as truncating that extension gives .ofm, which is already
in use.  On the other hand, feel free to convince me otherwise.

These sources are especially meant to allow Thomas and Fabrice and
me to sync up with each other, and may be of limited interest to
anyone else (though they should be fully functional).  Expect this
release to be superceded "soon".

As always, I'd be glad to hear reports about successful builds (especially
if you use non-GNU compilers / tools).

The ChangeLog entries:
* merge with web2c-7.3.9
* texconfig: sometimes, we don't need tcdialog...
* clean up ranlib stuff / remove library before recreating it
* fix typo in texconfig
* add support files for win32

texmf tarball:
* update custom-bib
* update ccaption

Thomas



Re: texi2pdf

2002-10-22 Thread Thomas Esser
> Well, I've been trying to create PDF from a .texi document where makeinfo and 
> texi2html work fine.  But, texi2pdf always fails.  I'm attaching the document 
> which is part of the emacs package ESS as an example.  Any help would be 
> appreciated.  Thanks.

That seems to be an invalid texinfo source file. texi2dvi does not run,
either.

The documentation contained in
  ftp://ftp.stat.math.ethz.ch/Software/emacs/ESS/ess-5.1.20.tar.gz
works fine with texi2pdf:
  cd ess-5.1.20/doc
  texi2pdf readme.texi
  texi2pdf ess.texi 

Thomas



Re: texi2pdf

2002-10-22 Thread Rodney Sparapani
Thomas:

Well, I've been trying to create PDF from a .texi document where makeinfo and 
texi2html work fine.  But, texi2pdf always fails.  I'm attaching the document 
which is part of the emacs package ESS as an example.  Any help would be 
appreciated.  Thanks.

Rodney Sparapani  Medical College of Wisconsin
Sr. Biostatistician   Patient Care & Outcomes Research
[EMAIL PROTECTED]  http://www.mcw.edu/pcor
Was 'Name That Tune' rigged?  WWLD -- What Would Lombardi Do


ESS[SAS] was designed for use with SAS.  It is descended from emacs 
macros developed by John Sall for editing SAS programs and SAS-mode by 
Tom Cook.  Those editing features and new advanced features are part of 
ESS[SAS].  The user interface of ESS[SAS] has similarities with ESS[S]
and the SAS Display Manager.  By emacs, we mean either GNU Emacs from 
the Free Software Foundation or XEmacs from the XEmacs Project.

@comment  node-name,  next,  previous,  up
@node ESS(SAS)--Design philosophy, ESS(SAS)--Editing files, Help for SAS, Help for SAS
@section ESS[SAS]--Design philosophy

ESS[SAS] was designed to aid the user in writing and maintaining
SAS programs, such as myfile.sas.  Both interactive and batch submission
of SAS programs is supported.   

ESS[SAS] was written with two primary goals.

1. The emacs text editor provides a powerful and flexible development environment
for programming languages.  These features are a boon to all programmers and,
with the help of ESS[SAS], to SAS users as well.

2. Although, a departure from SAS Display Manager, ESS[SAS] provides similar
key definitions to give novice ESS[SAS] users a head start.  Also, inconvenient
SAS Display Manager features, like remote submission and syntax highlighting,
are provided transparently; appealing to advanced ESS[SAS] users.

@c Rodney:  I didn't have these goals in mind exactly.  Above, I try to give
@c a coherent rationale for getting involved.
@c
@c 1. Using the emacs environment is desirable for users accessing a remote
@c computer via a network or dial-up who can not use the SAS Display Manager.
@c 
@c 2. Using the emacs environment is desirable for local users as well due to the
@c inherent efficiency of using the same, superior interface all of the time.

@comment  node-name,  next,  previous,  up
@node ESS(SAS)--Editing files, iESS(SAS)--Interactive SAS processes, ESS(SAS)--Design 
philosophy, Help for SAS
@section ESS[SAS]--Editing files

ESS[SAS] is the mode for editing SAS language files.  This mode handles:

@display
- proper indenting, generated by both [Tab] and [Return].
- color and font choices based on syntax.
- ability to send the contents of an entire buffer, a highlighted region,
  or a single line to an interactive SAS process.
- ability to switch between processes which would be the target of the
  buffer (for the above).
- ability to save and submit the file you are working on as a batch SAS
  process with a single keypress and to continue editing while it is runs
  in the background.
- capability of killing the batch SAS process through the shell buffer or
  allow the SAS process to keep on running after you exit emacs.
- single keypress navigation of .sas, .log and .lst files (.log and .lst
  files are automatically refreshed with each keypress).
@end display

ESS[SAS] is automatically turned on when editing a file with a .sas 
suffix (or other extension, if specified via auto-mode-alist).  The function
keys can be enabled to use the same function keys that
the SAS Display Manager does.  The interactive capabilities of ESS require you 
to start an inferior SAS process with M-x SAS
(@xref{iESS(SAS)--Interactive SAS processes}.)

At this writing, the indenting and syntax highlighting are generally 
correct.  Known issues:  for multiple line * or %* comments, only the first 
line is highlighted; for .log files, only the first line of a NOTE:, WARNING: 
or ERROR: message is highlighted; unmatched single/double quotes in CARDS 
data lines are NOT ignored; in a DO ... TO or a DO ... TO ... BY statement,
TOs are not highlighted (and neither is BY).

@comment  node-name,  next,  previous,  up
@node  iESS(SAS)--Interactive SAS processes, ESS(SAS)--Batch SAS processes, 
ESS(SAS)--Editing files, Help for SAS
@section iESS[SAS]--Interactive SAS processes

iESS (inferior ESS) is the method for interfacing with interactive
statistical processes (programs).  iESS[SAS] is what is needed for
interactive SAS programming.  iESS[SAS] works best
with the following settings for SAS command-line options 
(the default of inferior-SAS-args):

@example
-stdio -linesize 80 -noovp -nosyntaxcheck
@end example

@display
-stdio  required to make the redirection of stdio work
-linesize 80keeps output lines from folding on standard terminals
-noovp  prevents error messages from printing 3 times
-nosyntaxcheck  permits recovery after syntax errors
@end display

To start up iESS[SAS] mode, use:
@example
   M-x SAS
@end example

Th

Re: texconfig from beta-20021017 does not run with system dialog utility

2002-10-22 Thread Thomas Esser
> +if test -n "$DIALOG_PROG"; then
> +  dialogok=0
> +else
> +  check_for_binary tcdialog >/dev/null
> +  dialogok=$?
> +fi

I just have fixed it by the following (somewhat more compact):

  check_for_binary tcdialog >/dev/null || test -n "$DIALOG_PROG"
  dialogok=$?

Thanks for reporting that and the suggested fix.

Thomas



Re: texi2pdf

2002-10-22 Thread Thomas Esser
> Hi.  I've been using teTeX for a couple of years and I love it.  However,
> texi2pdf seems to be broken in every version that I have tried including
> 10/13.

Can you please give some more information on this? I just have tried
  cd bison-1.75/doc
  texi2pdf bison.texinfo
and it worked quite nicely.

> Am I in the right place to discuss this problem?  

Yes, you are welcome to report such kind of things here.

Thomas



texconfig from beta-20021017 does not run with system dialog utility

2002-10-22 Thread Michail Vidiassov
Dear Thomas,
if teTeX is compiled without dialog, system dialog is not used
when texconfig is run without arguments.
When checking if it is OK to use dialog,
texconfig checks for tcdialog utility only.
The result of find_dialogtype is ignored.
Thus if tcdialog was not compiled the check fails and argument
"help" is assumed.
A patch fixing the problem follows.
  Sincerely, Michail
--- texconfig.orig  Mon Oct 21 15:10:52 2002
+++ texconfig   Mon Oct 21 16:33:28 2002
@@ -1864,8 +1864,12 @@
 EDIT=${VISUAL-${EDITOR-$std_editor}}
 PAGER=${PAGER-$std_pager}

-check_for_binary tcdialog >/dev/null
-dialogok=$?
+if test -n "$DIALOG_PROG"; then
+  dialogok=0
+else
+  check_for_binary tcdialog >/dev/null
+  dialogok=$?
+fi

 # we have called some shellfunctions, so for HP-UX's shell, we need
 # to set the positional parameters this again:



texi2pdf

2002-10-22 Thread Rodney Sparapani
Hi.  I've been using teTeX for a couple of years and I love it.  However, 
texi2pdf seems to be broken in every version that I have tried including 10/13.  
Am I in the right place to discuss this problem?  

Rodney Sparapani  Medical College of Wisconsin
Sr. Biostatistician   Patient Care & Outcomes Research
[EMAIL PROTECTED]  http://www.mcw.edu/pcor
Was 'Name That Tune' rigged?  WWLD -- What Would Lombardi Do