Comment 10 for bug 26514

Revision history for this message
In , osamu (osamu) wrote : Re: Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt

On Fri, Dec 02, 2005 at 02:57:32PM +0100, Frank Küster wrote:
> Jens Seidel <email address hidden> wrote:
>
> >> Here, again, we are at a point were the debiandoc-sgml maintainers need
> >> to decide (perhaps you have, but I don't know yet):
> >>
> >> Do you want to produce PDF files only with pdflatex, or is there a
> >> reason to create them via latex/dvips/ps2pdf?
> >
> > PDF files are not created using latex/dvips/ps2pdf! (See again #321942.)
>
> So why not simply drop hyperref at all in this case?
>
> >> If yes, you should use CJKbookmarks also for DVI files, as indicated
> >> above. If not (and I recommend that), simply do not load hyperref at
> >> all when producing dvi (unless you want to distribute DVI files, too).
> >
> > Since our packages FTBFS all the time it may be a good idea to add an
> > option to debiandoc2latex to specify the further processing.
>
> Why do you think you need this? Isn't
>
> \ifpdf
> \usepackage[colorlinks=true,CJKbookmarks]{hyperref}
> \fi
>
> enough? This will ignore hyperref completely for dvi generation, and
> thus for ps generation.

Hmmm... I am lost in LaTeX world.

Current debiandoc-sgml has functionality to modify generated latex file
using messy but simple shell script called fixlatex. The default symple
one is in debiandoc-sgml but the most elaborate one is in
debian-reference.

As I reviewed this cutomized bin/fixlatex in debian-reference, I was
surprized how it grew so much.

It looks like we can add this there.

As I have been updating debiandoc-sgml, I can fix some bugs from here
too. (I have to be careful not to break previous work arounds.)
That is to fix files in tools/lib/Format in the source tree of
debiandoc-sgml and there is LaTeX.pm is good candidates. For this
issue, I do not know which is better.

My question is:

Is this issue caused by other broken package? (it seems YES.)

If this broken package is fixed, having workaround implimented cause
problem? or some missing featues? How serious?

Should all debiandoc-sgml based package get this fix?

Thanks for your help.

Osamu

PS: If either of you think having CVS access to debiandoc-sgml
(http://alioth.debian.org/projects/debiandoc-sgml/) or debian-reference
(project: qref.sourceforge.net), let me know your account there.

PS2: As I see some locale based issues such as usepackage{babel}...
this LaTeX.pm was better place to fix but I did not dare to do so back
then.

Osamu