06th of Apr ‘10
Tue 19:20
work
What do I do?—Part One
One of my responsibilities at work is to maintain a bi-monthly newsletter. It’s not much, just two A4 spreads for each issue. The catch is that it must be released in four languages in addition to English. The languages are Spanish, French, German, and Italian. Not speaking any of them doesn’t help, but I’ve picked up a fair amount of each in my time here so that I can at least get the gist of what’s in front of me. Doing what I do, there are some potential nightmares when dealing with different languages in a fairly rigid layout. I spent the past year working with the existing layout to understand the nuances of each language and how much wiggle room I have in altering the leading, tracking, font sizes, etc. In an ideal world, I would simply copy and paste a translation into the corresponding text box and it would fit perfectly, creating a work that is equal in my original intention in every way but the language. Some people (my sister) think this is how it works. I’m about to tell you otherwise, and hopefully in the process, expand your appreciation for the printed word. Or at least me. Appreciate me more.
I begin by sending out a request to the contributors to send me an article. For about a month, I harass them with reminders of the due date, with increasing frequency towards the final week—much like the work of a bill collector I imagine. Once I receive them all (about 4-5 depending on the issue), I send them to a proof-reader to make sure all of the i’s are dotted and t’s are crossed. Then I have about a week to work on other, always urgent, pending work. The articles come back to me in perfect English, and I experience an increased desire to drink until intoxication every single night.
Even with a pre-designed layout, I can expect to spend a good four or five hours playing with the text. First I like to adjust the tracking (space between words), eliminate the widows (single words that drop to the next paragraph), rivers (wide white vertical lines running down a column of text), and inappropriately hyphenated words or phrases on a per paragraph basis. If I’m lucky, I’m left with something that is either a bit to short or a little to long for the space it needs to fill. This is usually corrected by increasing the spacing after each paragraph. I try not to alter the content, especially at this stage. I’ll also try to keep leading (space between lines of text) and font-sizes consistent above all, as everything is aligned to a baseline grid of 6 points. I think these are some of the most noticeable attributes of badly set copy. After about an hour of trimming, tucking, and caressing—I turn my attention back to the screen.
This is the part where I take some liberties with my position. Many times, the articles I receive are written originally in a language other than English, or by a non-native English speaker. They’re not poorly written, but the read could be a bit friendlier with some punctuation. While I stay away from changing the actual wording, I go to town with the dashes. I have a particular love of the em-dash, which comes in handy because everyone loves their run-on sentences.
Oh merciful, glorious, beautiful sun that is praise-worthy and worthy to be praised, every single day before my morning jog in the wooded trail behind the home where I dodge the heated licks of your hot hot rays!
A well placed em-dash can defuse the situation without altering the meaning or intention of the sentence.
Oh merciful, glorious, beautiful sun that is praise-worthy and worthy to be praised—every single day before my morning jog in the wooded trail behind the home where I dodge the heated licks of your hot hot rays!
It really tickles the nerd in me to see an en-dash—or even worse—a figure dash used in its place. I know nobody cares, but I actually enjoy reading about em-dash versus spaced en-dash arguments and style guides for publishing houses. Also, sites like Pain in the English.
My favorite punctuation mark of all time has to be the no-break space. It’s more of a rule than a punctuation mark really, but it exists in my glyphs palette, so it qualifies. This nifty device is used to tell the program to keep a certain set of characters together on the same line. Handy when dealing with something like bible verses (Jn 3:16-18) and French punctuation (more to come on this one.) I think I like punctuation marks because they’re so powerful, but not as overwhelming as words can be.
Though I could easily spend a whole day kerning, I do have other work to do. So, I leave it up to my typeface of choice for this particular project, which is National primarily throughout and FF Meta on occasion. The first thing I did when I came here was purchase National. The glyphset is one of the most comprehensive I’ve ever used, and I really enjoy using all of the characters, especially German.
Links to PDF files of the issues: 2008, I had no hand in, while 2009 was my first issue, and 2010 the most recent.
ICCRS Newsletter, Volume XXXIV - Number 2, March-April 2008
ICCRS Newsletter, Volume XXXV - Number 2, March-April 2009
ICCRS Newsletter, Volume XXXVI - Number 2, March-April 2010
It’s easy to redesign something for the sake of doing it, but that wouldn’t be very responsible of me. I made changes out of necessity—switching programs from Corel to Adobe, licensing typefaces, and moving production in-house. All of this ended up saving me a lot of time and effort, but most importantly money for the organization. This is just the first step in trying to produce more consistent design across print and web, especially after I’m no longer here. Among other things, I am looking forward to producing my first style-guide for an established entity. My idea of fun.
What I really want to talk about next though, is international punctuation rules, which is when things get really interesting. Seriously—that’s Part Two.
Work & Play
In a little under two weeks, what began as ‘research’ for my next big project at work turned into this. I began testing layouts for a new website to be made for the organization I’m volunteering at, and I’m not sure at what point exactly I stopped sleeping and shaving. It definitely wasn’t on my list of things to do, and I actually thought I was done with the web for a while. Regardless, it’s here now, hopefully unchanged for a long long time. I’ve learned a lot in the process, and I’ll get to that in later posts, but for now I just want to share some of the resources I’ve used. I want to make it clear that much of this is all new for me, and the result you see here is thanks to a ton of people answering questions, posting guides, and otherwise holding my hand the entire way.
First, the basic structure that sparked my interest in the first place, is found at Typogridphy. The code and css is free, written by an eighteen year-old from the UK. His mark-up is so clean and clear, that even I could understand enough to alter it to my needs. A feature that really intrigued me about Typogridphy, that I wasn’t able to resolve in the end for this site, was ‘creating vertical rhythm.’ Basically it means trying to achieve a baseline whereby everything on the page aligns. I ended up giving up on that after the first week, because I just couldn’t get the math to work. If I knew a week ago what I know now, I think I could’ve done it, but at this point I’m over it. It’s a goal to consider for the upcoming site though, so if only for that, I’ve validated my time spent on this. For myself anyway, my boss has no idea. Even though I ended up changing a lot of the css, I wanted to give credit where it was due. Also the guy is eighteen. I was probably buying flowers for a girl or some shit like that at eighteen.
The rest of my html questions were answered by visiting the World Wide Web Consortium, which reminds me of this, but is unrelated. With just the W3C site alone, you can teach yourself how to build a site in html and css.
Then, I use ExpressionEngine to manage my content. EE lets me set everything up at once, and I don’t really have to think about code again until I pull some stunt like this and redesign everything. Actually, even if I did do a redesign, I wouldn’t have to touch anything EE-specific if I really didn’t want to. Basically it bridges a lot of gaps between design and functionality, and everyone loves bridges. There are a lot of great things said by others who’ve already drunk the Kool-Aid™, so I won’t say any more on that.
Other sites I found helpful were Web Design+ (same guy of Typogridphy), Blind Text Generator, and Textism. Of course, I looked at a lot of different page sources to study how real developers were structuring their code, and achieving certain effects. I looked a lot at Subtraction.com actually, and the article written by the nice man who actually coded it.
So, with this new website, I really just hope to use it as a space to share things, and eventually last as an archive. I planned the column on the left to hold all of my own photography, writing, or whatever. The right column will hold anything I’ve found and don’t want to forget, whatever the reason. We’ll see how things go, but I’m pretty hopeful that I can keep up with something like this at a relaxed rate, now that I’ve spent the time properly building up the structure to support it. Like I’ve mentioned before, I really had to teach myself a lot through this process, and I know there are a lot of mistakes. I appreciate any criticism and suggestions, and I hope to finally get some sleep now.