Re: [Groff] groff-current fail to compile

2013-02-01 Thread Werner LEMBERG
>> 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

Re: [Groff] groff-current fail to compile

2013-02-01 Thread Peter Schaffter
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

Re: [Groff] groff-current fail to compile

2013-02-01 Thread Deri James
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

Re: [Groff] groff-current fail to compile

2013-02-01 Thread Werner LEMBERG
> 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

Re: [Groff] groff-current fail to compile

2013-02-01 Thread Werner LEMBERG
> Here is a patch with more typo fixed (with partial help from > misspellings) Applied, thanks. Werner

Re: [Groff] groff-current fail to compile

2013-01-31 Thread g . esp
- Mail original - > De: "Deri James" > À: groff@gnu.org > Cc: "g esp" , "Werner LEMBERG" > Envoyé: Vendredi 1 Février 2013 00:49:03 > Objet: Re: [Groff] groff-current fail to compile > > On Thursday 31 Jan 2013 23:10:17 g@free.

Re: [Groff] groff-current fail to compile

2013-01-31 Thread Deri James
On Thursday 31 Jan 2013 23:10:17 g@free.fr wrote: > that was better with 1.22.1 patched with diff.gz. I could compile again. > I could confirm some of the warnings new in 1.22.1 remain in cvs code. > See attached log > > Looking at font/devpdf/util/BuildFoundries were the warnings come from,

Re: [Groff] groff-current fail to compile

2013-01-31 Thread g . esp
- Mail original - > De: "Werner LEMBERG" > À: "g esp" > Cc: groff@gnu.org > Envoyé: Jeudi 31 Janvier 2013 12:44:30 > Objet: Re: groff-current fail to compile > > > >> You need more programs for compiling from the CVS than from the > >> tarball. In particular, you need a bunch of netp

Re: [Groff] groff-current fail to compile

2013-01-31 Thread Werner LEMBERG
>> You need more programs for compiling from the CVS than from the >> tarball. In particular, you need a bunch of netpbm programs which >> you obviously don't have on your machine. > > That may explain why I encounter different issues patching 1.22.1 > using groff-1.22.1-current.diff.gz. I am un

Re: [Groff] groff-current fail to compile

2013-01-31 Thread g . esp
- Mail original - > De: "Werner LEMBERG" > À: "g esp" > Cc: groff@gnu.org > Envoyé: Jeudi 31 Janvier 2013 11:12:51 > Objet: Re: groff-current fail to compile > > > > current build fail for me in doc directory with > > > > xpmtoppm ./gnu.xpm | pnmdepth 15 | \ > > pnmtops -no

Re: [Groff] groff-current fail to compile

2013-01-31 Thread Werner LEMBERG
> current build fail for me in doc directory with > > xpmtoppm ./gnu.xpm | pnmdepth 15 | \ > pnmtops -noturn -rle >gnu.eps > /bin/sh: line 1: pnmtops: command not found > /bin/sh: pnmdepth: command not found > /bin/sh: xp