print “soapbox”;

the last piece of code is here. it’s an abbreviated version of the code that was running the installation aspect of the project. the code is debugged, afaik. the concept could use more development, imho.

the essay that was printed in the zines is here. some sort of errata is a future possibility. so: what do you think about the text?

this blog documented the print “soapbox”; project, warts and all. poke around. the code should work. there are still a few zines left, in case you want one. they look like this.

i’m releasing more code. i actually took some time to clean this up so that it run under the `strict pragma’

it’s the gist of the code that i used to print the zines. it’s how the groff sources that generate the typesetting were generated. how generative is that?

its input files may have a little groff mark-up. how `little’ or how much is precisely specified around line 47. this was the original (!) code.

i like the mark-up that comes out of the other end. here’s a sample. i know that it sounds cheesy to say it, but the code has been… ciphered. this is a `hell wrld’ for that:

\h'3M'h\h'-3M'\h'4M'e\h'-4M'\h'18M'l\h'-18M'\h'7M'l\h'-7M'
\h'11M' \h'-11M'
\h'3M'w\h'-3M'\h'8M'r\h'-8M'\h'12M'l\h'-12M'\h'4M'd\h'-4M'

and here are a few pdf’s that show what the code did, does.

this is not code aesthetics in that the purpose was not to write code that could live on its own, away from the parental home. the type of software development or code writing or whatever that i’m proposing doesn’t attempt to be general purpose. for any potential users beyond myself, the code is more than gpl or whatever — it’s a gift. i would love it if someone took a look at the code, as it’s something that i wrote for a very specific purpose, ie a publication. i feel that this is code that only makes sense next to the zines that i’ve made.

one detail that’s important is names of fonts. in groff, when using a font that is not default, the user picks a name for it. this is significant because those names have to be hardcoded into the groff sources when switching fonts. this means that unless there’s some sort previous agreement, groff code is not portable between users.

for anyone who would want to take a look at my code, the footnote is that i’m for the most part only using notcourier-sans, and that `NOTCOURIER’ is the name that i chose for it. that said, my code should be portable if groff and perl are there, as it is by default in the gnu-linux thing, operating system, platform, stuff, setup. or should be

in any case, the use of nondefault fonts in groff is explained here. i rewrote part of that recipe and added the fontforge spice. as the font/devps path came up when thinking about custom paper sizes, i added an addendum as here. these are notes to myself.

the first pack of code to be released comes a bit late. this was implemented a few weeks ago in class, tech days. it went alright, even though the code wasn’t working. it’s working now, and every line should have a random character that’s vertically displaced. in the spirit of nonproductivity, i have to say that some of those characters may be the blanks between words. use you imagination to see them displaced

that day in school the idea was to stir up some some discussion on what code re-enactment could be. in general i think that the script could be used in discussions in general. more in the manual.txt file.

h (thanks!) took some pictures.
some sample pages.

this is practically the final version of essay. it was the text on the zines of the exam. there are no pdf versions of those zines. the printing had irreversible, improvisational, generative, whatever elements. the distribution is like a copy can be sent to anyone who writes, as a gift.

today i coded a buggy, one-off, inane proto-wordprocessor. don’t ask me why.

it wasn’t easy. however, beyond my cynicism i did enjoy writing code that edits that essay once again. i’ve spent a lot of time this year revising that essay:

open TEMP, "> temp.txt";
open SECTION, "< $aSection";
open HEADER, "< header.groff";
[...]
        if ($. == 1) {
             while (
) {
                 print TEMP $_;
             }
        }
[…]
rename “temp.txt”, $aSection;

this is some of what i’ve been writing:

i have an affinity for paranoia. it may be an artistic practice. paranoia may lead to disinformation. disinformation and confusion may be tools. the stuff regarding 9/11 that he mentions was actually orchestrated by a cadre of digital tree-huggers as a countermeasure. his arguments can easily be morphed into dialing the police because the self-mediating neighbours are too loud. the paranoia can also turn into insomnia, and in some nights i wasn’t able to sleep thinking that they were being used to close down some sort of poetic medium in some place somewhere.

in more delicate situations, paranoia is just common sense. sometimes it may be better to fall prey to its apparent paralysis and disappear. hopefully disappearance is still possible.

draft is using a beta version of the notCourier font. adding fonts to groff is a bit of a hack. just to be on the safe side, i’m posting a pdf not a ps, because i haven’t really tested it. here’s the groff source anyway. it uses my personal naming convention for fonts. but of course

* edit: this is all very fuzzy. what’s the algebra of fonts in groff? if one can add fonts, can one divide them? all i can do is stare at their names. the name i chose for inconsolata is IOOAA. maybe i will add notcourier again, and call it UNCOURIER. this would get reflected in the groff sources. this could confuse any potential maintainers, including myself. what’s the point of calling them sources, anyway?

this is the blurb that will go into the catalogue:

“the essay deals with two things: code, and self-publishing. regarding self-publishing, the focus is on zine culture of the 1980s and 1990s. if the enormous energy of print matter of those years was an afterthought of consumer computing, how does this energy segue back into technology? the essay is the text that’s printed on the laserjet zine. the zine has been designed with custom tools. in this sense, both the code and the text of the zine have been written at the command line. in this sense, the zine is being printed from scratch. the code is freely available, but has not been thoroughly tested. it may only run on my machine. on a good day, it may run on the machines of the monad, too. speaking of, do you have any code to share? do you have any bugs to report?”

this blurs the critique blurb that i had to send in advance. it’s a pure text, cleaner version of the mock show code that i still have to put up. don’t know what to make of it.