Werner Lemberg wrote, quoting Bernd Warken:
>> With these troubles `make check' cannot be recommended.
>
> Yep. It should be disabled completely. Can you do that?
Hmm. IIRC, `make check' is a mandatory target for GCS compliance;
as a GNU Project, we should keep the `check' rule in the Makefiles
In the new groffer update, there are some new programs that transform
`roff' input into different formats:
`roff2dvi' prints dvi format to standard output,
`roff2html' generates html output,
`roff2pdf' outputs pdf mode,
`roff2ps' produces PostScript output,
`roff2text' generates text output in the
Hi,
Bernd Warken wrote:
> With the availability of these programs, it is no longer necessary to
> provide PostScript output for the `groff' example files because
> everyone can easily generate these files. A suitable README file
> could be written.
I think it's still worth providing the PostScr
> as a GNU Project, we should keep the `check' rule in the Makefiles,
> even if we leave it reporting only `nothing to be done for check'.
This is what I mean with `disabling'.
Werner
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mail
On Thursday 09 November 2006 9:52 pm, Werner LEMBERG wrote:
> > as a GNU Project, we should keep the `check' rule in the Makefiles,
> > even if we leave it reporting only `nothing to be done for check'.
>
> This is what I mean with `disabling'.
Fair enough; that wasn't clear earlier, and I just wa
> Von: Ralph Corderoy <[EMAIL PROTECTED]>
> I think it's still worth providing the PostScript files because they may
> not have a system where they can get things working sufficiently to
> produce them, despite a README. Further, it's more hassle and they may
> just want a quick peruse without th
Dean Allen Provins wrote:
I need to place multiple EPS files across and down a large page (A0 or
E size).
OpenOffice presentation mode works, but it is easy to confuse files
when
placing them, resulting in missed or duplicate images. Groff
provides a
facility to place only 3 across and se
