Re: Problems with PDF creation
Osamu Aoki [EMAIL PROTECTED] wrote: On Mon, Jun 26, 2006 at 10:17:20AM +0200, Frank Küster wrote: Osamu Aoki [EMAIL PROTECTED] wrote: Wait, there is less than 70MB of PDF. Yes, this is true. Due to difficulties of making nice PDF out of XML/SGML without hitting FTBFS, many packages does not bother PDF creation. Most of the doc containing PDF are: Can you please be more specific about difficulties ... nice ... FTBFS? There have been some problems when teTeX 3.0 was uploaded to sid after sarge's release, but that was a one-time problem (and the central packages like debiandoc-smgl, linuxdoc etc. were fixed quite fast; db2latex was harder). Do you imply that people stopped generating PDF files last summer/autumn because of these problems? That pretty much it. And which packages are affected? Or are there other problems I am not aware of? doc-debian used to loop 6 times to build PDF. If a LaTeX document is complex, this can be in fact needed (although I've never seen anything needing more than 4 repetitions). It could also be a problem of the build system. In any case it has nothing to do with the fact that the sourceis xml/sgml, except maybe that there might be suboptimal converters involved. Many Debiandoc packages did not contain PDF for cjk. cjk is still a problem, that's right. I hope I'll be able to sponsor an upload of latex-cjk soon. New build script is much more stable. Sorry, which build script are you talking about? doc-debian's? Then how is this a problem for generating PDF from xml/sgml sources? I know some package build PDF first as upstream. Sorry, I don't understand what you want to say. I fupdown does not come with documentation. ? It does contain documentation in form of example text files. If that's not enough, that's a problem of content, not of the format, isn't it? Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX)
Re: Problems with PDF creation
Osamu Aoki [EMAIL PROTECTED] wrote: cjk is still a problem, that's right. I hope I'll be able to sponsor an upload of latex-cjk soon. Please. I did few minor NMU to get it to etch. I thought Anthony Fok is back in action. Yes, he is, but Danai Sae-Han is taking over the package. I know current effort of moving developer-reference to XML is only for HTML and plain text. There seem to be issues with building PDF from UTF-8. Talk to W. Borgert [EMAIL PROTECTED] on this subject. Yes, I'll do that. I know some package build PDF first as upstream. Sorry, I don't understand what you want to say. I saw sometime ago, some package had non-PDF source, and PDF file as a part of source. Then build of the source package just moved PDF to binary package. I think this is okay to save some build time as long as it has been checked that building does indeed work. Many upstream LaTeX documents require the correct order and number of invocations of latex, bibtex, makeindex, etc., and often there is no build infrastructure for that. Look into the source package and run make ifupdown.pdf (yep you need few more dependancy application installed like dia. ) Thanks, I'll check that. Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX)
Re: Problems with PDF creation
On Tue, Jun 27, 2006 at 12:28:15PM +0200, Frank Küster wrote: Osamu Aoki [EMAIL PROTECTED] wrote: On Mon, Jun 26, 2006 at 10:17:20AM +0200, Frank Küster wrote: Osamu Aoki [EMAIL PROTECTED] wrote: Wait, there is less than 70MB of PDF. Yes, this is true. Due to difficulties of making nice PDF out of XML/SGML without hitting FTBFS, many packages does not bother PDF creation. Most of the doc containing PDF are: Can you please be more specific about difficulties ... nice ... FTBFS? There have been some problems when teTeX 3.0 was uploaded to sid after sarge's release, but that was a one-time problem (and the central packages like debiandoc-smgl, linuxdoc etc. were fixed quite fast; db2latex was harder). Do you imply that people stopped generating PDF files last summer/autumn because of these problems? That pretty much it. And which packages are affected? Sorry, I can not be specific. That is my old memory. Let's move on. :) Or are there other problems I am not aware of? doc-debian used to loop 6 times to build PDF. If a LaTeX document is complex, this can be in fact needed (although I've never seen anything needing more than 4 repetitions). It could also be a problem of the build system. In any case it has nothing to do with the fact that the sourceis xml/sgml, except maybe that there might be suboptimal converters involved. Many Debiandoc packages did not contain PDF for cjk. cjk is still a problem, that's right. I hope I'll be able to sponsor an upload of latex-cjk soon. Please. I did few minor NMU to get it to etch. I thought Anthony Fok is back in action. New build script is much more stable. Sorry, which build script are you talking about? doc-debian's? That what I meant. we fixed it by updating debiandoc-sgml. Anyway, that was non-trivial work for SGML DOC maintainer without LaTeX knowledge. Then how is this a problem for generating PDF from xml/sgml sources? That is history now. The point is if you think about building PDF from source, you are pulling huge amount of packages. That is major headache. I think people scream when GCC upgrades and cough on some programs. Similar situation is what might have happened with DOC package and TeX. I think TeX is maintained well in par with GCC. But Debian release cycle is mostly dictated by Kernel/GCC/glibc/X/gtk/gnome/Qt/... So current policy not to be FTBFS even for DOC package is tough one. (I think we need to have reasonable exceptions for DOC package. If it build with previous stable release, it should be allowed to be published. I know current effort of moving developer-reference to XML is only for HTML and plain text. There seem to be issues with building PDF from UTF-8. Talk to W. Borgert [EMAIL PROTECTED] on this subject. I know some package build PDF first as upstream. Sorry, I don't understand what you want to say. I saw sometime ago, some package had non-PDF source, and PDF file as a part of source. Then build of the source package just moved PDF to binary package. I fupdown does not come with documentation. ? It does contain documentation in form of example text files. If that's not enough, that's a problem of content, not of the format, isn't it? Look into the source package and run make ifupdown.pdf (yep you need few more dependancy application installed like dia. ) Regards, Frank Osamu
Re: Problems with PDF creation
On Tuesday 27 June 2006 17:07, Frank Küster wrote: Osamu Aoki [EMAIL PROTECTED] wrote: I know current effort of moving developer-reference to XML is only for HTML and plain text. There seem to be issues with building PDF from UTF-8. Talk to W. Borgert [EMAIL PROTECTED] on this subject. Yes, I'll do that. I'm very interested too (for the Installation Guide). pgpbvbRNQQPY2.pgp Description: PGP signature
Re: Problems with PDF creation
Frank Küster [EMAIL PROTECTED] wrote: Look into the source package and run make ifupdown.pdf (yep you need few more dependancy application installed like dia. ) Thanks, I'll check that. There's no LaTeX- or PDF-specific reason not to build the documentation. It builds without changing anything, just call the respective target. There are some cosmetic issues with the output, though. I've submitted a patch to the BTS. Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX)
Re: Problems with PDF creation
Frans Pop [EMAIL PROTECTED] wrote: On Tuesday 27 June 2006 17:07, Frank Küster wrote: Osamu Aoki [EMAIL PROTECTED] wrote: I know current effort of moving developer-reference to XML is only for HTML and plain text. There seem to be issues with building PDF from UTF-8. Talk to W. Borgert [EMAIL PROTECTED] on this subject. Yes, I'll do that. I'm very interested too (for the Installation Guide). Does that mean that you *do* encounter problems? Which? Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX)
Re: Problems with PDF creation
Frank Küster wrote:
Frank Küster [EMAIL PROTECTED] wrote:
Look into the source package and run make ifupdown.pdf (yep you need few
more dependancy application installed like dia. )
Thanks, I'll check that.
There's no LaTeX- or PDF-specific reason not to build the
documentation. It builds without changing anything, just call the
respective target. There are some cosmetic issues with the output,
though. I've submitted a patch to the BTS.
And if you do not want to check how many times you need to run latex/
pdflatex/bibtex/... or if you do not want to look manually for the
correct dependencies between .tex, .dvi, .ps, .bib, .bbl, ... you can
apply this patch (but this add a build-depends on latex-make)
Best regards,
Vincent
--- Makefile.orig 2006-06-27 19:58:43.0 +0200
+++ Makefile 2006-06-27 20:02:53.0 +0200
@@ -25,7 +25,7 @@
install -m 0755 ifup ${BASEDIR}/sbin
ln ${BASEDIR}/sbin/ifup ${BASEDIR}/sbin/ifdown
-clean :
+clean ::
rm -f *.aux *.toc *.log *.bbl *.blg *.ps *.eps *.pdf
rm -f *.o *.d $(patsubst %.defn,%.c,$(DEFNFILES)) *~
rm -f $(patsubst %.defn,%.man,$(DEFNFILES))
@@ -35,7 +35,8 @@
clobber : clean
rm -f ifupdown.tex $(PERLFILES) $(CFILES) $(HFILES) $(DEFNFILES)
-distclean : clobber
+distclean :: clobber
+distclean ::
rm -f makecdep.sh makenwdep.sh Makefile
ifup: $(OBJ)
$(CC) $(CFLAGS) $^ $(LDFLAGS) $(OUTPUT_OPTION)
@@ -59,20 +60,9 @@
%.tex : %.nw
noweave -delay -index -latex $ $@
-%.bbl : %.tex biblio.bib
- latex $
- bibtex $(basename $)
-
-%.dvi : %.tex %.bbl
- latex $
- latex $
-
-%.pdf : %.tex %.bbl
- pdflatex $
- pdflatex $
-
-%.ps : %.dvi
- dvips -o $@ $
+LU_MASTERS=ifupdown
+LU_FLAVORS=PS PDF
+include LaTeX.mk
%.gz : %
gzip --best --stdout $ $@
Re: Problems with PDF creation
On Tuesday 27 June 2006 20:06, Frank Küster wrote: Frans Pop [EMAIL PROTECTED] wrote: On Tuesday 27 June 2006 17:07, Frank Küster wrote: Osamu Aoki [EMAIL PROTECTED] wrote: I know current effort of moving developer-reference to XML is only for HTML and plain text. There seem to be issues with building PDF from UTF-8. Talk to W. Borgert [EMAIL PROTECTED] on this subject. Yes, I'll do that. I'm very interested too (for the Installation Guide). Does that mean that you *do* encounter problems? Which? Oops. Sorry. No, we don't have problems building PDF from UTF-8, but we use a somewhat roundabout method [1]. What I meant is that I'm very interested in having CJK (and better Greek and Russian) support for building PDFs. Cheers, FJP [1] We use openjade and jadetex to generate a DVI file from the docbook XML, and then generate the PDF from the DVI file using dvipdf. pgpF6XkgHcJOq.pgp Description: PGP signature
Re: Problems with PDF creation (was: Why does doc packages need to contain gzipped files?)
On Mon, Jun 26, 2006 at 10:17:20AM +0200, Frank Küster wrote: Osamu Aoki [EMAIL PROTECTED] wrote: Wait, there is less than 70MB of PDF. Yes, this is true. Due to difficulties of making nice PDF out of XML/SGML without hitting FTBFS, many packages does not bother PDF creation. Most of the doc containing PDF are: Can you please be more specific about difficulties ... nice ... FTBFS? There have been some problems when teTeX 3.0 was uploaded to sid after sarge's release, but that was a one-time problem (and the central packages like debiandoc-smgl, linuxdoc etc. were fixed quite fast; db2latex was harder). Do you imply that people stopped generating PDF files last summer/autumn because of these problems? That pretty much it. Or are there other problems I am not aware of? doc-debian used to loop 6 times to build PDF. Many Debiandoc packages did not contain PDF for cjk. New build script is much more stable. I know some package build PDF first as upstream. I fupdown does not come with documentation. ...
