zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: zsh 5.0.0 released, finally
Date: Wed, 25 Jul 2012 22:15:40 +0100	[thread overview]
Message-ID: <20120725221540.1aebaa58@pws-pc.ntlworld.com> (raw)
In-Reply-To: <20120725205709.GA25464@ruderich.org>

On Wed, 25 Jul 2012 22:57:09 +0200
Simon Ruderich <simon@ruderich.org> wrote:
> Should we switch to the roff2ps & ps2pdf approach for the
> Doc/Makefile? Then we won't ship the doubled PDF in the doc
> package. The website needs a4 and us-letter (and their PS
> versions), so maybe something like this:
> 
>     roff2ps -ms -P-pa4 < intro.ms > intro.a4.ps && ps2pdf intro.a4.ps
>     roff2ps -ms -P-pletter < intro.ms > intro.us.ps && ps2pdf intro.us.ps

Yes, that looks OK.
 
> Is it possible to create HTML files from a roff file? My attempts
> with roff2html failed.

I've never looked at this.

Index: Doc/.distfiles
===================================================================
RCS file: /cvsroot/zsh/zsh/Doc/.distfiles,v
retrieving revision 1.11
diff -p -u -r1.11 .distfiles
--- Doc/.distfiles	14 Apr 2012 20:42:39 -0000	1.11
+++ Doc/.distfiles	25 Jul 2012 21:14:11 -0000
@@ -18,5 +18,5 @@ DISTFILES_DOC='
     *.html
     zsh.dvi
     zsh.pdf
-    intro.pdf
+    intro.a4.pdf intro.us.pdf
 '
Index: Doc/Makefile.in
===================================================================
RCS file: /cvsroot/zsh/zsh/Doc/Makefile.in,v
retrieving revision 1.50
diff -p -u -r1.50 Makefile.in
--- Doc/Makefile.in	14 Apr 2012 20:42:39 -0000	1.50
+++ Doc/Makefile.in	25 Jul 2012 21:14:11 -0000
@@ -94,7 +94,7 @@ dvi: zsh.dvi
 zsh.dvi: $(sdir)/zsh.texi
 	$(TEXI2DVI) $(sdir)/zsh.texi
 
-pdf: zsh.pdf intro.pdf
+pdf: zsh.pdf intro.a4.pdf intro.us.pdf
 .PHONY: pdf
 
 zsh.pdf: $(sdir)/zsh.texi
@@ -104,8 +104,14 @@ zsh.pdf: $(sdir)/zsh.texi
 	  PDFTEX=$(PDFETEX) $(TEXI2DVI) --pdf $(sdir)/zsh.texi; \
 	fi
 
-intro.pdf: $(sdir)/intro.ms
-	pdfroff -ms $(sdir)/intro.ms >intro.pdf
+# Use roff2ps / ps2pdf because pdfroff produces doubled output.
+intro.a4.pdf: $(sdir)/intro.ms
+	roff2ps -ms -P-pa4 < $(sdir)/intro.ms > intro.a4.ps
+	ps2pdf intro.a4.ps
+
+intro.us.pdf: $(sdir)/intro.ms
+	roff2ps -ms -P-pletter < $(sdir)/intro.ms > intro.us.ps
+	ps2pdf intro.us.ps
 
 texi: $(sdir)/zsh.texi
 .PHONY: texi


-- 
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/


  reply	other threads:[~2012-07-25 21:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120724094229.6bd93bb9@pwslap01u.europe.root.pri>
2012-07-24 15:59 ` Simon Ruderich
2012-07-24 16:11   ` Simon Ruderich
2012-07-25  9:13   ` Peter Stephenson
2012-07-25 16:48     ` Bart Schaefer
2012-07-25 20:57     ` Simon Ruderich
2012-07-25 21:15       ` Peter Stephenson [this message]
2012-07-28 13:29         ` Simon Ruderich
2012-07-28 19:48           ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120725221540.1aebaa58@pws-pc.ntlworld.com \
    --to=p.w.stephenson@ntlworld.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).