Scott Moore wrote:
Frank Heckenbach wrote:
Scott Moore wrote:
- Is the postscript or PDF suitable to be cut down to manual size ?
For example, the GCC manual is cut to 7x9 inches. Most people don't like 8.5x11" books, and the "perfect" in perfect binding occurs because the books are cut after binding, which cleans up the book considerably. I usually custom format my books for the final print size, and add "trim marks", which are marks on the 8.5x11 page that show where to cut it.
If you're building the manual yourself (`make gpc.ps' or `make gpc.pdf' in the <build>/gcc directory; requires (pdf)tex and the texinfo package), you can customize the paper size. Currently p/Make-lang.in contains `@afourpaper' (once for PS and PDF each). You could try replacing it with `@smallbook'. I haven't done this myself; according to the texinfo manual, this makes a paper size of 7 by 9.25 inch. Or by `"@pagesizes height,width"' for a completely custom size (text area, not paper size).
This is probally a trivial item. However, I should make it clear, at the risk of offending now (instead of later). If there is such work to be done, it should be done by a GNU member. I'm not offering my time, just the ability to create manuals. If you guys want 8.5x11, or some other size, thats fine. I brought it up principly because all GNU manuals I have seen are cut downs.
In the next release, I'll introduce a variable `GPC_PAGESIZE', so modifications (even if trivial) of the Makefile should no more be necessary. Something like this should work then (after configuring GPC):
cd gcc; make gpc.ps GPC_PAGESIZE=@smallbook
If there are any other things that should be "fixed" regarding the printable version, you or someone else might want to tell me. Please note that I almost exclusively use the info and html versions and rarely look at the "printed" (PS/PDF) version myself, so I don't know very well how nice or ugly it looks.
So then, hopefully, building the manual will be a simple matter of getting a GPC release and running some configure/make command (which can be automated in a script). If you set this up for yourself, you'd have the advantage of being able to build the current manual of each release whenever you want, not having to wait for someone to make a smallbook format.
- What cover art ?
So far we have the "Gnu & Blaise Pascal" drawing by Markus Gerwinski. Any objections to it?
None, but if you are talking about the one that appears in the GPC manual, it has no color. Most GNU manuals are color covers. PS, if you want full bleed (color runs to the edge), it also needs to be a cut manual (less than 8.5x11).
Since Markus also reads the list AFAIK, he might want to comment on it. I don't mind either way.
- You can use it and distribute it, in whichever form, modified or
unmodified, for any price you are able to get.
Yes, but that mainly applies to my producing "my brand" of the book. I'm proposing to use the standard GNU format and name. I.e., I don't really wish to do other than be your binder.
No problem, AFAICS, whether or not you want to mention you name as the printer/binder.
Frank