Re: DocBook - db2pdf and db2ps problems
On Sat 17 Feb, Adam Di Carlo wrote:
> Henning Hansen <hh@2m.dk> writes:
>
> > > - Font problem, Postscript and PDF:
> > >
> > > I needed to include the 'µ' (micron) letter in my text, and this
> > > makes db2pdf and db2ps (dvips to be more exact) ask for a font file
> > > called lbmr.pfb. It's not there, and while the letter will be left
> > > out in the PDF output, the Postscript file contains no text at all
> > > because of this.
>
> Ah. This is bug#39711 and is fixed in a rejected upload of JadeTeX.
> I'll re-upload it, but you'll have to force \@ifpackageloaded{lucidabr}
> to fail. I think it runs by default in tetex even though the actual
> pfb files are non-free and not included.
>
> Would it be possible to send me a *small* docbook SGML file that has
> these characters? I'd like to follow up with this -- I think there's
> a tetex bug here that it's enabling the lucidabr font package by
> default.
I don't think a complete file will be needed, all that matters is that
if I have a 'µ' character in the text, I will get no Postscript output.
The .tex file will still contain the 'µ' character as it is, and dvips
will report the following and create Postscript output with no text:
This is dvips(k) 5.86 Copyright 1999 Radical Eye Software (www.radicaleye.com)
' TeX output 2001.02.21:0921' -> _test.ps
<texc.pro><8r.enc><texps.pro><special.pro><color.pro>. <lbmr.pfb>This is DVIPS,
t1part module
lbmr.pfb: No such file or directory
I get the same result if I replace 'µ' by 'µ' but one solution is
to use 'μ' or '&mgr;' instead. In the .tex file, they will have been
translated into '\Character{956}' which will end up being printed out
from Postscript as a correct 'µ' symbol.
However, using 'μ' or '&mgr;' with ps2html means the \Character{956}
ends up as 'μ' im my HTML files, which my browser doesn't like and
simply displays as '&956;'.
So, here is my current solution.
I define the following entities in the <!DOCTYPE header (when creating
Postscript, the INCLUDE and IGNORE must be swapped):
<!entity % html "INCLUDE">
<!entity % postscript "IGNORE">
Then to get the 'µ' output as desired for both HTML and Postscript, I
type the following in the text:
<![%html;[ µ ]]>
<![%postscript;[ μ ]]>
It works - but it should not be neccesary ?
>
> > > - BeginPage tag:
> > >
> > > The <beginpage> tag does not seem to work at all, it's supposed to
> > > induce a pageshift in printed output.
> > >
> > > I have seen no mention of these problems anywhere, so I wonder if it
> > > works for everybody else, or am i the only person to actually prepare
> > > documentation for printout using docbook on Debian?
>
> Again, provide a sample file, and I can check it. May be a
> docbook-stylesheets (DSSSL) bug.
>
I have tried to put it anywhere, including in a header like the
<chapter> example in "The Definitive Guide" - nothing happens.
It's probably the stylesheet - what should I look for?
BTW, my document header looks like this, in case it matters:
<!DOCTYPE set PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
]>
Regards,
--
Henning Hansen
2M ELECTRONIC A/S, MALERVEJ 10, DK-2630 TAASTRUP, DENMARK
Reply to: