>> Either the document can use only the base 14 fonts, or the document
>> should set #ABORT_FT_ERRORS to zero, which appears to allow MOM not
>> to abort on font errors. Peter can decide. :-)
>
> Better, I think, to use the base 14 fonts. I hadn't realized there
> was an issue with New Century S
On Fri, Feb 01, 2013, Deri James wrote:
> On Friday 01 Feb 2013 09:22:25 Werner LEMBERG wrote:
> > Deri, Peter, any ideas how teo fix this? Maybe
> > guarding this part in `typesetting.mom' with an if-clause which tests
> > the availability of font family `N'?
> >
> >
> > Werner
>
> Either
> Von: "walter harms"
>
> Am 01.02.2013 01:39, schrieb Bernd Warken:
> > I have a man-page with a table that is 3 pages long. It works when
> > I split it in 3 parts and call .TS/.TE for each.
> >
> > I would prefer to use hdtbl. You mention in groff_hdtbl(7) a
> > macro that can go over sever
Am 01.02.2013 01:39, schrieb Bernd Warken:
> I have a man-page with a table that is 3 pages long. It works when
> I split it in 3 parts and call .TS/.TE for each.
>
> I would prefer to use hdtbl. You mention in groff_hdtbl(7) a
> macro that can go over several pages, but that works only in ms.
On Friday 01 Feb 2013 09:22:25 Werner LEMBERG wrote:
> Deri, Peter, any ideas how teo fix this? Maybe
> guarding this part in `typesetting.mom' with an if-clause which tests
> the availability of font family `N'?
>
>
> Werner
Either the document can use only the base 14 fonts, or the docume
> I could confirm some of the warnings new in 1.22.1 remain in cvs
> code. See attached log
The warnings
examples/mom-pdf.mom:6: can't transparently output node at top level
are expected, AFAIK. I can imagine that make emits a line:
expect some warnings about `output nodes'
as a guide
> Here is a patch with more typo fixed (with partial help from
> misspellings)
Applied, thanks.
Werner
