WalaWiki content from p1k3.com
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

#### ChapbookProcess 6.1KB Permalink History Raw

 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121 WareLogging. PortableDocumentFormat. UnrequiredPoetry. = part 9, 2/20/07 = Flyering. = part 8, 8/11/06 = <[[Brennen]]> Finished it for real this time; got a proof copy and discovered a dozen minor things to fix. = part 7, 7/30/06 = <[[Brennen]]> Finally got around to doing the last little bit of work; it's now [http://www.lulu.com/content/378672 up on Lulu.com]. I'm still really not sure about the title, to be honest. It sucks, but I can't decide what else to use. * Did a quick front cover in TheGimp, cleaned things up a bit, threw in a pseudo-copyright notice. * Should probably write a real makefile. * Should probably add more real info to the front page and a description for the back cover. * Eventually might spring for an ISBN for this. * Next time I'm using real version control. Current source is at [http://p1k3.com/chapbook /chapbook]. = part 6, 4/26/06 = <[[Brennen]]> New monitor this week. Ugly but large and relatively functional. Moved from buildbook.sh to a BasicMakefile. Moved images into their own directory, and added a \graphicspath declaration: \usepackage[pdftex]{graphicx} \graphicspath{{/home/bbearnes/chapbook/images/}} This was difficult to find on Google, though I knew I'd seen it somewhere, so here is a page for the search that seemed most obvious: PdflatexGraphicxImageDirectory. Some additional tweaks. Also this week got a copy of ''LearnCalligraphy'', by MargaretShepherd. May or may not incorporate some calligraphic elements into design. = part 5 = <[[Brennen]]> My monitor flickers a lot and has stopped, mostly, displaying the color red. Also, I have a full-time job this week. Book progress has slowed accordingly, but all that's really left to do is tweak the visuals and have it printed. = part 4 = <[[Brennen]]> Switching to pdflatex in order to include PNG & JPEG files without doing a lot of conversion. Except that this looks kind of lousy. Actually it looks kind of lousy because I'm using low-res images. I think. Went back to source photos and cranked DPI way up in TheGimp; results are much improved. = part 3 = <[[Brennen]]> Some general thoughts: * LaTeX's basic verse environment leaves some things to be desired. * It would be better to generate from some more generalized / flexible format. * The "parsing" routine I use is fine for taking a block of markup and replacing the markers that bookend it along with a few special characters in the block (line endings, etc.), but for something really structured, this would get dumb in a hurry. = part 2 = <[[Brennen]]> Getting display.pl to do most of the tedious stuff (linebreaks, setting off poems in blocks) was easy, since it already handles that stuff for poetry. Slightly trickier were things like character entities and indented lines. The table of contents also required some fiddling. The current source files are a blend of quasi-HTML and some explicit LaTeX markup: * blocks become \begin{verse} ... \end{verse} blocks. * Quotes - generally represented by character entities in my original source - are now specified explicitly with , '', , or '. A better solution for at least the standard doublequotes would be translating a tag. * I replaced all & entities with \& * Dollar signs are likewise escaped: \\$ * Dashes are explicitly specified with -- (en dash) or (three hyphens) (em dash) * Added a tag to manually specify pagination. This doesn't map precisely to real pages, but it's close enough. * Added an tag to specify authors on poems in the mixed input section. * I'm currently using stuff like \hspace{3em} and \vspace{1em} for indentation and some spacing between poems. This could be automated maybe, but it produces nice output. Everything is sandwiched between files called header.tex and footer.tex: \documentclass{book} \usepackage{geometry} % dvips was necessary to get a properly sized PDF in the end \geometry{verbose,dvips,paperwidth=6in,paperheight=9in,tmargin=.5in,bmargin=.5in} \parindent=0in \author{(bpb, caeb, eb, ag)} \title{unrequired poetry} \date{march 2006} \begin{document} \maketitle \tableofcontents ''(bulk of document here)'' \end{document} My "build" process is to run a script called buildbook.sh: #!/bin/bash ./displaytex.pl source_caeb source_collab source_bpb > ./test/test.tex cd test latex test.tex && latex test.tex dvipdf test.dvi gpdf test.pdf Which runs latex twice to make sure table of contents entries are included (it uses the previous iteration's toc info) and pulls up a PDF viewer so I can see the results. = part 1 = <[[Brennen]]> A rough description as I go, just so I remember how I went about things. Options for getting the thing printed are under SelfPublishing. General info about typography, printing, design, etc. goes under BookMaking. I did a little grepping through [http://p1k3.com/archives /archives] to pull up a near-complete list of poems I've posted here (shld automate this sort of thing), then handed it off to CarolAnn. She gave me back a paper list of possibles, which I converted to a textfile: :2003/1/28 2003/1/28/turtle 2003/2/4/fiction 2003/4/15 2003/1/6 2003/7/5 2003/10/9 2003/10/16 2003/10/22 2003/12/25 2004/1/5 2004/1/12 2004/1/20 2004/1/19 2004/1/29 2004/2/2 2004/2/10 2004/2/15 2004/2/16 2004/3/23 2004/4/19 2004/6/23 2004/6/27 2004/7/4 2004/7/6 2004/9/3 2004/9/8 2004/7/12 2004/9/21 2004/9/25 2004/10/24 2004/11/9 2004/11/22 2004/12/7 2004/12/12 2004/12/17 2005/7/6 2005/8/8 2005/10/14 2005/10/22 2005/12/2 2005/12/14 2006/1/17 2006/2/1 I commented out half a dozen lines in display.pl: the call to line_parse(), the datestamp, and header/footer files. Then did this: ./displayraw.pl cat ./chapbook_list > chapbook_source This was the easiest thing because some dates are stored like 2010/12/1 and some like 2010/12/2/index, and display.pl knows the difference. Here is the [http://p1k3.com/chapbook_source chapbook_source] file that resulted. I'm going to pare the selection down, do some cleanup, and then modify line_parse() in display.pl to give me (La?)TeX instead of HTML. `