Re: 2.99.7: first rc of teTeX-3.0
Thomas Esser writes: > That's ok. Just use > MF = @METAFONT@ -progname=mf > in Makefile.in. Ah, of course; thanks! Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org
Re: 2.99.7: first rc of teTeX-3.0
On Sat, Jan 08, 2005 at 04:05:16PM +0100, Jan Nieuwenhuizen wrote: > AC_CHECK_PROGS(METAFONT, mf-nowin mf mfw mfont) That's ok. Just use MF = @METAFONT@ -progname=mf in Makefile.in. Thomas
Re: 2.99.7: first rc of teTeX-3.0
Akira Kakuto writes: >> mktexfmt mf-nowin.base >> >> fails. > > mf-nowin.base is not necessary and mktexfmt mf-nowin.base will be > never called if you always invoke mf-nowin like mf-nowin > --progname=mf ... ... I understand , but why add this extra complexity, and how to guarantee that? For example, currently, for LilyPond I'm using AC_CHECK_PROGS(METAFONT, mf-nowin mf mfw mfont) Can you suggest something better? Thanks, Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org
Re: 2.99.7: first rc of teTeX-3.0
> > Please, explain why you can't use > > mf-nowin -progname=mf > > I could, but after installing tetex, and running texconfig init, > when invoking mf-nowin there is no mf-nowin.base, and > > mktexfmt mf-nowin.base > > fails. mf-nowin.base is not necessary and mktexfmt mf-nowin.base will be never called if you always invoke mf-nowin like mf-nowin --progname=mf ... ... Best regards, Akira
Re: 2.99.7: first rc of teTeX-3.0
Thomas Esser writes: > Please, explain why you can't use > mf-nowin -progname=mf I could, but after installing tetex, and running texconfig init, when invoking mf-nowin there is no mf-nowin.base, and mktexfmt mf-nowin.base fails. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org
Re: 2.99.7: first rc of teTeX-3.0
On Fri, Jan 07, 2005 at 05:29:02PM +0100, Jan Nieuwenhuizen wrote: > +mf-nowin mf-nowin- -translate-file=cp227.tcx mf.ini Please, explain why you can't use mf-nowin -progname=mf That's what the UNIX script mktexpk does. That loads mf.base. I think that mf-nowin.base is not needed, because mf / mf-nowin are compatible regarding base files. Thomas
Re: 2.99.7: first rc of teTeX-3.0
Thomas Esser writes: I would like to suggest the patch below. Jan. --- texk/web2c/fmtutil.in.orig 2005-01-07 17:19:33 +0100 +++ texk/web2c/fmtutil.in 2005-01-07 17:27:43 +0100 @@ -31,6 +31,7 @@ # metafont and metapost: mf mf - -translate-file=cp227.tcx mf.ini +mf-nowin mf-nowin- -translate-file=cp227.tcx mf.ini mpost mpost - -translate-file=cp227.tcx mpost.mp metafunmpost - -translate-file=cp227.tcx metafun.mp -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org
Re: 2.99.7: first rc of teTeX-3.0
Thomas Esser writes:
> The search path has changed. The old path was
> TEXPSHEADERS = .;$TEXMF/{dvips,pdftex,tex,fonts/type1}//
> and it *did* have the complete $TEXMF/tex// in it.
I see.
> If it is only used as a header file for dvips, just put it somewhere
> into $TEXMF/dvips. That works with any version.
Ok, I'll do that.
Thanks, again!
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
Re: 2.99.7: first rc of teTeX-3.0
Akira Kakuto writes:
>>
>> /home/janneke/cvs/savannah/lilypond/lilypond/share/lilypond/tex/source/out/music-drawing-routines.ps
>
> The directory is wrong.
So how come this works with 2.0? Btw, it is also in TEXMF/ps:
$ find ./share -follow -name music-drawing-routines.ps
./share/lilypond/tex/source/out/music-drawing-routines.ps
./share/lilypond/tex/tex-out/music-drawing-routines.ps
./share/lilypond/ps/music-drawing-routines.ps
but that might not be of interest.
> You have the ps header in TEXINPUTS directory.
> Files of type kpse_tex_ps_header_format are searched under
> TEXPSHEADERS = .;$TEXMF/{dvips,fonts/{enc,type1,type3}}//
Hmm, ok. That is only a small problem, because dvips is already
symlinked to another directory.
The problem will be with installations that upgrade tetex but not
LilyPond (before we fix the LilyPond installation).
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
Re: 2.99.7: first rc of teTeX-3.0
> Is this a new feature, or has the layout/location of the PostScript
> header path changed?
The search path has changed. The old path was
TEXPSHEADERS = .;$TEXMF/{dvips,pdftex,tex,fonts/type1}//
and it *did* have the complete $TEXMF/tex// in it.
> How do we get this to work with tetex-2.0 and tetex-3.0 without
> resorting to environment variable trickery?
If it is only used as a header file for dvips, just put it somewhere
into $TEXMF/dvips. That works with any version.
Thomas
Re: 2.99.7: first rc of teTeX-3.0
3.0
> $ kpsewhich music-drawing-routines.ps
>
> /home/janneke/cvs/savannah/lilypond/lilypond/share/lilypond/tex/source/out/music-drawing-routines.ps
The directory is wrong. You have the ps header in TEXINPUTS directory.
Files of type kpse_tex_ps_header_format are searched under
TEXPSHEADERS = .;$TEXMF/{dvips,fonts/{enc,type1,type3}}//
--
Akira Kakuto
Re: 2.99.7: first rc of teTeX-3.0
Thomas Esser writes: > On Mon, Jan 03, 2005 at 11:37:22AM +0100, Jan Nieuwenhuizen wrote: >> dvips: ! Couldn't find header file music-drawing-routines.ps > > dvips uses the 'PostScript header' path for it (TEXPSHEADERS variable, > kpse_tex_ps_header_format from the "C" API of the kpathsea library). Is this a new feature, or has the layout/location of the PostScript header path changed? > To simulate that with kpsewhich, use > kpsewhich --format='PostScript header' music-drawing-routines.ps To avoid the endless support problems we had with [setting] the various *TEX/MF* environment variables, we have laid out the typical lilypond installation like a standard TEXMF tree, and only set TEXMF. This has proven to be a much more robust solution. The LilyPond installation is laid out thus: $ l /usr/share/lilypond/2.2.6/ dvips/ fonts/ ly/ make/ ps/ python/ scm/tex/vim/ with $ ls /usr/share/lilypond/2.2.6/ps/ lilyponddefs.ps music-drawing-routines.ps How do we get this to work with tetex-2.0 and tetex-3.0 without resorting to environment variable trickery? Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org
Re: 2.99.7: first rc of teTeX-3.0
On Mon, Jan 03, 2005 at 11:37:22AM +0100, Jan Nieuwenhuizen wrote: > dvips: ! Couldn't find header file music-drawing-routines.ps dvips uses the 'PostScript header' path for it (TEXPSHEADERS variable, kpse_tex_ps_header_format from the "C" API of the kpathsea library). To simulate that with kpsewhich, use kpsewhich --format='PostScript header' music-drawing-routines.ps Thomas
Re: 2.99.7: first rc of teTeX-3.0
Thomas Esser writes:
> As usual: please, send me feedback, even if it all just works :-)
I'm having an ever so slightly annoying problem when trying to use
tetex-3.0 with LilyPond. We include a postscript header in the dvi
which dvips cannot find, although kpsewhich can. Any ideas?
$ cat simple.tex
\special{header=music-drawing-routines.ps}
\bye
These are the commands that I ran for tetex-2.0 and tetex-3.0
echo $TEXMF
which kpsewhich
kpsewhich music-drawing-routines.ps
which dvips
dvips simple.dvi
KPATHSEA_DEBUG=1 dvips simple.dvi 2>&1 | grep music-drawing-routines
simple.tex
\special{header=music-drawing-routines.ps}
\bye
3.0:
11:24:08 [EMAIL PROTECTED]:~/lily
$ echo $TEXMF
{/home/janneke/cvs/savannah/lilypond/lilypond/share/lilypond,{!!/home/janneke/usr/pkg/tetex/share/texmf}}
11:24:09 [EMAIL PROTECTED]:~/lily
$ which kpsewhich
/home/janneke/usr/pkg/tetex/bin/kpsewhich
11:24:09 [EMAIL PROTECTED]:~/lily
$ kpsewhich music-drawing-routines.ps
/home/janneke/cvs/savannah/lilypond/lilypond/share/lilypond/tex/source/out/music-drawing-routines.ps
11:24:09 [EMAIL PROTECTED]:~/lily
$ which dvips
/home/janneke/usr/pkg/tetex/bin/dvips
11:24:09 [EMAIL PROTECTED]:~/lily
$ dvips simple.dvi
This is dvips(k) 5.94b Copyright 2004 Radical Eye Software
(www.radicaleye.com)
' TeX output 2005.01.03:1123' -> |lpr
dvips: ! Couldn't find header file music-drawing-routines.ps
11:24:09 [EMAIL PROTECTED]:~/lily
$ KPATHSEA_DEBUG=1 dvips simple.dvi 2>&1 | grep music-drawing-routines
kdebug:kpse_normalize_path (./music-drawing-routines.ps) => 0
kdebug:kpse_normalize_path (./music-drawing-routines.ps) => 0
kdebug:kpse_normalize_path
(/home/janneke/cvs/savannah/lilypond/lilypond/share/lilypond/dvips/music-drawing-routines.ps)
=> 1
kdebug:kpse_normalize_path
(/home/janneke/cvs/savannah/lilypond/lilypond/share/lilypond/fonts/type1/music-drawing-routines.ps)
=> 1
dvips: ! Couldn't find header file music-drawing-routines.ps
2.0:
$ echo $TEXMF
{/home/janneke/lily/share/lilypond/,{!!/usr/share/texmf}}
11:31:26 [EMAIL PROTECTED]:~/lilyal
$ which kpsewhich
/usr/bin/kpsewhich
11:31:26 [EMAIL PROTECTED]:~/lily
$ kpsewhich music-drawing-routines.ps
/home/janneke/lily/share/lilypond/tex/source/out/music-drawing-routines.ps
11:31:26 [EMAIL PROTECTED]:~/lily
$ which dvips
/usr/bin/dvips
11:31:26 [EMAIL PROTECTED]:~/lily
$ dvips simple.dvi
This is dvips(k) 5.92b Copyright 2002 Radical Eye Software
(www.radicaleye.com)
' TeX output 2005.01.03:1123' -> simple.ps
.
[1]
11:31:26 [EMAIL PROTECTED]:~/lily
$ KPATHSEA_DEBUG=1 dvips simple.dvi 2>&1 | grep music-drawing-routines
kdebug:kpse_normalize_path (./music-drawing-routines.ps) => 0
kdebug:kpse_normalize_path
(/home/janneke/lily/share/lilypond/tex/source/out/music-drawing-routines.ps) =>
1
kdebug:kpse_normalize_path (./music-drawing-routines.ps) => 0
kdebug:kpse_normalize_path
(/home/janneke/lily/share/lilypond/tex/source/out/music-drawing-routines.ps) =>
1
kdebug:kpse_normalize_path (.) => 0
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
Re: 2.99.7: first rc of teTeX-3.0
On Tue, Dec 28, 2004 at 08:36:21PM +0300, Vladimir Volovich wrote: > - sparc/Linux, GNU gcc-3.3.5, GNU flex 2.5.31, GNU bison 1.875d, GNU make > 3.80 Thanks. > Though, there is a bug in pdfetex which makes it impossible to use > hyperlinks in right-to-left mode. It would be very nice to have that > fixed before the release... :) Yes, I have seen that bug report. If we get a tested fix for it in one of the next days, that might get in. Otherwise, we have to live with that bug. Thomas
Re: 2.99.7: first rc of teTeX-3.0
"TE" == Thomas Esser writes: TE> As usual: please, send me feedback, even if it all just works :-) successfully compiled on: - sparc/Linux, GNU gcc-3.3.5, GNU flex 2.5.31, GNU bison 1.875d, GNU make 3.80 Though, there is a bug in pdfetex which makes it impossible to use hyperlinks in right-to-left mode. It would be very nice to have that fixed before the release... :) [bug reports were sent to tex-k, pdftex and tex-live lists] Best, v.
Re: 2.99.7: first rc of teTeX-3.0
On Tue, Dec 28, 2004 at 03:51:50PM +0100, Jan Nieuwenhuizen wrote: > Do you have an overview available of the layout changes? I think that section "Release notes for teTeX-3.0" in tetex-src-2.99.7.20041226-beta/texk/tetex/doc/TETEXDOC.pdf is what you are looking for. Thomas
Re: 2.99.7: first rc of teTeX-3.0
Thomas Esser writes: > As usual: please, send me feedback, even if it all just works :-) This compiles fine for Cygwin, I haven't tested it because I need to revise the package splitting (-base, -doc, -extra); it seems that the texmf layout changed a bit. It may take me a while to do this, as my development time slice has been decimated. Do you have an overview available of the layout changes? Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org
Re: 2.99.7: first rc of teTeX-3.0
On Tue, Dec 28, 2004 at 12:34:41PM +0100, Helmut Jarausch wrote: > It builds just fine here. Good, thanks. > But where has all that font directory related material gone? > No varfonts and 'remove global write permissions' and so on. The situation is now somewhat different than at the time the first version of texconfig was written. The TDS was not well esablished and supported everywhere, so I have seen a need to make lots of things configurable: dosnames, stripsupplier, ... I think that most people can just use the defaults for these now. Concerning the permissions / destinations, things have improved, too. Generated files are no longer mixed with font sources in the same tree and with the new TEXMFVAR variable, users have a way to specify their own tree for variable data. The default settings should work for most people, even in multi-user environments. If the directory specifies by TEXMFVAR is not writable by one user, generated fonts will go to $VARTEXFONTS. It was no easy decision to drop this part from texconfig and even though I think that there is less need to change the defaults than with previous releases, I might have missed some good reason to keep it. What do you (and other users think)? Thomas
Re: 2.99.7: first rc of teTeX-3.0
On 26 Dec, Thomas Esser wrote: > This 2.99.7 *is* the first release candidate of teTeX-3.0. Many thanks. It builds just fine here. But where has all that font directory related material gone? No varfonts and 'remove global write permissions' and so on. Helmut. -- Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany
Re: 2.99.7: first rc of teTeX-3.0
Your patch to texconfig-dialog works under irix... Ezra
Re: 2.99.7: first rc of teTeX-3.0
>> Initial tests show that font creation is going into the share/texmf tree now. >That is intentional, because TEXMFVAR points there. Font creation used to >go to the tree of the font source (if that was writable), but to fit into >the general concept, I have changed that (it can be undone by removing >"texmfvar" from the file mktex.cnf). >Is there any problem with this approach? Nope - that is what I wanted to see... Earlier pre-releases they went into texmf-dist - which did not make as much sense. Ezra
Re: 2.99.7: first rc of teTeX-3.0
On Mon, Dec 27, 2004 at 09:39:24AM +0100, Thomas Esser wrote:
> Your analysis is right, DIALOG_TERMINFO should point to
> $TEXMFMAIN/texconfig. The old script has done this and I have forgotten
> to copy that part of the code. I'll fix that.
A quick fix could be like this:
*** texconfig-dialog.broken2004-12-25 21:36:41.0 +0100
--- texconfig-dialog 2004-12-27 10:54:40.047835169 +0100
***
*** 428,433
--- 428,436
: ${TEXMFMAIN=`kpsewhich -var-value=TEXMFMAIN`}
export TEXMFCONFIG TEXMFVAR TEXMFMAIN
+ : ${DIALOG_TERMINFO=$TEXMFMAIN/texconfig}
+ : ${DIALOG_TERM=generic}
+
setupTmpDir
echo "$progname: started `date`" > $log
findDialog
Thomas
Re: 2.99.7: first rc of teTeX-3.0
On Sun, 26 Dec 2004 22:49:55 +0100, Thomas Esser <[EMAIL PROTECTED]> wrote: > This 2.99.7 *is* the first release candidate of teTeX-3.0. I am still > waiting for the final texinfo-4.8 and I think that some points in the > documentation still need a little tweaking, but: HERE WE GO! > ... > > As usual: please, send me feedback, even if it all just works :-) works well (like other 2.99.x) under FC3 here ! Thank you, Q. NGUYEN-DAI -- http://vnoss.org/forum/
Re: 2.99.7: first rc of teTeX-3.0
Ezra, thanks a lot for this early feedback (very much appreciated)! > Okay - everything compiles under irix 6.5.20m with the base compiler and make. Good. > However, texconfig does not run interactively... I believe that > tcdialog is having issues - it just exits - the problem is the > TERM/TERMINFO settings. Your analysis is right, DIALOG_TERMINFO should point to $TEXMFMAIN/texconfig. The old script has done this and I have forgotten to copy that part of the code. I'll fix that. I did not notice this bug, because I am using Linux and this has a special case to use /usr/bin/dialog instead of tcdialog. > Separate wish list... It would be useful to have > "texconfig paper" return the current setting... Hm... Sounds good. (The same is certainly true for a few other settings as well.). I'll have a look and see how much work this is. > Also - "texconfig help" indicates that one could configure the paper > size seoarately for xdvi, dvipdfm. Are these stll valid? The menu access > in texconfig does not allow these to be individually set. Here, the batch mode has more capabilities than the interactive mode. I thought it might be better to restrict the interactive tool to the most basic tasks. That way, it is easier to find the important things. > Initial tests show that font creation is going into the share/texmf tree now. That is intentional, because TEXMFVAR points there. Font creation used to go to the tree of the font source (if that was writable), but to fit into the general concept, I have changed that (it can be undone by removing "texmfvar" from the file mktex.cnf). Is there any problem with this approach? Thomas
Re: 2.99.7: first rc of teTeX-3.0
Okay - everything compiles under irix 6.5.20m with the base compiler and make.
However, texconfig does not run interactively... I believe that
tcdialog is having issues - it just exits - the problem is the
TERM/TERMINFO settings.
I see the following problems (at least):
a) In texconfig-dialog - before executing tcdialog - TERM is set to
$DIALOG_TERM and TERMINFO is set to $DIALOG_TERMINFO - neither of
which are set.
b) ncurses is configured to look in ${prefix}/share/terminfo. I
vaguely remember that at least an xterm terminfo entry was installed
in the past. There is nothing there now...
If I configure, and install the full ncurses sources tree (from
ftp.gnu.org) and copy the vt100 and xterm terminfo tree to the
expected place, texconfig works.
Therefore, the following fixes are needed...
a) set DIALOG_TERM and DIALOG_TERMINFO
b) Ensure that a terminfo database is present -- hmm I see that
${prefix}/share/texmf/texconfig contains such a database -
DIALOG_TERMINFO should point there.
After this, texconfig should work on an SGI.
Separate wish list... It would be useful to have
"texconfig paper" return the current setting...
Also - "texconfig help" indicates that one could configure the paper size
seoarately for xdvi, dvipdfm. Are these stll valid? The menu access in
texconfig does not allow these to be individually set.
I will need to test tomorrow if everything else is working... Initial
tests show that font creation is going into the share/texmf tree now.
Ezra
