Re: could not find app-default file for xdvi
On Wed, Mar 05, 2003 at 11:59:18AM -0800, Chris Majewski wrote: > "make world", I get "could not find app-default file for xdvi". I You should have unpacked the texmf tarball in /cs/local/generic/lib/pkg/teTeX-1.0.0/share/texmf That should have given you (among others) the file /cs/local/generic/lib/pkg/teTeX-1.0.0/share/texmf/xdvi/XDvi. Did you do that? Thomas
teTeX-2.0.2: another texconfig fix
texconfig should no longer try to call "fmtutil --byfmt mfw". Doing
so gives
fmtutil: no info for format `mfw'
(but does not cause any harm).
The following patch fixes this.
Thomas
--- 2.0.2/texk/tetex/texconfig Sat Mar 1 10:13:18 2003
+++ texk/tetex/texconfigSat Mar 1 16:05:23 2003
@@ -443,7 +443,6 @@
{
echo "Running mf to create plain base ..."
fmtutil --byfmt mf
- fmtutil --byfmt mfw
echo "Done."; echo
}
Re: teTeX 2.0.2 problem
On Sat, Mar 01, 2003 at 12:41:26PM +0300, Dmitry Sivachenko wrote:
> There is also a file
> texmf/doc/help/Catalogue/entries/g-brief.html
> which was probably intended to be removed (I am not sure though).
No, that is ok. The Catalogue lists lots of packages. Not all of them
are available in teTeX.
Thomas
PS: I think that I have deleted your message before passing it to the
tetex list, so here your original message again:
===
Date: Sat, 1 Mar 2003 12:05:47 +0300
From: Dmitry Sivachenko <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: teTeX 2.0.2 problem
Hello!
The following patch is probably needed for teTeX 2.0.2 (2.0.1 was OK):
--- texconfig.orig Sat Mar 1 09:01:38 2003
+++ texconfig Sat Mar 1 08:59:34 2003
@@ -1791,7 +1791,7 @@
test -z "$TC_DFT_CONFIG_PS" && TC_DFT_CONFIG_PS=$TC_TEXMFMAIN/dvips/config/config.ps
: ${TC_DFT_DVIPDFM_CFG=`kpsewhich -progname=dvipdfm -format='other text files'
config`}
-test -z "$TC_DFT_DVIPDFM_CFG" && TC_DFT_DVIPDFM_CFG=$TC_TEXMFMAIN/dvipdfm/config
+test -z "$TC_DFT_DVIPDFM_CFG" &&
TC_DFT_DVIPDFM_CFG=$TC_TEXMFMAIN/dvipdfm/config/config
: ${TC_DFT_PDFTEX_CFG=`kpsewhich -progname=pdftex --format=tex pdftex.cfg`}
test -z "$TC_DFT_PDFTEX_CFG" &&
TC_DFT_PDFTEX_CFG=$TC_TEXMFMAIN/pdftex/config/pdftex.cfg
@@ -1820,7 +1820,7 @@
xdvi_app_dir=$TC_VARTEXMF/xdvi
xdvi_app_file=$xdvi_app_dir/XDvi
dvips_conf_dir=$TC_VARTEXMF/dvips/config
-dvipdfm_conf_dir=$TC_VARTEXMF/dvipdfm
+dvipdfm_conf_dir=$TC_VARTEXMF/dvipdfm/config
pdftex_conf_dir=$TC_VARTEXMF/pdftex/config
maketex_site_dir=$TC_VARTEXMF/web2c
maketex_site_file=$maketex_site_dir/mktex.cnf
ANN: teTeX-2.0.2
=== teTeX 2.0.2 === This is the announce of teTeX-2.0.2, a TeX distribution for UNIX compatible systems. === General disclaimer: === This is a bugfix release, with only a few changes. See the file ANNOUNCE-2.0 for more information. === Changes in this release: === The main change is the new pdftex which has a few important fixes. For details, please look at tetex-src-2.0.2/texk/web2c/pdftexdir/NEWS. ChangeLog entries: In the src tarball: * portability fix for texk/kpathsea/cnf.c * pdftex version 1.10b * add eomega support to fmtutil * ttf2afm: FontFamily patch by Siep Kroonenberg * update config.guess / config.sub * handle manpages for kpsepath / kpsexpand properly * fix two bugs in texdoctk * mktexmf fix for CJK fonts * adjust cxx-runtime-hack a little * add search paths for non"k"-xdvi to texmf.in * fix bug in texk/etc/autoconf/acspecific.m4 In the texmf tarball: * add doc/latex/styles/multiple-span.txt * move dvipdfm/* to dvipdfm/config * update ragged2e * support uppercase mathtime fonts via aliases * remove g-brief: it is not free software * update shadow.sty * add package mparhack and jurabib * listings package is back (license *is* ok!) * SIunits.cfg updated (only comments have changed in a minor way) * replace old README by new readme in doc/latex/pdfpages * added sihyph23.tex (Slovenian hyphenation patterns) === The files / installation === You can get teTeX-2.0.2 from the following server: ftp://cam.ctan.org/tex-archive/systems/unix/teTeX/2.0/distrib/ (UK) Other servers will follow shortly: ftp://dante.ctan.org/tex-archive/systems/unix/teTeX/2.0/distrib/ (GER) ftp://tug.ctan.org/tex-archive/systems/unix/teTeX/2.0/distrib/ (US) A full list of mirrors is available here: ftp://cam.ctan.org/tex-archive/CTAN.sites From these servers, you need the following files for teTeX-2.0: sources of the programs (required): ==> tetex-src-2.0.2.tar.gz support tree with fonts / macros (required): ==> tetex-texmf-2.0.2.tar.gz sources for parts of the texmf tarball (optional): ==> tetex-texmfsrc-2.0.2.tar.gz The installation instructions are included in the tetex-src-2.0.2.tar.gz archive as files INSTALL (complete instructions) and QuickInstall (short version). Thomas Esser, February 2003
Re: Building tetex on HP-UX 11.0
On Thu, Feb 27, 2003 at 06:14:43PM +0100, Miguel Covas O'Ryan wrote:
> Now, I have some problems. First of all, I've been unable to use gcc as
> ANSI compiler.
> configure complains about gcc being unable to generate executable files
> (I think the test is
> done with flags "-g -Aa +e -D_HPUX_SOURCE" which gives
> : missing '(' after predicate
> )
That should not happen. configure has:
case "$target" in
...
hp*hpux*)
if test "$CC" = "cc"; then
CFLAGS="$CFLAGS -Aa +e -D_HPUX_SOURCE"; export CFLAGS
AC_MSG_WARN(HP-UX's cc)
fi
;;
...
So, if you have gcc on your system, the unusual CFLAGS should not
be added.
> A bit dissapointed since my bad experiences with HP ANSI cc I've
> configured with HP cc as
> ANSI C compiler and gcc as C++ compiler (configure allows gcc to act as
> C++ compiler !!)
The GNU C++ compiler should be called as g++, I think.
> do background silent processing, not to edit or visualize anything. Can
> I skip someway that step?
Yes, two possibilities:
./configure --with-system-ncurses
or
./configure --without-dialog
> On the other hand I can try to fix hashmap.c which seems to be badly
> build by the cpp (ufff)
> machines? Can we act as repository for
> anyone wanting to install tetex on a HP-UX machine? We (as Bancoval)
> have modestly funded tex users group, but we would like to cooperate in
> a more active way...
As long as the relative structure (binaries vs. texmf tree) is
kept intact, the binaries can even be used by other people in other
directories. The usual rules apply, so if you have used non-standard
shared libraries (e.g. for X11 or some curses lib), other people will
need that, too.
Thomas
Re: Bug#182772: dvipdfm can't find ot1r.enc
On Fri, Feb 28, 2003 at 08:53:39AM +0900, Atsuhito Kohda wrote: > It seemed ot1*.enc (ot1.enc, ot1alt.enc, ot1r.enc) > were really missing. Nothing in (the original) teTeX refers to these files. Correct me if I am wrong. If something in debian refers to these files, debian should provide them. teTeX *has* encoding files for all text fonts of the CM set. They are extracted from the BSR type1 files and should be 100% correct. Just look at texmf/dvips/tetex/*.enc. Thomas
Re: mktex.cnf
On Thu, Feb 27, 2003 at 01:04:52PM +0900, Atsuhito Kohda wrote: > In teTeX 2.0.1, there are two mktex.cnf, one in tetex-src > and the other in tetex-texmf. > > Which one is a recommended mktex.cnf? The file in src is the original one by Olaf Weber. Everything is commented-out in it. It is not automatically installed. The one in texmf is what I'd like to use for the default configuration of teTeX. Thomas
Re: texdoctk 0.5.2 beta3
On Wed, Feb 26, 2003 at 03:12:32AM +0100, Reinhard Kotucha wrote: > Does it mean that the save button will be removed? Sorry, a misunderstanding. I had written "the saved settings are not (again) stored in $HOME/.texdocrc ." where I wanted to write "the saved settings are now (again) stored in $HOME/.texdocrc ." :-( > Of course both files can be in different texmf trees and should be > looked up independently. Ok, sure. E.g. a texdocrc.defaults in a local texmf tree makes sense. So, I have two independend kpsewhich calls now. Thomas
Re: kpathsea manpages
On Wed, Feb 26, 2003 at 09:26:57PM -0500, David R. Morrison wrote: > It looks to me like these were revised at some point, but the Makefile > wasn't updated quite right. The patch below seems to fix it. I prefer a different fix using symlinks. The files kpsepath.man and kpsexpand.man can be removed the the src dir, then. Thomas --- 2.0.1/tetex-src/texk/tetex/Makefile.in Sat Feb 15 18:57:16 2003 +++ tetex-src/texk/tetex/Makefile.inThu Feb 27 06:57:21 2003 @@ -10,7 +10,7 @@ SCRIPTS= dvi2fax ps2frag texconfig dvired pslatex texi2html allcm allneeded fontexport fontimport kpsetool mkfontdesc MakeTeXPK fontinst rubibtex rumakeindex fmtutil texdoc texlinks texexec texdoctk updmap PDFSCRIPTS=e2pall epstopdf texi2pdf thumbpdf -manpgs= allcm allec allneeded dvi2fax dvired e2pall epstopdf fontexport fontimport fontinst kpsepath kpsetool kpsexpand ps2frag pslatex rubibtex rumakeindex texconfig texdoc texexec texi2html texi2pdf texshow texutil thumbpdf texdoctk updmap +manpgs= allcm allec allneeded dvi2fax dvired e2pall epstopdf fontexport fontimport fontinst kpsetool ps2frag pslatex rubibtex rumakeindex texconfig texdoc texexec texi2html texi2pdf texshow texutil thumbpdf texdoctk updmap INFOFILES= latex.info latex.info-1 latex.info-2 latex.info-3 POOLFILES = etex-pl.pool pdfetex-pl.pool pdftex-pl.pool tex-pl.pool @@ -60,6 +59,8 @@ ln -s pdftex.$(manext) $(man1dir)/cont-nl.$(manext) ln -s pdftex.$(manext) $(man1dir)/cont-en.$(manext) ln -s mktexpk.$(manext) $(man1dir)/MakeTeXPK.$(manext) + ln -s kpsetool.$(manext) $(man1dir)/kpsepath.$(manext) + ln -s kpsetool.$(manext) $(man1dir)/kpsexpand.$(manext) test -r ./latex.info || cd $(srcdir) && for i in latex.info*; do \ $(INSTALL_DATA) $$i $(infodir)/$$i; done if $(SHELL) -c 'install-info --version' >/dev/null 2>&1; then \
Re: texdoctk 0.5.2 beta3
> The path searched by kpsewhich contains "." as its first element, so
> $sysrc points to a file "texdocrc.defaults" in the current working
> directory instaed of the real system file.
>
> This is not bad in general, but obviously the value of $sysrc is used
> to find the database file as well.
texdocrc.defaults is written to $HOME when the options are saved. This
is against Thomas R.'s intention and was introduced in TeX Live. I have
fixed this in beta4 (Thomas R. has written to me that he has no time
to work on texdoctk at the moment): the saved settings are not (again)
stored in $HOME/.texdocrc .
Maybe, an additional fix might be helpful:
- my $database="$datadir/texdoctk.dat";
+ my $database=`kpsewhich --progname=texdoctk --format=${qq}other text files${qq}
texdoctk.dat`;
This is to fix the situation where a locally installed older texdoctk
in a local texmf tree had a texdocrc.defaults but no texdoctk.dat in
the local tree (older versions of texdoctk have used different names
for the database files).
Comments on this change?
Thomas
Re: Which fonts are installed?
> I have a Linux box with mandrake 9.0, which ships tetex 1.07. > My problem is: how can I figure out which are all fonts which are > installed/usable ? For a start, I suggest that you read the files displayed with find `kpsewhich -expand-var='$TEXMFMAIN'`/doc \ -name Catalogue -prune -o -type f -print| grep font > I know there is a useful file called testfont.tex: its only drawback is > that it asks me for the font to be tested... I would like to tell him: > test all fonts! Well, you could start with generating a sample for each tfm file. Others have already pinted out that this does not catch all fonts, but it catches most of them. You could use something like this simple one-liner: find `kpsexpand '$TEXMFMAIN'`/fonts/tfm -name '*.tfm' -print | sed '[EMAIL PROTECTED]/@@; [EMAIL PROTECTED]@@' | xargs sh -c 'for i in "$@"; do (echo $i; echo \\sample\\bye) | tex testfont; mv testfont.dvi $i.dvi; echo $i.dvi; done' sh > Wouldn't it be nice if there were an utility for this? It would be nice to have a document wich lists the fonts and the relevant macro packages to access them Thomas
Re: europs.sty in 2.0(.1)
On Sat, Feb 22, 2003 at 11:04:38AM +0100, Giuseppe Ghibò wrote: > like isn't official euro symbol the \texteuro of textcomp.sty. IMHO the one > provided in font "eurosym" (feymr10) is enough to provide the euro symbol. teTeX-2.0 (and later) has eurosym.sty and the metrics and type1 files for the fonts (texmf/fonts/type1/public). > In this case maybe .tfm and europs.sty could be provided, but then it ... > The europs.sty license is this: %% File eurofont.sty %% copyright Rowland McDonnell 1998 %% email [EMAIL PROTECTED] %%\This file is part of the eurofont distribution. You can distribute it %% freely provided that you include the rest of the eurofont distribution %% with this file and make no more than a nominal charge to cover the %% costs of distributing it. So, the eurofont package is not free software. Thomas
Re: g-brief is non-free?
> %% You are NOT ALLOWED to distribute this file alone. You are NOT ALLOWED > %% to take money for the distribution or use of this file (or a changed > %% version) except for a nominal charge for copying etc. > > especially the last sentence is very problematic. Sure, that makes it unfree. > It is very sad to see some authors of LaTeX packages > put possibly unnecessary or unintentinal phrase > to their license. Yes. g-brief is gone now. Anybody interested in getting it back into teTeX might try to contact the author and ask him to make it free software. Thomas
Re: europs.sty in 2.0(.1)
> is it possible that europs is missing in teTeX 2.0(.1)? g-brief 3.0 > seems to rely on it. teTeX has eurosym and marvosym to support the Euro symbol. I am not sure ig this "dependency" of g-brief to europs is intentional or a bug. IMHO, g-brief should be happy with just one implementation for the Euro symbol. As other have guessed: I don't like that europs approach as the type1 files cannot be distributed with teTeX. Thomas
Re: kpesewhich & BeOS (long)
> I am trying to use tetex in BeOS and have managed to compile it making > some small changes that I will post later for reference. ... > fmtutil: config file `fmtutil.cnf' not found. kpathsea translates search path read from texmf.cnf on unix-like systems by replacing ";" -> ":". The unix-defection can be found in texk/kpathsea/cnf.c: /* gcc -ansi doesn't predefine `unix', since ANSI forbids it. And AIX generally doesn't predefine unix, who knows why. HP-UX is, of course, also different. Apple's MacOsX is also unix-like. */ #ifndef unix #if defined (__unix__) || defined (_AIX) || defined (_HPUX_SOURCE) #define unix #elif defined (__APPLE__) && defined (__MACH__) #define unix #elif defined (__NetBSD__) #define unix #endif #endif I think that your system needs to be added with an appropriate detection. Note, that the same detection is implemented in texk/dviljk/config.h. To explain why some of your searches work, while others don't: kpathsea has one search path that it never takes from texmf.cnf and that's the search path for texmf.cnf itself. If you say kpsewhich fmtutil.cnf then kpathsea does not search in the "web2c files" search path, but in the path for texmf.cnf (.cnf format). The same happens if you say kpsewhich --format='web2c\ files' fmtutil.cnf or kpsewhich --format='blubber kpathsea does not know' fmtutil.cnf The "web2c files" format (if you don't cripple it by misspelling it with a backslash), however is read via texmf.cnf and there, you are hit by the missing ";" -> ":" translation. Argh... If only these #ifdef's could be replaced by a proper autoconf check... Thomas
Re: teTeX-2.0.1 on SGI Irix 6.5 problem linking mfw, oxdvik, xdvik
> With 2.0.1, configure is setting "X_LIBS" to "-L/usr/lib", which causes Irix to
> try to link again o32 libraries:
I guess that's because I have applied a patch from Albert Chin
incorrectly. A fix for my incorrect patch is appended to this mail.
Thomas
diff -ru /t/2.0.1/tetex-src/ChangeLog /t/src/tetex-src/ChangeLog
--- /t/2.0.1/tetex-src/ChangeLogSun Feb 16 02:25:13 2003
+++ /t/src/tetex-src/ChangeLog Tue Feb 18 05:11:42 2003
@@ -1,3 +1,8 @@
+Tue Feb 18 05:11:38 CET 2003
+ * fix bug in texk/etc/autoconf/acspecific.m4
+
+= teTeX-2.0.1 =
+
Sun Feb 16 00:00:20 CET 2003
* fix a bug that I introduced in dvipdfm (in my attempt to
stop using the return value of sprintf)
diff -ru /t/2.0.1/tetex-src/configure /t/src/tetex-src/configure
--- /t/2.0.1/tetex-src/configureTue Feb 4 23:54:16 2003
+++ /t/src/tetex-src/configure Tue Feb 18 05:12:51 2003
@@ -1745,7 +1745,7 @@
#include "confdefs.h"
#include
int main() {
-${x_direct_test_function}()
+${x_direct_test_function}(1)
; return 0; }
EOF
if { (eval echo configure:1752: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test
-s conftest${ac_exeext}; then
diff -ru /t/2.0.1/tetex-src/libs/t1lib/configure /t/src/tetex-src/libs/t1lib/configure
--- /t/2.0.1/tetex-src/libs/t1lib/configure Tue Feb 4 23:54:19 2003
+++ /t/src/tetex-src/libs/t1lib/configure Tue Feb 18 05:12:53 2003
@@ -1160,7 +1160,7 @@
#include "confdefs.h"
#include
int main() {
-${x_direct_test_function}()
+${x_direct_test_function}(1)
; return 0; }
EOF
if { (eval echo configure:1167: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test
-s conftest${ac_exeext}; then
diff -ru /t/2.0.1/tetex-src/texk/etc/autoconf/acspecific.m4
/t/src/tetex-src/texk/etc/autoconf/acspecific.m4
--- /t/2.0.1/tetex-src/texk/etc/autoconf/acspecific.m4 Tue Feb 4 23:53:55 2003
+++ /t/src/tetex-src/texk/etc/autoconf/acspecific.m4Tue Feb 18 05:11:07 2003
@@ -2519,7 +2519,7 @@
# Don't add to $LIBS permanently.
ac_save_LIBS="$LIBS"
LIBS="-l$x_direct_test_library $LIBS"
-AC_TRY_LINK([#include ], [${x_direct_test_function}()],
+AC_TRY_LINK([#include ], [${x_direct_test_function}(1)],
[LIBS="$ac_save_LIBS"
# We can link X programs with no special library path.
ac_x_libraries=],
diff -ru /t/2.0.1/tetex-src/texk/web2c/configure /t/src/tetex-src/texk/web2c/configure
--- /t/2.0.1/tetex-src/texk/web2c/configure Sat Feb 15 22:35:03 2003
+++ /t/src/tetex-src/texk/web2c/configure Tue Feb 18 05:12:53 2003
@@ -3353,7 +3353,7 @@
#include "confdefs.h"
#include
int main() {
-${x_direct_test_function}()
+${x_direct_test_function}(1)
; return 0; }
EOF
if { (eval echo configure:3360: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test
-s conftest${ac_exeext}; then
diff -ru /t/2.0.1/tetex-src/texk/xdvik/configure /t/src/tetex-src/texk/xdvik/configure
--- /t/2.0.1/tetex-src/texk/xdvik/configure Tue Feb 4 23:54:18 2003
+++ /t/src/tetex-src/texk/xdvik/configure Tue Feb 18 05:12:53 2003
@@ -2360,7 +2360,7 @@
#include "confdefs.h"
#include
int main() {
-${x_direct_test_function}()
+${x_direct_test_function}(1)
; return 0; }
EOF
if { (eval echo configure:2367: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test
-s conftest${ac_exeext}; then
teTeX-2.0.1
===
teTeX 2.0.1
===
This is the announce of teTeX-2.0.1, a TeX distribution for UNIX
compatible systems.
===
General disclaimer:
===
This is a bugfix release, with only a few changes. See the file
ANNOUNCE-2.0 for more information.
===
Changes in this release:
===
In the src tarball:
* fix a bug that I introduced in dvipdfm (in my attempt to
stop using the return value of sprintf)
* fix a configure bug in texinfo
* add dvipdft script to dvipdfm
* \usepackage{palatcm} for TETEXDOC
* fix a bug in texdoctk related to calling a web browser
* texk/kpathsea/Makefile.in: use % instead of @ (AFS fix)
* "fmutuil --enablefmt" no longer returns error code if format is
already enabled
* mv tcdialog support files from texmf to src tarball
* remove DO_TEXLINKS variable from texconfig
* update texk/etc/texinfo.tex
* make usre that mf-nowin works without mf
* additions to INSTALL by Harald Harders (thanks!)
* texinfo update: 4.4 + bugfix -> 4.5
* fix minor typo in texconfig
* use "tex --parse-first-line" in makempx.in
* small fixes to texk/etc/autoconf/acspecific.m4
* fix updmap for CM-Super fonts
* portability fix for libs/t1lib/t1lib.ac
* small updates to texk/tetex/doc
In the texmf tarball:
* was package added
* update Catalogue
* update tex/texinfo/texinfo.tex
* mv tcdialog support files from texmf to src tarball
* add afm files for tx/pxfonts
* update endnotes.sty
* update tocbibind, wrapfig, uktug-faq
* updatex doc/help/tds.dvi
* remove ragged2e.bug
===
The files / installation
===
You can get teTeX-2.0.1 from the following server:
ftp://cam.ctan.org/tex-archive/systems/unix/teTeX/2.0/distrib/ (UK)
Other servers will follow shortly:
ftp://dante.ctan.org/tex-archive/systems/unix/teTeX/2.0/distrib/ (GER)
ftp://tug.ctan.org/tex-archive/systems/unix/teTeX/2.0/distrib/ (US)
A full list of mirrors is available here:
ftp://cam.ctan.org/tex-archive/CTAN.sites
From these servers, you need the following files for teTeX-2.0:
sources of the programs (required):
==> tetex-src-2.0.1.tar.gz
support tree with fonts / macros (required):
==> tetex-texmf-2.0.1.tar.gz
sources for parts of the texmf tarball (optional):
==> tetex-texmfsrc-2.0.1.tar.gz
The installation instructions are included in the tetex-src-2.0.1.tar.gz
archive as files INSTALL (complete instructions) and QuickInstall
(short version).
Thomas Esser, February 2003
Re: solaris 9 compile faliure
> configure: WARNING: sys/ptem.h: present but cannot be compiled > configure: WARNING: sys/ptem.h: check for missing prerequisite headers? > configure: WARNING: sys/ptem.h: proceeding with the preprocessor's result > configure: WARNING: ## ## > configure: WARNING: ## Report this to [EMAIL PROTECTED] ## > configure: WARNING: ## ## That will be fixed in the next version. > bison -y -d -v ./web2c.y > conflicts: 1 shift/reduce > test -f y.tab.c && mv -f y.tab.c y_tab.c > make[3]: [y_tab.h] Error 1 (ignored) > test -f y.tab.h && mv -f y.tab.h y_tab.h > make[3]: [y_tab.h] Error 1 (ignored) > gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I.. -I./.. -g -O2 -c main.c > main.c:18:19: y_tab.h: No such file or directory Strange. bison should habe created the files y.tab.h y.tab.c y.output and the mv commands mv -f y.tab.c y_tab.c mv -f y.tab.h y_tab.h should have renamed them. It works for me (and I just have installed bison 1.75 to verify this). Thomas
Re: `@' sign in path not treated properly
> I've tried to compile current TeTex on Tru64Unix 5.1A with latest > version of compilers from Compaq/HP, and I got the error below. Please, cc > me in any replies. The fix suggested by Albert Chin looks ok. Olaf Weber (web2c + kpathsea maintainer) has decided to use % as separator instead as a short-term solution and to get rid of that code in the long term. > Please note, that configure forced usage CFLAGS -Olimit 1000 -std1 . > -std1 makes cc into more strict mode, although it is sometimes better > than standard -std. I'm not sure about limiting the optimization by > default. I don't think it's a good idea and I as a user did not ask for > it either. That optimization limit was added to work around some compiler bugs which produced incorrect code with higher optimization. That -std1 was needed, too at some point. > sign. Maybe this is the same problem, I don't know, maybe it's enough to > recreate configure with never auto* tools. No, since automake is not used and the code in question is used in some Makefile.in. Thanks for your report. Thomas
Re: dvipdft is missing?
> We, tetex maintainers of Debian, got the bug which said > that teTeX 2.0 included dvipdfm but a wrapper script > dvipdft was missing (in the teTeX 2.0 source tree). When I added dvipdfm to teTeX, I have looked at the dvipdft and found that it writes to /tmp in an insecure way. Then, just before making the teTeX-2.0 release, I have forgotten that item... > Apparently, dvipdft was referenced in a manual page of dvipdfm. > Is there any chance that dvipdft will be included in teTeX? Yes, but not the original script. It needs to be fixed for security. Thomas
Re: listings.sty removed ?
> Fundamentalism is a Bad Thing. About politics, religion, licensing or > anything. And the fact is that teTeX 2.0 have lost usefulness because > of such fundamentalism. I will check if the license of the listings package is ok for free software and put the package back if this turn out to be true. I don't agree with your opinion on licensing. Being free software is a great plus for teTeX. All those nonfree packages are still available to TeX users, they are just not part of teTeX. On the other hand, teTeX is now free and can be included as part of a book-cdrom, linux distributions, other free software packages etc. To Robin: no I don't think that multicol.sty is nonfree. I remember that there was a lengthy discussion about that with the outcome of the current license. Is there any reason to recheck the license of multicol.sty? Shall we really restart it all? Thomas
Re: how to install TeTeX 2.0 ?
> but now I do not know how to compile and install them. >From ANNOUNCE-2.0 (same directory as the three tar files): The installation instructions are included in the tetex-src.tar.gz archive as files INSTALL (complete instructions) and QuickInstall (short version). Do you need help to unpack the tetex-src.tar.gz tarball? Thomas
Re: Broken pipe, teTeX dvips, Redhat linux
> I have a problem with dvips(k) 5.86 of tetex-1.0.7-57 under linux > Redhat 8. RedHat has turned on secure mode in dvips (by a setting in dvips's config.ps) to fix a security problem in the print filter despite the following facts: - printing dvi files to lpr does not work if the file references eps graphics from the user's directory (so in fact, it does not make much sense to have this support in the print filter) - the dvips version is broken because secure mode cannot be turned on via commandline option - secure mode also affects the output pipe specified in the config file The last two bugs are fixed in teTeX-2.0's dvips (dvips(k) 5.92b). Thomas
Re: teTeX-2.0, libwww, linux
> If I try to compile the www library in a linux (redhat-8.0) system, > there is a header that is missing. I added an > #include configure checks for netdb.h and sets HAVE_NETDB_H in wwwconf.h. Please, check if this has worked on your system. Look into config.cache (in libs/libwww) if HAVE_NETDB_H is not set. wwwsys.h includes netdb.h if HAVE_NETDB_H is set. Is there some .c file includes HTDNS.h without including wwwsys.h before? You somehow have missed to send the actual error message... > people use an already installed libwww. I like to compile my own TeX > and have its binaries independent of redhat's supplied libs. I regulary compile libwww on my linux (non-redhat system) without any problem. Thomas
Re: texlinks
> +# History: > +# Tue Apr 9 22:46:34 CEST 2002, te: > +# do not create symlinks for cont-??, metafun and mptopdf > > This is IMHO a bad idea, if one enables a format he/she wants > to use it. ConTeXt supports these formats by its helper scripts, e.g. texexec and mptopdf (both wrappers to perl scripts). Thomas
Re: installation of tetex 2.0, replacing tetex 1.0
> older version of tetex. With tetex 1.0 running on my Linux box, I'm not > sure how best to upgrade to version 2.0. I've read FAQ point 16 on It depends... Where does your teTeX-1.0 come from (rpm from your Linux distribution, or self-installed)? Do you plan to use the new release in parallel wih the old one? What directories are used by the old installation and where do you plan to put the new one? Thomas
teTeX-2.0
Well, a long time has been around since teTeX-1.0 ... I hereby proudly
presend:
===
teTeX 2.0
===
This is the announce of teTeX-2.0, a TeX distribution for UNIX
compatible systems.
===
Main features of teTeX-2.0:
===
- included files reviewed for license problems; teTeX now is free software!
- program packages: web2c 7.4.5, pdfTeX 1.10a, e-TeX 2.1, Omega 1.23.2.1,
xdvik 22.40v, dvipsk 5.92b, dviljk 2.6p2, dvipdfm 0.13.2c, ps2pk 1.5,
makeindex 2.14, texinfo 4.4, texconfig 2.0, updmap 2.0, texdoctk
- main TeX formats:
plain.tex 3.14159265, LaTeX2e <2001/06/01>, ConTeXt 2003.1.31
- TDS (TeX Directory Structure) compliant support tree
with fonts / macros / documentation: 150 MB, >11000 files
- easy to install and to customize, even for a multi-platform setup
- ready for producing resolution independent (bitmap free) postscript or
pdf documents (including thumbnails, hyperlinks and bookmarks)
For release notes, please look at ./NEWS inside the tetex-src tarball.
===
Legal notice / license
===
teTeX is free software. Individual files and sub-packages are copyright
by different authors, but I have taken care that everything is free
software as defined by the free software foundation:
http://www.gnu.org/philosophy/free-sw.html
===
The files / installation
===
You can get teTeX-2.0 from the following server:
ftp://cam.ctan.org/tex-archive/systems/unix/teTeX/2.0/distrib/ (UK)
Other servers will follow shortly:
ftp://dante.ctan.org/tex-archive/systems/unix/teTeX/2.0/distrib/ (GER)
ftp://tug.ctan.org/tex-archive/systems/unix/teTeX/2.0/distrib/ (US)
A full list of mirrors is available here:
ftp://cam.ctan.org/tex-archive/CTAN.sites
From these servers, you need the following files for teTeX-2.0:
sources of the programs (required):
==> tetex-src-2.0.tar.gz
support tree with fonts / macros (required):
==> tetex-texmf-2.0.tar.gz
sources for parts of the texmf tarball (optional):
==> tetex-texmfsrc-2.0.tar.gz
The installation instructions are included in the tetex-src.tar.gz
archive as files INSTALL (complete instructions) and QuickInstall
(short version).
===
Windows and MacOS X versions
===
I don't maintain such ports myself, but you can get them here:
Windows (win32)http://www.fptex.org/
MacOS X (darwin) http://www.rna.nl/tex.html
===
Documentation / getting started
===
teTeX contains a lot of documentation about the packages it includes.
For a start, please look at
texmf/doc/tetex/TETEXDOC.{ps,pdf,dvi}
and
texmf/doc/index.html
texmf means the directory in which you have unpacked the tetex-texmf
tarball during the installation process
===
De-support of repacked and binary distribution
===
Unlike previous releases, I don't plan to make binary releases or
sub-packges of the texmf tarball. Lots of other projects and people
provide teTeX in repacked and compiled form and I am willing to maintain
links to such resources on teTeX's web page. I think that I will do
a better service to the TeX community by concentrating on the three
tarballs (src, texmf, texmfsrc) and shorter release cycles, than by
providing binaries and repacking the distribution.
===
Mailing lists / web pages:
===
Mailing lists:
for discussion:[EMAIL PROTECTED]
for announcements: [EMAIL PROTECTED]
Related web pages:
http://tug.org/teTeX/
http://www.pdftex.org/
http://www.tex.ac.uk/cgi-bin/texfaq2html?introduction=yes
http://www.dante.de/
http://tug.org/
http://www.pragma-ade.com/
Have fun!
Thomas Esser, February 2003
Re: How can I instruct dvips to use outline fonts instead of the CMones?
> Could anybody tell me how to instruct dvips > to use bluesky fonts instead of the standard > Computer Modern fonts? The following works with standard teTeX-1.0. I don't know if this is different in RedHat's version... cd `kpsewhich -expand-var='$TEXMFMAIN'`/dvips/config vi updmap # or use a different editor # change type1_default=false -> type1_default=true ./updmap That's it. updmap is described in TETEXDOC, just texdoc TETEXDOC Thomas
Re: teTeX dvips/bluesky/bsr.map and updmap
> I am a Japanese pTeX on teTeX user. I use TeXShop and dvipdfm > program to compile TeX and preview on my Mac OS X, which needs > reencode files for computer modern fonts which are remapped by > dvipdfm. Can you please explain, why you think that you need reencoding for all fonts in the bsr set? The idea of reencoding is to help the reader to find ligatures (if you have a version with the "search" option) and to help text extraction. I don't see a benefit for reencoding e.g. cmbsy10. In the map files from the author of dvipdfm, only the "pure" text fonts have been reencoded (see cmr.map in the dvipdfm distribution). > While making this encode files, I found updmap didnot work on Mac OS > X since sed cannot understand replacement statements like > 's/\(.*\)/\0 \1/'. '&' mark do the same work as '\0' on Mac OS X > and '\0' is just a letter '0'. I don't know how to avoid this > matter. I just have fixed a few compatibility problems with updmap and I hope that the teTeX-2.0 version will be good enough. If you want to test it now, get it from here: http://www.dbs.uni-hannover.de/~te/updmap Thomas
Re: problem with "make pdftexbin", -static (teTeX 2.0 rc1)
> When I try to build only the pdftex and pdfetex binaries > by "make pdftexbin" in texk/web2c/, broken binaries are I don't know who made / needs that "pdftexbin" target. If it does not work for you, don't use it. Thomas
Re: platex+teTeX
> trees, one for the original teTeX and one for ptex. I'd rather unify > these two, if possible --- this will also simplify the situation for > users who require access to both trees, and save me some support > time. Your users should not notice much of the separation into two trees if you set up both texmf trees in the system-wide texmf.cnf file. Thomas
Re: Problems with teTeX on FreeBSD 4.7
> i've looked over the list of supported teTeX platforms at the above link, > but none of them corresponds to my platform, which is X86/cygwin . > do you support the cygwin platform, or are the cygwin people responsible > for that? Yes, teTeX for cygwin can be downloaded at various cygwin sites. Thomas
Re: Problems with teTeX on FreeBSD 4.7
> Building the most recent teTeX (tetex-src-1.0.7.tar.gz) on our OpenBSD > Sparc server proceeded without problems. When I tried to add support > for our FreeBSD i386 platforms by mounting the proper directories on the > freebsd platform, logging in there and doing: Thanks for your bug report. Since you have found your work-around and since I am close to release a new version of teTeX, it does not make much sense to try fixing teTeX-1.0.7 in this respect. The current teTeX-beta (which is already close to the next teTeX release) is known to work fine on FreeBSD/i386. If you want to try it yourself, follow the "beta versions" link on the teTeX homepage (http://tug.org/teTeX/). Thomas
Re: Building teTeX on HP-UX 11.0
> checking host system type... Invalid configuration > `hppa2.0w-hp-hpux11.00': machine `hppa2.0w-hp' not recognized For the current teTeX-beta, I just have updated the relevant config.sub / config.guess files from the gnu server. That hopefully fixes this problem. So, you can try if today's teTeX-beta release fixed your problems. That teTeX-beta release will soon (within the next 24 hours) be available at ftp://cam.ctan.org/tex-archive/systems/unix/teTeX-beta/teTeX-src-beta-20021209.tar.gz ftp://cam.ctan.org/tex-archive/systems/unix/teTeX-beta/teTeX-texmf-beta-20021209.tar.gz ftp://cam.ctan.org/tex-archive/systems/unix/teTeX-beta/teTeX-texmfsrc-beta-20021209.tar.gz or ftp://ftp.dante.de/tex-archive/systems/unix/teTeX-beta/teTeX-src-beta-20021209.tar.gz ftp://ftp.dante.de/tex-archive/systems/unix/teTeX-beta/teTeX-texmf-beta-20021209.tar.gz ftp://ftp.dante.de/tex-archive/systems/unix/teTeX-beta/teTeX-texmfsrc-beta-20021209.tar.gz Thomas
Re: europs
> I want to use the Euro-character in LaTeX. Therefore I tried to install > the europs.sty package under teTeX in Mac OS X, but without success. teTeX-beta includes the eurosym package for more than two months now. You can try this if your Mac OS X port of teTeX already includes that package. Documentation is included in texmf/doc/fonts/eurosym. > Perhaps I should not extract the eurofont.zip for Windows and rename > the extracted files appropriately, but adapt the eurofont.sea.hqx for > Mac somehow. I don't think that this is the problem. pdftex works fine with usual type1 fonts. I'd guess that there are missing or incorect lines in your map files that pdftex uses. But, since Rowland McDonnell (author of the eurofont package) is a MAC user, I sugggest that you contact him directly: [EMAIL PROTECTED] Thomas
Re: Local texmf tree not correctly recognised
> I installed some local additions to the system wide texmf tree in
> ~~/texmf. In order to have latex pick that stuff up, I set $TEXMF to
> {$HOME/texmf,!!$TEXMFMAIN//,!!$TEXMFLOCAL//}. That results in:
You should make this
{$HOME/texmf,!!$TEXMFMAIN,!!$TEXMFLOCAL}
> warning: kpathsea: variable `TEXMF' references itself (eventually).
I have seen this before. Could you please report that to [EMAIL PROTECTED]?
Thomas
Re: Quick question regarding -src-specials
> It is a well-known problem that there are quite a few TeX versions
> are around where -src-specials will cause the equivalent of
> \usepackage{indentfirst}, namely causing chapter beginnings and the
> like under LaTeX to be indented.
I think that teTeX-beta never had this bug. It was introduced by a "last
minute" web2c-fix, shortly before TeX Live 7 was released. I was unsure
about that fix and had not aapplied it to teTeX-beta.
> Are there any specific releases of teTeX-beta and/or TeXlive that one
> could recommend as not being afflicted in that particular manner?
I think that only the first versions of TeX Live 7 are affected. The
programs identify themself with a web2c-version that ends up with "x",
7.3.7x I think.
Thomas
Re: Duplicate messages
> Is it just me or are others getting duplicate messages from the > list? Thomas, can you take care of this problem? Thanks. No, it is not just you. I have found out, that the duplicate messages are being send via btamail.net.cn back to the list. Thus, I have just unsubscribed all (two) adresses subscribed from there. Thomas
Re: increasing string size
> both teTeX and fpTeX? Note that I am using the same Omega, version 1.15, in > both fpTeX and teTeX from TeX-Live6. You can set this in texmf/web2c/texmf.cnf. TeX Live is based on teTeX, but unless you are sure that the problem you have is not caused by a change made in TeX Live, you should send bug reports to the texlive list. Thomas
Re: pk font not created
> This is METAFONT, Version 2.7182 (Web2C 7.3.1) (base=mf 2002.11.8) 14 > NOV 2002 16:58 > **\mode:=ljfzzzfr; mag:=1+57/600; nonstopmode; input cmsy10 ... > ! This can't happen (m). Your metafont binary does not work properly. Can you try to recompile metafont with no or less optimitation? Thomas
Re: Compilation problem (no check for missing headers)
> Shouldn't the --configure stage check for the presence of these > headers? Yes, that's a bug. I think that you can work around it by passing --without-x to configure and that this problem is fixed in current teTeX-beta. Thomas
Re: dvipdfm compression
> In TeXLive6 compression in dvipdfm does not work in teTeX, though it works You are on the wrong list. dvipdfm is not part of teTeX (although I might add it). > Sounds like a compilation problem. Is there a way to fix this without When reporting a problem with some binary, you should mention the platform that you are using. Thomas
Re: new dvips
> When we say that the character shifting issue has been corrected, > do we mean that > dvips -Ppdf ... without either -G or -G0, > now works for computer modern, adobe postscript, and combinations of them? > Is that right? It means that -G1 (as set e.g. via -Ppdf) does no longer produce incorrect output. The remapping of characters works for computer modern, but it does not work for a lot of other fonts. The new dvips decides on a per-font basis whether to remap it or not and it only remaps if that won't mess up the result. Thomas
Re: Compilation problem (no check for missing headers)
> I downloaded tetex-src-1.0.7.tar.gz, ran './configure --prefix=$HOME' > and then 'make'. The compilation halted part way through with > > gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I.. -I./.. -g -O2 -c x11.c > x11.c:19: X11/Xlib.h: No such file or directory > x11.c:20: X11/Intrinsic.h: No such file or directory > x11.c:21: X11/StringDefs.h: No such file or directory > > Shouldn't the --configure stage check for the presence of these > headers? That's right but a bug prevents this from working everywhere. It is fixed in teTeX-beta 20021025 (see: http://tug.org/teTeX/) If you want to use teTeX-1.0.7 instead of the current beta, try ./configure --without-x Thomas
Re: dvips-ing TETEXDOC.dvi
> > is fixed in newer version of dvips, but with the old version, you can > > use -Ppdf -G0. > > It would be helpful to have a more precise definition of "newer". I have I am sure that dvips version 5.90a or later are ok. I am not 100% sure if 5.90a was the first version that fixes the problem. A simple test is the following: echo '\font\x=ptmr7t\x fi\end' | tex; dvips texput -G1 -o If you get the fi ligature in texput.ps: all is ok. Else: dvips is broken wrt. -G1. Thomas
Re: dvips-ing TETEXDOC.dvi
> No doubt this is an FAQ somewhere, but if I use the '-Ppdf' option when > dvips-ing TETEXDOC.dvi, the 'fi' ligatures turn into English pound > symbols. Further processing of the PS file with gs's ps2pdf doesn't > help. Using the '-Pcmz' option avoids this problem. Perhaps I have > misunderstood the reason for using '-Ppdf': should it be used only if > one intends to immediately distill the PS file with Adobe's Acrobat > distiller program? (Since I don't have this program, I can't test > whether the resulting PDF file would be OK.) That -Ppdf turn on a feature called "character shifting" and dvips is not smart enough to detect that this does not work with all fonts. This is fixed in newer version of dvips, but with the old version, you can use -Ppdf -G0. Thomas
Re: redefinition of `struct option'
> I'm having an install problem. I'm on linux-mandrake 8.2 and have gcc > v2.96. > > gcc -DHAVE_CONFIG_H -DKPATHSEA -I. -I. -I.. -I./.. -g -O2 -c gsftopk.c > gsftopk.c:409: redefinition of `struct option' Where is "struct option" defined for the first time? Thomas
Re: creating a type1 fonts package
> If not: What is the cleanest way to update the fonts map in the > post-install script (and in the post-uninstall script! my package should > also clean-up after itself when it is uninstalled). With the updmap as contained in teTeX-beta, you just need to call updmap --enable Map foo.map with foo.map being the name of the map file that is to be added to the configuration. Thomas
Re: teTeX 1.0.7 doesn't install
> > ^[[H^[[2JError opening terminal: generic. > > ^[[H^[2Jmake: *** [install] Error 1 > > It appears that your TERM variable is set to "generic" rather than > something like "xterm" or "vt100". I think this failure is in the texconfig is passing this TERM=generic setting to dialog (or tcdialog). This is a fail-safe setting because dialog is compiled with a static version of ncurses and this might 1) have trouble to find the right path for the terminfo files on the system it runs on 2) might have touble to use the terminfo files, because they are not necessarily compatible with ncurses That's why texconfig passes settings for TERM and the TERMINFO path to dialog. This only works, however, if teTeX's texmf tree is properly installed. Thomas
Re: fancybox documentation missing
> Just wanted to let you know that the fancybox documentation obtained > by running latex on the fancybox.doc file is missing from tetex. You have reported this quite some time ago and I have added the missing fancydoc.dvi file. There has not been a stable teTeX release since, only new teTeX-beta releases. Thomas
RE: MAC OS X (BSD)
> Hrm,.. I'm thinking of buying a MacOSX box. Am I wrong in my understanding > that a \approx vanilla teTeX would compile and work? Interesting to know > whether or not I'd be able to follow "bleeding edge" with ease. > > mh (old fbsd fan/user -- haven't enough followed the MacOSX/Darwin thing ;) It should work (latest teTeX beta). I am in touch with the maintainer of the mac os x port and he tells me when something breaks on mac os x. The most recently fixed bug was an incompatibility of texconfig and zsh (with the result that the temp. directory directory will not be removed upon program exit), but I have already fixed that (just a few days after that 2002-05-30 beta). Thomas
Re: MAC OS X (BSD)
>We have a couple of users that would like to run > TeX on their MAC laptops running the new MAC OS X . I have checked the ftp > sites and the catalogs to see if there is any reference and don't > see any as of yet. Is there any releases or future plans on > releases for this MAC OS based on BSD. I think that teTeX on Mac OS X is already better supported than I could do by simply adding the binaries to teTeX. Even without using the knowledge I have by the communication with the maintainer of the Mac OS X port of teTeX, I have easily found the page http://www.rna.nl/tex.html by searching for "teTeX mac" with google. Thomas
Re: Why VARTEXMF instead of (say) TEXMFCONFIG ?
> I am thinking over the problem of maintaining a complex TeX system with > several TDS trees (on a Unix computer), looking at documentation such as One main question to answer is the degree of integration into the linux system. Sure, you can split teTeX into several directories, e.g. put config files somewhere below /etc, variable runtime data somewhere into /var etc. In my opinion, you should only do that if you have a good reason to do so. If you focus on your linux system and have special needs for backup, system configuration etc., you should go the "linux way". If you focus on TeX and want to have an easy way of upgrading, running multiple instances of teTeX / TeX Live etc. it recommended to keep each TeX installation in its own directory tree. > What does the "VAR" mean in VARTEXMF? Well, why care about names? It is the semantic that defines things, not their name. VARTEXMF is a special name, because it defines the texmf tree where you want to keep variable configuration data. Some scripts (e.g. the upcoming updmap in today's teTeX-beta or TeX Live 7 and texconfig) use the VARTEXMF to detect your intention that you want to put changed / new files there, rather than into TEXMFMAIN. > intended use of VARTEXMF seems rather different. As near as I can tell a > more accurate name for VARTEXMF would be TEXMFCONFIG. This directory tree does not only store configuration files, but also format files etc., so in unix terms "variable runtime data". > (Is this a texk question rather than a teTeX question?) It is a teTeX question, since "texk" has no script which assigns a special semantic to VARTEXMF. All those scripts (texconfig, fmtutil, the new updmap) have been written for teTeX. > FHS recommendations without preconceived notions. I suppose some of > these questions are better asked on an FHS mail list but if anyone As I said above: I would ignore the FHS unless you have a good reason to follow it. > ---What is difference between /opt and /usr/local? I.e., what is the > best "main" location for teTeX? Why? You should have a convention for putting additional software to your system (I mean something that does not come with your linux distribution). For teTeX, just follow that convention. In the department of the university where I have previously worked (with the name dbis), we have decided to use /software/dbisfor locally developped stuff /software/pay for things we have to pay for /software/oss for the rest. You see, I don't really care about names; not everything here is really open source, e.g. the acrobat reader. Below these directories, we have grouped applications into categories, e.g. Editors, Networking, Databases, Development. teTeX ended up in /software/oss/Text/teTeX-1.0. > /usr/local for anything obtained elsewhere? (If that is indeed true, I > think I would rather have a top level /local directory instead of > /usr/local.) /local sounds great. It won't conflict with anything else. > not included in teTeX, what about making a common parent directory to > hold both teTeX and the other packages: Not a bad idea... > The FHS description of the /usr/share area makes it seem that all the > run-time TeX input files for LaTeX and similar should go here. Or, how If you really want to share things between different systems, you need to find a strategy about how to do it. nfs, rsync whatever. If you don't need that, then don't care about these special directories. > to be extremely slow. And also format files are not yet generated on > demand, last I knew? Although it would be feasible if sufficient fmtutil Today's teTeX-beta and TeX Live 7 will generate format files "on demand". Hope, this is helpful somehow... Thomas
Re: Release / status of teTeX
> As already mentioned in an announcement on the tetex-pretest list > >(http://www.mail-archive.com/tetex-pretest%40informatik.uni-hannover.de/msg00369.html) > you can have the latest teTeX beta (2002-04-02) _and_ the fix by applying > http://www.tug.org/teTeX/teTeX-src-beta-20020402-expdvips.patch.gz. > Afterwards the dvips(k) version is still 5.86g, but the bug is fixed > (at least for me). After some testing of the patch, it was applied to the main version of dvips and the version number was increased. So, a patched 5.86g is about the same as the new 5.90a. Thomas
Re: Release / status of teTeX
> Which softwares has bugs that make character-switching necessary? I am not the expert on this, but the things I know are Acrobat Reader (don't know exactly when they fixed that bug, but version 3.x are broken) and Adobe Illustrator. > I, for another reason, updated to the latest teTeX beta (2002-04-02) and > the dvips version included is: > > dvips --version > dvips(k) 5.86g > kpathsea version 3.3.7 The *next* teTeX pretest will have that fixed dvips. TeX Live 7 won't have that fix. But, Sebastian is working on a "TeX Live Special Edition for TUG 2002" which will also have that fix, I guess. Thomas
Re: Release / status of teTeX
> > No, not a 100% corresponding release. I have the -G1 fix for dvips and > > the "downgrade update" for Omega (1.15 is the best version currently > > available, the TeX Live version is not that stable). > > What is "the -G1 fix for dvips"? The -G1 option in dvips (can be activated on the commandline or in a config file; typically it is enabled in config.pdf) turn on a feature named "character shifting". This works around bugs in various other software, by shifting characters of a font to the "upper" area of a font. This works well e.g. with CM fonts, but it fails if the upper slots are not free in the font. Example: $ cat x.tex \font\x=ptmr7t\x fi\end $ tex x; dvips -G1 x -o The fi ligature appears as some other character when a broken dvips is used. The new fix (dvips(k) 5.90a or later) checks on a per font basis if character shifting is possible. Thomas
Re: Release / status of teTeX
> Now that the latest tex-live release is practically on its way out the > door, can we expect a corresponding teTeX release? No, not a 100% corresponding release. I have the -G1 fix for dvips and the "downgrade update" for Omega (1.15 is the best version currently available, the TeX Live version is not that stable). In the very near future, I plan to release a new teTeX-pretest. teTeX-2.0 (the next "stable" release) is not too far away, too. There are so many improvements that have been recently made, which justify raising the version number to 2.0 for the next stable release. > (The relationship between tex-live and teTeX seems shady to me at best...) program sources === It is like this: TeX Live is available in an online repository which I can read/write. I have a separate (non-public) source tree where I keep the teTeX sources. If I have something new, I usually put it into the teTeX tree first. If I ask Sebastian if he wants that for TeX Live, he always says "yes". Then, either I send him something, or I check it in directly. But, I am not the only person who contributes to teTeX / TeX Live. Other people make fixes / new stuff available for TeX Live either by sending stuff to Sebastian or by directly updating the online repository. >From time to time (sometimes several times a day) I sync my local copy of TeX Live with the online repository and get all the updates. Then, I take all the useful stuff and put it into the teTeX source tree. Having the software at different places causes some maintenance overhead, but I think that no real development work is doubled. texmf tree == We both maintain our own "texmf" tree, but from time to time we copy stuff from each other... > I currently > run the latest teTeX beta personally, but don't dare expose more than > a select few of my users to it - although I must say have had no I think that the latest "beta" stuff has much less problems than the old "stable" stuff. That's yet another reason why it is time for a new stable release. Thomas
Re: config woes
> for I never had to that there. Is there a reason TeXLive does not configure > texmf-var for UNIX immediately upon installation? While TeX Live contains teTeX, it has it's own installation procedure. You are asking at the wrong list. Please, consult the TeX Live documentation for the right place... Thomas
Re: config woes
> :~> /usr/TeX/bin/i386-linux/oxdvi -version > xdvi(k) version 22.40b for Omega That's ok, So the script and the binary behind it both work. > I use KDE, which can make links to various programs through such shell > scripts. So when I mouse-click on the xdvi shell script (or a link to it), I guess that "KDE" has a special case for xdvi. Othat than that, I have no idea why one should work and the other not. After all: this is not a teTeX problem, but a KDE problem. Thomas
Re: config woes
> avail. Clicking on it gives > Couldn't find the program 'oxdvi'' What happens if you start a shell and type /usr/TeX/bin/i386-linux/oxdvi -version in it? BTW: what do you mean by "Clicking on it"? Which application are you using to start oxdvi by "Clicking on it"? Thomas
Re: config woes
> 1. I can't get my path commands to stick. When I issue > export PATH=$PATH:/usr/TeX/bin/i386-linux > I have to reissue it each time I log in and sometimes more often. I have > issued this command as root, and the problem still wont go away; environment variables are only passed to child processes on UNIX, never to parent processes. Put this setting into your private ~/.profile or /etc/profile to make it permanent. > 2. mktexlsr does not update everything. I have added my former texmf-var tree > to teTeX, but mktexlsr gives > > mktexlsr: Updating /var/lib/texmf/ls-R... > mktexlsr: Updating /var/lib/texmf/db/ls-R... > mktexlsr: Updating /var/cache/fonts/ls-R... > mktexlsr: Done. > > ignoring /usr/TeX// entirely. I have not changed anything in texmf.cnf; Was it the right file? Check with kpsewhich texmf.cnf Did you really add your new texmf-var to the TEXMF variable? kpsewhich -expand-var=\$TEXMF > 3. Clicking on the shell script for oxdvi gives the following message: > Couldn't find the program 'oxdvi'' Just check if the oxdvi script exists in /usr/TeX/bin/i386-linux. Thomas
Re: cmbright
> while upgrading my SuSE 7.3 to SuSE 8.0 the tetex rpm was upgraded from > 1.0.7-285 to beta.20020207-70. Now the problem seems to be that in that new ... > Now my question is: Has cmbright been removed from tetex? (If yes, why?) How > can I get that package and include it in my tex installation? Yes, cmbright was removed for copyright reasons. Meanwhile, however, the license was changed again, and I have put the package back into teTeX. So, the next version (beta or stable) will have it again. Thomas
Re: Compile problems on Tru64 Unix
[Olaf: another suggested change for mktexpk] > 1. Edit some files. Here are diffs between the modified and "pure" src >directories: Can you please resend using "diff -u" (preferred) or "diff -c"? > /usr/local/share/teTeX/bin/alpha-osf/mktexpk: mf-nowin: not found > ^^ A bug in mktexpk (it fails to supress this output). Fix: execute mf-nowin --version in a subshell, i.e. if (mf-nowin --version) >/dev/null 2>&1; then ... This obviously works for e.g. ttf2pk and hbf2gf invocations which are already implemented like this. Thomas
Re: [tex-live] Xdvi binaries
> Many thanks, Thomas. Such a brave member of DANTE and GUST ;-) > I didn't expected that you're still on line (5:40 here). Just for the record: I am a member of TUG and GUST. And I am not "still on line", but "again online" (your local time is the same as mine). I'll have breakfast and then go to work... Thomas
Re: [tex-live] Xdvi binaries
> I think that most important thing to be resolved before the final > release of TL7 is that Xdvi cannot run on *still* widely used RH6.x > (missing shared libraries: libXaw.so.7). > I got many messages concerning that... Find a system with a static version of libXaw, then we can use that system to build a binary which no longer depends on the shared libXaw. Thomas
Re: Local Fonts requested
> I work as a usual user on a teTeX system (UNIX). When kpathsea has to > generate > new fonts it tries to generate them on a read-only file system (see > below). Is it possible to let kpathsea generate these fonts in a directory > in my home account? And can I do this by setting an environment variable? As admin, set the varfonts feature (using texconfig). You can set VARFONTS to $HOME/texfonts, so each user gets his own directory. Thomas
dvips config change. Comments?
[This "rfc" is send to comp.text.tex, the tex-k list and the tetex list] I am planning to change teTeX's default configuration of dvips. The current configuration is that bitmap fonts are preferred over type1 if both are available. This has the drawback that lots of ugly pdf files are produced (since the acrobat really does not do a good job in displying type3 fonts) and even ugly prints (if the resolution of the bitmap font does not match the printer). My plan is to reverse the preference so that type1 fonts are used unless a paramter is given (e.g. -Pusepk) or a printer specific configuration file requests this otherwise (e.g. by setting "p usepk.map"). The implementation of that feature would be that I set up a psfonts.map which includes all type1 fonts available and a usepk.map file without the fonts that are availabe in metafont format. Some config.usepk file which just contains "p usepk.map" can be provided too. Users of teTeX can use the updmap script which will be changed to output (among other files) psfonts.map and usepk.map. So, there would still be a single place to configure the map files. So, if you have your own fonts, just make them known to updmap and regenerate the map files for all applications (dvips, pdftex, gsftopk, xdvi, ...). Of course, it will be easily possible to change the global preference (i.e. make bitmap download the default) via updmap, but still, I'd like to hear if the suggested change would cause a problem somewhere. Thomas
Re: Compile problems on Tru64 Unix
> cxx -o pdftex pdftexini.o pdftex0.o pdftex1.o pdftex2.o pdftexextra.o > pdftexdir/libpdf.a ../../libs/libpng/libpng.a ../../libs/zlib/libz.a > pdftexdir/xpdf-0.80/xpdf/pdftoepdf.a pdftexdir/xpdf-0.80/goo/libGoo.a > lib/lib.a ../kpathsea/STATIC/libkpathsea.a -lm > ld: > load_compressed_file could not malloc 25820987655. bytes for Well, it looks like the linker (ld) wants to allocate 24GB of memory which fails. My first guess is that something, most propably the linker, is broken. Thomas
Re: Compile problems on Tru64 Unix
> I am trying to install the latest teTeX beta. On SuSE Linux 7.2 it compiles > all right, but on Tru64 Unix V5.1, using GNU make and gcc, "make all" > exits with the following error message: > > gcc xstat.c -DHAVE_CONFIG_H -I. -I. -I.. -I./.. -g -O2 -c -o STATIC/xstat.o > xstat.c:41:19: macro "lstat" requires 2 arguments, but only 1 given > make[2]: *** [xstat.lo] Error 1 > make[2]: Leaving directory > `/usr/local/share/src/teTeX-beta/teTeX-src-beta-20020402/texk/kpathsea' > make[1]: *** [do-kpathsea] Error 2 > make[1]: Leaving directory > `/usr/local/share/src/teTeX-beta/teTeX-src-beta-20020402/texk' > make: *** [all] Error 1 > > Does anyone have a clue about what to do? Yes. Remove line 41 in file texk/kpathsea/xstat.c: extern int lstat (); Olaf, do you have an idea how to fix this in a portable way? Do you want to support systems which do not have proper declarations in theit header files and thus risking to break other systems? Thomas
Re: mktexpk destination
> I've just installed teTeX on a Sun system running Solaris 2.7.
>
> How do I tell mktexpk to put the fonts it creates into
> a directory defined by the user? Once upon a time,
> with maketexpk, we used:
>
> setenv MTPK_DESTROOT $HOME/tex/fonts
Just look at the variables in texmf/web2c/mktexnam. The name for the
variable of the destroot is:
MT_DESTROOT
Other then playing with this more "internal" variable (which require
setting the search path for pk fonts, too), you can enable the varfonts
feature (using texconfig) and set VARTEXFONTS to $HOME/tex/fonts.
If you don't want to use texconfig for this, put
: ${MT_FEATURES=appendonlydir:varfonts}
into texmf/web2c/mktex.cnf and set
VARTEXFONTS = $HOME/tex/fonts in
texmf/web2c/texmf.cnf.
Thomas
Re: About "texdoc pdftex" and "texdoc omega"
> So one possible solution would be to add some lines to texmf/aliases: > > pdftex.pdf pdftexman.pdf > omega.pdf omega-manual.pdf > etex.pdf etex-man.pdf Good idea (but the order is wrong. Right is e.g. pdftexman.pdf pdftex.pdf). > But when someone begins looking for documentation about pdftex, maybe > they would like to know first of all that there are four or five files > that might contain the desired information. Again, I'd say that this should be handled by texdoctk / helpindex.html. Thomas
Re: teTeX documentation
> I suppose you implemented something that searches through the file > names? Yes. > That is good, certainly, but what I wanted to suggest was an > idea of having something that searched through file *contents*. And this > would apply mainly for source forms like .tex or .dtx, since (at least > as far as I know) we don't have free & fast tools for searching dvi > files or pdf files. I don't think that texdoc should be extended in that way. IMHO, it should be a simple tool which just displays some documentation if you know the filename. For other things, use e.g. texdoctk or the helpindex. Thomas
Re: shell problem
> The tetex system contains some important perl scripts, for instance > epstopdf. Unfortunately, these scripts run only with bourne shell or > cshell, but not with bash (bash1, bash2). There are differences in case > of internal exec evaluation, in this case of the recursive determination > of perl binary's location. But the bash is the default shell, at the > very least with redhat linux. Don't debate, if it is sensibly or not - > what is the best way to clear the user's problem? I cannot reproduce the problem. It works for me with bash as login shell and on Linux (tested SuSE 7.2 and RedHat 7.2). > One solution could be to write "#!/usr/bin/perl" oder simple ":" as > first line into the scripts ... teTeX should work on systems where perl is not in /usr/bin. I don't see how a : should invoke perl. Thomas
Re: More texdoc requests
> In addition to the feature requests for texdoc, > I have one more request. Sometimes you want to > printout some package documentation on paper. xdvi (non-k) already has printing support and I think that this feature will be added to xdvik in the near future. So, there would not be any need for this feature any more... Thomas
Re: teTeX documentation
First of all, thanks for all these suggestions about texdoc. > 1. Running texdoc with no arguments does nothing. Why not make it run > the --help option? Well, I don't know why it didn't do this from the beginning. It was easy to fix, though. > 2. It would be good if this command would show something useful: > texdoc texdoc Ok, it now runs "man texdoc". > 3. It would be good if this command would show something useful: > > texdoc teTeX > > Maybe by having symlinks teTeX.pdf -> TETEXDOC.pdf, teTeX.dvi -> > TETEXDOC.dvi, etc.? Ok, I have an entry TETEXDOC.pdf teTeX.pdf in texmf/aliases. > 4. It would be good if this command would show the FAQ with "more", or > something to that effect: > > texdoc teTeX-FAQ > > Instead what I see is this: > > /usr/local/bin/texdoc: /usr/local/teTeX/share/texmf/doc/tetex/teTeX-FAQ: cannot >execute > > Perhaps something along the lines of > > case "$filename" in > *FAQ *faq *.txt *README*) $TEXDOCVIEW_txt $filename ;; > ... Everything with empty extension will now be viewed using a pager. > 5. It would be good to have an additional option to allow grepping > through the documentation tree, perhaps > > texdoc -l -s 'regular-expression-for-grep' > > This would be slower, of course, but it would help to have it as a > fallback for situations like > > texdoc teTeX > texdoc amsthm > > that fail only because the documentation file is called by a different > name. amsthm is badly chosen, since it does not match amsthdoc.dvi :-) Anyway, I have just implemented that -s feature (it does not need -l, it only displays filenames). > This would only work well if it were a general practice to have *.tex > and other source formats in the doc tree for searching, in addition to > the derived formats for viewing. But I think this is a good idea anyway, > because not infrequently when looking at some documentation it is useful > also to look at the source to see how the documentation was produced. texdoc only operates in $TEXMF/doc, and the (docstrip) sources belong into texmf/source. I don't think that texdoc should look at texmf/source. > Or, perhaps, have a parallel subtree "docsource" ?? No. > I am willing to help work on some of these features but I wanted to ask first > if some or all of them are already being addressed by others. Well, it was fun to implement these useful features myself :-) Thomas
Re: teTeX documentation
> > texdoc -l -s 'regular-expression-for-grep' > > Allowing regexp search is always a good idea. Do we need an extra > commandline switch here? IMO it is sufficient to replace the > string-match by a regexp-match. texdoc usually uses kpsewhich to find files which is much faster than scanning disks for files using find. So, the default should be that string-match done using kpsewhich and the regexp-match is specified by an option "-s" for "search disk". > But I think that grep should be called as "grep -i". With my implementation, people can do texdoc -s '-i pattern' 'another pattern' Thomas
Re: tetex distribution and these instructions in Sketch web page
> Sketch needs to know about the LaTeX fonts in order to display them. In > particular a directory with the *.afm files has to be added to the > sketch font path The afm files are not needed by LaTeX, so may not So, just cd texmf/fonts/afm and all afm files will be there. You still need the afm files from cmps-unix.tar.gz since these are not included in teTeX. > Similarly, the X server font path needs to have the *.pfb files from > Latex, and that one has me stumped. These files can be found in texmf/fonts/type1 > I administer 8 different RedHat systems, and don't want to have to > custom edit font stuff in each one unless really necessary, so I'm > asking here. I'd copy or symlink all type1 files from TeX into one directory for X. Then, use type1inst to create a fonts.scale file. If the different RedHat systems are networked, you can set up a font server for X, so you'll be able to maintain the fonts at one single place. Thomas
Re: Missing characters
> 1) If you use Computer Modern font, then use dvips -G -Ppdf > (otherwise you lose things like half of integrals or large parentheses) > > 2) If you use an Adobe Postscript font, then use dvips -G0 -Ppdf > (otherwise you lose things like fi ff ligatures) "dvips -G0 -Ppdf" is the same as "dvips -G0 -Ppdf" or even "dvips -Ppdf". If you want to load config.pdf without character shifting, specify that -G0 *after* -Ppdf: dvips -Ppdf -G0 For dvips, later settings overwrite earlier ones on the command line. Thomas
Re: Including pdfTeX extension files
> I just received my latest TUGboat with Han's PhD thesis on extending > TeX. In it, he refers to several utility files such as efcode.tex and > protcode.tex. They are available on CTAN (systems/pdftex/ext); can > they go into teTeX? (Haven't checked the latest beta, but they > weren't in the December one.) I didn't follow the discussion on the pdftex list about these features, but I think that the macros needed to be changes as pdftex has evolved. I think that these files should be available on CTAN or on http://tug.org/applications/pdftex, but I don't think that they are ready for wide distribution, yet. Especially, since teTeX's mktextfm is not yet ready to generate the needed tfm's on the fly... Thomas
Re: problems with eurofont tfm-Files
> gsftopk(k) version 1.17/700 gs7.00 is known to be broken wrt. font generation via gsftopk. Try a different (earlier or later) version. I recommend the latest version gs7.04: $ gsftopk zpeubi 300 gsftopk(k) version 1.19/704 [32] [33] [34] [35] [36] [37] [38] [39] [40] [41]... ... [253] [254] [255] mktexpk: zpeubi.300pk: successfully generated. Thomas
Re: pdf[la]tex problems with config
> Since my disk storage has increased from 4Gbytes to 24Gbytes, I can now > have in parallel emTeX (which has several very useful features) and TeXLive 6b contains parts of teTeX, but strictly speakingg, it is not the same. > C:\tmp>pdftex null > This is pdfTeX, Version 3.14159-pre-1.0-unofficial-20010704 (Web2c > 7.3.3.1) > (d:/emtex/texinput/null.tex It seems to me that this environment is not clean from emTeX settings. > Error: pdftex.exe (file pdftex.cfg): cannot open config file > Besides, "kpsewhich pdftex.cfg" yields nothing, while: You are calling kpsewhich without the proper flags. kpsewhich has no special detection for *.cfg files and uses teh TEXINPUTS search path. Since pdftex.cfg is not in texmf/tex//, the file is not found. Something like kpsewhich -progname=pdftex pdftex.cfg better simulates what pdftex does. > is a difference: "kpsewhich --help" says that *.cnf are searched, but > not the *.cfg. When called without proper options, kpsewhich is doing the right thing in most cases, but for the other cases, you have to be more precise. Thomas
Re: amscls docs in latest teTeX
> In the doc/latex/amscls directory, there is a thmtest.dvi file. > However, this is not very useful; it's the source file thmtest.tex, > which provides an example file of how to use the amsthm package, which > should be distributed instead. I think that I just have unzip'ed the archives that the AMS provides: ftp://ftp.ams.org/pub/tex/amsltx2.tgz In order to get this fixed, please send a bug report to them (just latex latexbug and choose amslatex category). Note, however that thmtest.tex is included in the texmfsrc tarball of teTeX (source/latex/amscls/thmtest.tex). Thomas
Re: TeX/LaTeX Fonts
> The problem I usually ran into was: > dvips -D XXX file.dvi Just don't do this. Define a printer with dpi and mode and then dvips -P... file.dvi -o (only add -o if you don't want to print). Or, if you really want "ad hoc" invocations without setting up a config.PRINTER file, then say dvips -D ... -mfmode ... file.dvi Thomas
Re: TeX/LaTeX Fonts
> Which reminds me of something that bugged be for some time (and this brings > us back to teTeX): > There is (at least was when I last looked) no [default] mode for dvips above > 600dpi. If you set up the printer the right way, you specify both mode and dpi. texconfig does it automatically for you. I don't consider it a problem to have no default mode for modes >600dpi. You should avoid these large font bitmaps anyway and use type1 fonts for printers with these resolutions. Thomas
Re: CM-Super font package v0.3.2 released
> Sorry if this is a naive question, but I would like to install > CM-super in a local-texmf tree rather than the main tree which > contains updmap. What is the step I need to take instead of > editting the updmap script? - copy updmap and the map files to your local tree - edit + run updmap - run texhash Thomas
Re: latest pdftex?
> I am wondering, why the latest tetex does not include the latest pdftex 0.14h > from > > ftp://ftp.muni.cz/pub/tex/local/cstug/thanh/pdftex/ teTeX-1.0 was released in June, 1999. At that time, there was no pdftex 0.14h. > but instead the older > > [rainer@rai21] ~$ pdflatex -v > pdfTeX (Web2C 7.3.1) 3.14159-0.14f-released-2525 This is not true. teTeX contains pdfTeX-0.13d which was the most recent pdfTeX version at that time. The latest teTeX-beta has pdfTeX, Version 3.14159-1.00a-pretest-2004-ojmw (Web2C 7.3.7) I think (guessing from your mail header) that you are using a Linux system which comes with a modified teTeX package. So, ask *them* (i.e. the people who did that Linux system) why they have just this pdfTeX version and not another... Thomas
Re: Know anything about the tetex distributed with the Cygwin toolkit?
> > I have never tried the cygwin port myself > > Since ANNOUNCE has "support for win32 systems will be added, too", > should we assume that you're that you're planning on getting it before > the next release? The cygwin ports and fpTeX are two distributions for win32 which are close to teTeX and largely compatible, too. Since the stable teTeX release was not updated for quite some time now, both win32 ports use newer sources in some places. fpTeX has native ports of scripts the origin by me (e.g. fmtutil) and there was some coordination of development in the past. So, I'd say that fpTeX is the "official" win32 port of teTeX. The cygwin port is more or less directly based on web2c (without some "teTeX"-addons). Thomas
Re: 'texconfig', 'texlinks' and multiple platforms
> 'texlinks' are run by 'texconfig' when adding a new format. On a multiple > platform installation of teTeX this isn't behaving as expected / > wanted. When I generate a new format (which is the same for all the > platforms) I expect links from format to engine to be added for _all_ > platforms - not just the one 'texconfig' / 'texlinks' is currently running > on. Since 'texlinks' has a '--multiplatform' switch I expect that the fix > is to add the switch to every occurrence of 'texlinks' in 'texconifg'. > Is that correct? > > I really think this should be the default behaviour of 'texconfig' - or at > least an option. Well, I just have done the suggested change. It will be in the next pretest. Thomas
Re: search paths for tetex
> The background for this question is the following: At ZAIK/RRZk at the > University of Cologne, we have two AFS-trees, one for writing and one > for read-and-execute-only-access, the second being replicated from the > first once per day. So installation has to go to the writable tree but > execution and including of packages has to be done from the other tree. So, just make sure that texmf.cnf has the right paths (most important: TEXMFMAIN setting). Also mage sure that at compile-time the TEXMFCNF path points to the place where the texmf.cnf file can be found at runtime. The second thing can be done by changing "TEXMFCNF = ..." in texk/kpathsea/texmf.in That's it. Thomas
Re: old tetex and new tetex problem
> >>LaTeX Warning: You have requested, on input line 23, version > >> `2000/01/15 v2.05 AMS math features' of package amsmath, Well, teTeX-1.0 which was last updated in Feb-2000 should just be recent enough for that. > (hagar) TEX : tex gentle.tex > This is TeX, Version 3.14159 (Web2C 7.3.1) > (Fatal format file error; I'm stymied) tex reads the wrong format file. It is either looking at the wrong directory or the right directory has wrong format files. Please run fmtutil --all to recreate the format files. If this does not cure the problem, run tex with KPATHSEA_DEBUG=4 (environment variable) and check that the right format file is read. > Third question: I want to keep the fonts and other files > generated in my texmf directory if we move to the new installation. Just add your old tree via TEXMF variable in the new texmf/web2c/texmf.cnf file. But, pleas put your tree *after* the main tree if it also contains old stuff. Thomas
Re: CM-Super font package v0.2.0
> I don't seem to be able to find recent versions of dvips on the net. For > instance, dvips does not seem to be on CTAN anymore. Is there a way > around downloading an entire TeX-Live image, if the only thing one needs > is dvips 5.86d ??? dvipsk-5.86d is contained in the teTeX-beta distribution which is much much smaller than TeX Live... Thomas
Re: New version (Was: neue Version)
> When is the next texfm beta coming? Are you still waiting for some > new releases of major packages - are there something that we can > do? I am currently updating the texmf tree. When this is done, I will update teTeX-beta. I am going to skip over web2c-7.3.2 and 7.3.3. The next teTeX version will contain the next web2c release. Olaf Weber has told me that a pretest version of that web2c release might be available near the end of this month. Thomas
Re: neue Version
> I want to install a new version of teTeX. > On www.tug.org/teTeX I found all file inclusive binaries but I am a little > bit surprised - > the date of all files is february 2000 or older. Is that a new version or > where can I found a newer one? If you go to the teTeX-beta area, you'll find something slightly newer (Sept. 2000). Thomas
Re: Bug in tetex1.0.7 might explain the missing tex.fmt
> I recently compiled and installed tetex on my Linux computer. > I'm not using X-Windows so i configured with: > ./configure --prefix=/usr --disable-multiplatform --without-x > make world && texconfig confall > > This fails at texconfig, a screen appears and says that it cannot find xdvi > defaults. (This I regard as a bug, when I requested an X-free install). The The xdvi defaults file is included in the texmf tarball, so your problem must be somewhere else (i.e. it is not related to your configuration choice). > around, so I had no problems. But as I was compiling with high optmization > (-O3 -march=pentium some -f's and -malign-double) > fmtutil was compiled incorectly and had a segmentation fault. Also resulting fmtutil is a shell script. > If anyone could give me a workaround regarding the xdvibug it would help me > alot. Just make sure that the texmf tarball is installed and found by the programs (e.g. just follow QuickInstall). > P.S. If anyone want the exact optmization sequence, ask me I might be able > to backtrace it. D.S. It is most likely a compiler bug. Thomas
Re: CM-Super package released
> > AFAIK the AFPL is not compatible with distribution on the TeXlive > > and CTAN cds. :-( > > i will re-release the fonts under GNU GPL in a few days. That's good. > note, however, that TeX Live and teTeX include URW fonts released under AFPL > (i.e. not from the GNU Ghostscript), and noone complains. Oops... An oversight. I will replace these fonts with the set that was released under the GNU license. Thomas BTW: some time ago, I have asked for help about finding files with license issues in teTeX. I'll append my message in case that anybody is willing to help. -- From: Thomas Esser <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Reply-to: [EMAIL PROTECTED] Subject: licenses in teTeX Dear TeX user, I have maintained teTeX for over 5 years and now I need your help in order to make it really "free software". The first step is to find all files which are not covered by a free software license. Any file covered by a license not mentioned in the list given below should be reported to [EMAIL PROTECTED] (please, do not send such reports directly to me). If you want to help, make sure to have a teTeX-beta release which is dated from 4 Aug 2000 or later. Please report any file which does not have one of these licenses: - LaTeX Project Public License (LPPL, see http://www.ctan.org/tex-archive/macros/latex/base/lppl.txt) - GPL (see http://www.gnu.org/copyleft/gpl.html) - LGPL (see http://www.gnu.org/copyleft/lgpl.html) - Public Domain (PD, see http://www.gnu.org/philosophy/categories.html#PublicDomainSoftware) - the old BSD license or the revised BSD license Other licenses might or might not be ok, so we want to find them and check them. If you want to help, please make sure you have the *original* teTeX-beta version released by me. The archives which need license checking are: ftp://ftp.dante.de/pub/tex/systems/unix/teTeX-beta/teTeX-texmf-beta-2804.tar.gz and ftp://ftp.dante.de/pub/tex/systems/unix/teTeX-beta/teTeX-texmfsrc-beta-2804.tar. gz You can find these files on other CTAN servers, too, so please use a mirror near to you. BTW: for the third teTeX tarball (teTeX-src-beta-2804.tar.gz, containing the sources for the binaries), we are quite sure that every file is covered by a free software license. Thank you for your help! Thomas Esser
Re: cannot open font map file
> I have just installed tetex from the new TeX Live 6 CD for some Unixes. ... > Warning: pdftex (file rawfonts.map): cannot open font map file > Warning: pdftex (file csfontd.mapfile): cannot open font map file > > Seemingly it doesn't hurt, but is something wrong, though? TeX Live 6 seems to have its own configuration setup for pdfTeX (pdftex.cfg) which differs from teTeX. So, please report this to the texlive bug adress. Thomas
Re: nasty bug in TL6's/tetex's mktexpk: gs died due to signal 13
> I came to the conclusion that it is not gs error (gsftopk ... > I will appreciate somebody suggesting a way to trace down > the bug. The bug is in gs. Just look at http://www.math.berkeley.edu/~vojta/gsftopk.html and http://www.math.berkeley.edu/~vojta/gsftopk-details.html Thomas
Re: strange destination directory for generated pk-fonts
> TEXMF = {$TEXMFLOCAL,$TEXMFGROUP,!!$TEXMFWWU,!!$TEXMFMAIN}
> SYSTEXMF = $TEXMFWWU;$TEXMFMAIN
...
> pk-fonts generated from mf-sources, which lie in the TEXMFWWU or TEXMFMAIN tree,
> are stored in the VARTEXFONTS directory.
right.
> But pk-fonts generated from mf-sources, which lie in the TEXMFGROUP tree, are
> stored in the working directory (eg ./dev600/name.pk), when the TEXMFGROUP
> directory is not writable for the user. If TEXMFGROUP is writable the pk-fonts
> are stored in TEXMFGROUP.
> Why aren't they stored in the VARTEXFONTS directory?
Just add $TEXMFGROUP to the SYSTEXMF variable. The idea is that SYSTEXMF
defines the "system areas" and the rest is "user area". Fonts from the
"user area" should not be put into a global tree such as VARTEXFONTS.
Thomas
Re: new tetex release?
> Is there a new tetex release on it's way? If yes is there any time > horizon on it? Well, I plan the next release to happen after the next web2c release. That might be near the end of this year. Thomas
Re: can't add hyphenation pattern
> this is probably simple, but I don't find the cause of the problem: I > wanted to add hyphenation patterns for spanish to the LaTeX on my system run fmtutil --byfmt latex and see if the format is generated successfully and where it is stored. Then, run latex with env-var KPATHSEA_DEBUG=4. If this picks up a differnt format file, you have a search path problem. Thomas
