>>>>>"Oliver" == Oliver Fischer <plexus(a)snafu.de&gt; writes: Oliver> I am going to print the lisp reference from Oliver> www.xemacs.org. Is this the current version? The pdf and Oliver> ps files on ftp are from 1999! Oliver> So I am asking myself if the dokumentation is maintained? Oliver> Didn't anything change since 1999? ;) In 21.4, probably not so much. But why don't you make the new documentation from current 21.4 and put them somewhere where we can grab them and upload them to the server?

Sure. Hm. Seems to me there are two ways to go there. One would be ordinary TeX -> DVI -> Ghostscript. The other would be pdftex. It would be nice if we could support both.

>>>>>"Oliver" == Oliver Fischer <plexus(a)snafu.de&gt; writes: Oliver> Am I right, that the Makefile must be able to run with Oliver> nearly every make in the world? Yes, it _should_, but don't worry about it. Just try to be careful about the ones you are familiar with.

BZIP2 ?= bzip2 -f -k -9 CAT = cat DVIPS ?= dvips -o GZ ?= gzip -9 MAKEINFO ?= makeinfo RM = rm -f SHELL = /bin/sh TEXI2DVI ?= texi2dvi TEXI2HTML ?= texi2html -verbose -split chapter TEXI2PDF ?= texi2pdf --verbose --pdf -b

.SUFFIXES: .html .info .texi .dvi .pdf .ps

pdf_files = \ cl.pdf \ custom.pdf \ emodules.pdf \ external-widget.pdf \ info.pdf \ lispref.pdf \ internals.pdf \ new-users-guide.pdf \ standards.pdf \ term.pdf \ termcap.pdf \ texinfo.pdf \ widget.pdf \ xemacs.pdf \ xemacs-faq.pdf ps_files = \ cl.ps \ custom.ps \ emodules.ps \ external-widget.ps \ info.ps \ lispref.ps \ internals.ps \ new-users-guide.ps \ standards.ps \ term.ps \ termcap.ps \ texinfo.ps \ widget.ps \ xemacs.ps \ xemacs-faq.ps

.PHONY: info dvi pdf

$(TEXI2DVI) $<

$(RM) *.toc *.aux *.log *.op *.cp *.cps *.fn *.fns *.bz2 $(RM) *.ky *.kys *.pg *.pgs *.tp *.tps *.vr *.vrs *.gz

$(RM) core *.dvi *.pdf *.ps

# == P D F ================================================================ # All the targets in this section are needed to transform the texinfo # documents into pdf. pdf : $(pdf_files) .texi.pdf: $(TEXI2PDF) $< xemacs.pdf : $(xemacs-srcs) $(TEXI2PDF) -I xemacs xemacs/xemacs.texi lispref.pdf : $(lispref-srcs) $(TEXI2PDF) -I lispref lispref/lispref.texi internals.pdf : $(internals-srcs) $(TEXI2PDF) -I internals internals/internals.texi new-users-guide.pdf : $(new-users-guide-srcs) $(TEXI2PDF) -I new-users-guide new-users-guide/new-users-guide.texi # == P S ================================================================== # All the targets in this section are needed to transform the texinfo # documents into ps. ps : $(ps_files) .texi.ps: $*.dvi $(DVIPS) $＠ $*.dvi xemacs.ps : $*.dvi $(DVIPS) $＠ $*.dvi lispref.ps : $*.dvi $(DVIPS) $＠ $*.dvi internals.ps : $*.dvi $(DVIPS) $＠ $*.dvi new-users-guide.ps : $*.dvi $(DVIPS) $＠ $*.dvi # == G Z I P ============================================================== gzip : $(dvi_files) $(pdf_files) $(ps_files) ＠for d in $(dvi_files) $(pdf_files) $(ps_files) ; do \ if (test ! -e $$d.gz) || (test $$d -nt $$d.gz) ; then \ echo "$$d -> $$d.gz" ; \ $(CAT) $$d | $(GZ) > $$d.gz ; \ fi \ done # == B Z I P 2 ============================================================ bzip2 : $(dvi_files) $(pdf_files) $(ps_files) ＠for d in $(dvi_files) $(pdf_files) $(ps_files) ; do \ if (test ! -e $$d.bz2) || (test $$d -nt $$d.bz2) ; then \ echo "$$d -> $$d.bz2" ; \ $(BZIP2) $$d ; \ fi \ done

>>>> "Oliver" == Oliver Fischer <plexus(a)snafu.de&gt; writes:

Sure. Hm. Seems to me there are two ways to go there. One would be ordinary TeX -> DVI -> Ghostscript. The other would be pdftex. It would be nice if we could support both.

Do you have global commit?

Do you have global commit? If so, you can just check them into the xemacs-builds module, which are all maintainer-specific, so anything goes. (There's Python, and Perl, and awk, and zsh (I mean, bash don't cut it) and what not already, a little more Perl can't hurt.) Make a new darrylo (or whatever) directory.

Never mind -- I found it. However, it's an SSH1 key. Is that OK, or do I need to use an SSH2 key (which I have)?

Sure. Hm. Seems to me there are two ways to go there. One would be ordinary TeX -> DVI -> Ghostscript. The other would be pdftex. It would be nice if we could support both.