* [9fans] converting to .ps/.pdf @ 2001-02-09 19:17 ` William Staniewicz 2001-02-09 18:48 ` Scott Schwartz 0 siblings, 1 reply; 7+ messages in thread From: William Staniewicz @ 2001-02-09 19:17 UTC (permalink / raw) To: 9fans After composing a document in ACME or SAM, is this a good way to convert to a .ps file format? lp -dstdout -pppost file.txt > file.ps Taking that one step further, how can I convert to a .pdf file within Plan9? -Bill ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [9fans] converting to .ps/.pdf 2001-02-09 19:17 ` [9fans] converting to .ps/.pdf William Staniewicz @ 2001-02-09 18:48 ` Scott Schwartz 0 siblings, 0 replies; 7+ messages in thread From: Scott Schwartz @ 2001-02-09 18:48 UTC (permalink / raw) To: 9fans | Taking that one step further, how can I convert | to a .pdf file within Plan9? Use ghostscript. ^ permalink raw reply [flat|nested] 7+ messages in thread
* [9fans] macro files with troff @ 2001-02-20 3:10 ` William Staniewicz 2001-02-19 21:21 ` Scott Schwartz 0 siblings, 1 reply; 7+ messages in thread From: William Staniewicz @ 2001-02-20 3:10 UTC (permalink / raw) To: 9fans I would like to begin using troff to prepare some document files. So far, I have looked over /sys/doc/troff.ps which includes the manual and tutorial. It appears the easiest way to start is to invoke troff with a standard macro/package like -ms or -mm. The definitions for these I presume are in /sys/lib/tmac. When I begin writing the document with acme, how do I identify all the 'requests' set in the packages? For example, Would I need to look in /sys/lib/tmac/tmac.s for info on the -ms package or is there a table set up for them somewhere? Any other hints on how to begin using this would be appreciated. -Bill ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [9fans] macro files with troff 2001-02-20 3:10 ` [9fans] macro files with troff William Staniewicz @ 2001-02-19 21:21 ` Scott Schwartz 0 siblings, 0 replies; 7+ messages in thread From: Scott Schwartz @ 2001-02-19 21:21 UTC (permalink / raw) To: 9fans The Research Unix 10th Edition documentation is a good source for troff related material. ^ permalink raw reply [flat|nested] 7+ messages in thread
* [9fans] Acme definition @ 2001-03-12 5:27 ` William Staniewicz 2001-03-11 23:43 ` George Michaelson 0 siblings, 1 reply; 7+ messages in thread From: William Staniewicz @ 2001-03-12 5:27 UTC (permalink / raw) To: 9fans A friend asked me about the origin of the word "Acme". My first impulse was to consult the "OED", but not having one handy, I resorted to some online sources. Most neglected to include a reference to one of my favorite contexts: The Roadrunner cartoon (btw, while living in Texas, I actually saw one run across the street in front of my car, it actually looked like the one in the Warner Bros' series and moved like it too!). Acme n. [from Greek `akme', highest point of perfection or achievement] The canonical supplier of bizarre, elaborate, and non-functional gadgetry - where Rube Goldberg and Heath Robinson (two cartoonists who specialized in elaborate contraptions) shop. The name has been humorously expanded as A (or American) Company Making Everything. (In fact, Acme was a real brand sold from Sears Roebuck catalogs in the early 1900s.) Describing some X as an "Acme X" either means "This is insanely great", or, more likely, "This looks insanely great on paper, but in practice it's really easy to shoot yourself in the foot with it." Compare pistol. This term, specially cherished by American hackers and explained here for the benefit of our overseas brethren, comes from the Warner Brothers' series of "Roadrunner" cartoons. In these cartoons, the famished Wile E. Coyote was forever attempting to catch up with, trap, and eat the Roadrunner. His attempts usually involved one or more high-technology Rube Goldberg devices - rocket jetpacks, catapults, magnetic traps, high-powered slingshots, etc. These were usually delivered in large cardboard boxes, labeled prominently with the Acme name. These devices invariably malfunctioned in improbable and violent ways. -Bill ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [9fans] Acme definition 2001-03-12 5:27 ` [9fans] Acme definition William Staniewicz @ 2001-03-11 23:43 ` George Michaelson 0 siblings, 0 replies; 7+ messages in thread From: George Michaelson @ 2001-03-11 23:43 UTC (permalink / raw) To: 9fans The Epitome seems to embody almost all concepts Acme tried to reach for, without the downside connotations. Plus, as an added benefit, it has only one correct pronounciation but at least two plausible ones, permitting the cogniscenti to discern those of a less 'au courant' comprehension. Wiley should have learned from his mistakes. Nowadays, I suspect a smart lawyer could injunct either Acme, or the new mexico roads department, possibly both. -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [9fans] converting to .ps/.pdf @ 2001-02-09 18:15 Russ Cox 0 siblings, 0 replies; 7+ messages in thread From: Russ Cox @ 2001-02-09 18:15 UTC (permalink / raw) To: 9fans To convert PS to PDF via Ghostscript: gs -s'DEVICE=pdfwrite' -s'OutputFile=file.pdf' -r600 -dBATCH -dQUIET -dNOPAUSE file.ps Russ ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2001-03-12 5:27 UTC | newest] Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <wstan@localhostnl.demon.nl> 2001-02-09 19:17 ` [9fans] converting to .ps/.pdf William Staniewicz 2001-02-09 18:48 ` Scott Schwartz 2001-02-20 3:10 ` [9fans] macro files with troff William Staniewicz 2001-02-19 21:21 ` Scott Schwartz 2001-03-12 5:27 ` [9fans] Acme definition William Staniewicz 2001-03-11 23:43 ` George Michaelson 2001-02-09 18:15 [9fans] converting to .ps/.pdf Russ Cox
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).