[6518] in APO Printshop
Fwd: Wedding Invitation Design Draft
daemon@ATHENA.MIT.EDU (Andrew Farrell)
Wed Mar 21 05:57:37 2012
In-Reply-To: <CAPadfSAh7KNVtutHJgo6UbJBGQK88zZcze8v1+2tfuopzSJehQ@mail.gmail.com>
From: Andrew Farrell <afarrell@MIT.EDU>
Date: Wed, 21 Mar 2012 05:57:02 -0400
To: apo-printshop <apo-printshop@mit.edu>
--f46d0442879efbd79204bbbdd19c
Content-Type: text/plain; charset=ISO-8859-1
this correspondence took place.
---------- Forwarded message ----------
From: Jen Selby <jenselby@gmail.com>
Date: Wed, Mar 21, 2012 at 5:26 AM
Subject: Re: Wedding Invitation Design Draft
To: Andrew Farrell <afarrell@mit.edu>
Cc: Nick Martin <nim@nimlabs.org>
Thanks! Good luck with Conclave.
On Mar 21, 2012 2:13 AM, "Andrew Farrell" <afarrell@mit.edu> wrote:
> Oh sorry. yes. I'm planning on looking at this after conclave
> (I'm one of the conclave chairs)
>
> On Wed, Mar 21, 2012 at 4:48 AM, Jen Selby <jenselby@gmail.com> wrote:
>
>> Hi Andrew,
>>
>> I'm getting a little nervous since I haven't heard anything in the
>> past two weeks. If you haven't had time yet to look over the drafts
>> and supplies, that's fine, but can you just ack this email so that I
>> know that you've been getting these?
>>
>> YiLFS,
>> Jen
>>
>> On Sun, Mar 18, 2012 at 11:51 PM, Jen Selby <jenselby@gmail.com> wrote:
>> > Hi Andrew,
>> >
>> > Here are the updated drafts of our layout. There were a few wording
>> > changes, and a number of changes in where we placed the linebreaks.
>> >
>> > Let us know if you have any questions, or if there is anything we
>> > should change based on the supplies the print shop has on hand.
>> >
>> > We would like to have these by early April, if possible.
>> >
>> > Jen Selby
>> >
>> > On Tue, Mar 6, 2012 at 12:09 AM, Jen Selby <jenselby@gmail.com> wrote:
>> >> Hi Andrew,
>> >>
>> >> I'm sorry I'm getting this to you a little later than I promised, but
>> >> I hope it's still early enough that you'll be able to print these up
>> >> over spring break, as you hoped. This is our first draft of the
>> >> layout. Please let us know of anything that would be difficult to lay
>> >> out nicely. We're happy to make changes. We'll send an updated version
>> >> after we get feedback from some other people.
>> >>
>> >> Since (sadly) Nick and I use HTML/CSS more often than LaTeX these
>> >> days, we used that to lay out the designs. I'm including a PDF (to
>> >> skirt browser display issues) as well as the HTML and CSS source
>> >> files, in case those are useful for getting details of some of the
>> >> layout choices. We don't recommend viewing the HTML file in a browser
>> >> to look at the layout :)
>> >>
>> >> We'd like 225 of each piece.
>> >>
>> >> For the paper, we're looking for something in the ivory-buttercup
>> >> yellow spectrum. We based the layout sizes on standard (I hope)
>> >> Baronial envelopes -- Lee for the large envelope and Baronial 4 for
>> >> the reply card. For ink, we were thinking of something like Pantone
>> >> 5615 (dark green), but a brown or black would be OK as well. I'd like
>> >> to stress that we are not super picky about either sizes or colors,
>> >> and as long as there is something close, we'd rather go with something
>> >> you have in stock than wait for an order to come in.
>> >>
>> >> Our names should be in TypoScript 24. Most of the rest of the text is
>> >> Garamond 14 or 18, except for the numbers in the password, because
>> >> Garamond zeros look too much like lowercase zeros. Any reasonable
>> >> distinct zero character should be fine to use instead. We also noticed
>> >> that you don't have bold-weight Garamond, which we used in our layout.
>> >> Do you have any suggestions for what we could do instead to make the
>> >> dates stand out a bit?
>> >>
>> >> We grabbed a random image for the APO logo. I assume you have
>> >> something you can use for that.
>> >>
>> >> The border image is meant to stand in for the leafy border pieces that
>> >> I saw when I visited. We may be really off on the size of those pieces
>> >> relative to the text, in which case we can adjust our layout
>> >> accordingly.
>> >>
>> >> Jen
>>
>
>
--f46d0442879efbd79204bbbdd19c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
this correspondence took place.<br><br><div class=3D"gmail_quote">---------=
- Forwarded message ----------<br>From: <b class=3D"gmail_sendername">Jen S=
elby</b> <span dir=3D"ltr"><<a href=3D"mailto:jenselby@gmail.com">jensel=
by@gmail.com</a>></span><br>
Date: Wed, Mar 21, 2012 at 5:26 AM<br>Subject: Re: Wedding Invitation Desig=
n Draft<br>To: Andrew Farrell <<a href=3D"mailto:afarrell@mit.edu">afarr=
ell@mit.edu</a>><br>Cc: Nick Martin <<a href=3D"mailto:nim@nimlabs.or=
g">nim@nimlabs.org</a>><br>
<br><br><p>Thanks! Good luck with Conclave.</p><div class=3D"HOEnZb"><div c=
lass=3D"h5">
<div class=3D"gmail_quote">On Mar 21, 2012 2:13 AM, "Andrew Farrell&qu=
ot; <<a href=3D"mailto:afarrell@mit.edu" target=3D"_blank">afarrell@mit.=
edu</a>> wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Oh sorry. yes. I'm planning on looking at this after conclave<div>(I=
9;m one of the conclave chairs)<br><br><div class=3D"gmail_quote">On Wed, M=
ar 21, 2012 at 4:48 AM, Jen Selby <span dir=3D"ltr"><<a href=3D"mailto:j=
enselby@gmail.com" target=3D"_blank">jenselby@gmail.com</a>></span> wrot=
e:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Andrew,<br>
<br>
I'm getting a little nervous since I haven't heard anything in the<=
br>
past two weeks. If you haven't had time yet to look over the drafts<br>
and supplies, that's fine, but can you just ack this email so that I<br=
>
know that you've been getting these?<br>
<br>
YiLFS,<br>
Jen<br>
<div><div><br>
On Sun, Mar 18, 2012 at 11:51 PM, Jen Selby <<a href=3D"mailto:jenselby@=
gmail.com" target=3D"_blank">jenselby@gmail.com</a>> wrote:<br>
> Hi Andrew,<br>
><br>
> Here are the updated drafts of our layout. There were a few wording<br=
>
> changes, and a number of changes in where we placed the linebreaks.<br=
>
><br>
> Let us know if you have any questions, or if there is anything we<br>
> should change based on the supplies the print shop has on hand.<br>
><br>
> We would like to have these by early April, if possible.<br>
><br>
> Jen Selby<br>
><br>
> On Tue, Mar 6, 2012 at 12:09 AM, Jen Selby <<a href=3D"mailto:jense=
lby@gmail.com" target=3D"_blank">jenselby@gmail.com</a>> wrote:<br>
>> Hi Andrew,<br>
>><br>
>> I'm sorry I'm getting this to you a little later than I pr=
omised, but<br>
>> I hope it's still early enough that you'll be able to prin=
t these up<br>
>> over spring break, as you hoped. This is our first draft of the<br=
>
>> layout. Please let us know of anything that would be difficult to =
lay<br>
>> out nicely. We're happy to make changes. We'll send an upd=
ated version<br>
>> after we get feedback from some other people.<br>
>><br>
>> Since (sadly) Nick and I use HTML/CSS more often than LaTeX these<=
br>
>> days, we used that to lay out the designs. I'm including a PDF=
(to<br>
>> skirt browser display issues) as well as the HTML and CSS source<b=
r>
>> files, in case those are useful for getting details of some of the=
<br>
>> layout choices. We don't recommend viewing the HTML file in a =
browser<br>
>> to look at the layout :)<br>
>><br>
>> We'd like 225 of each piece.<br>
>><br>
>> For the paper, we're looking for something in the ivory-butter=
cup<br>
>> yellow spectrum. We based the layout sizes on standard (I hope)<br=
>
>> Baronial envelopes -- Lee for the large envelope and Baronial 4 fo=
r<br>
>> the reply card. For ink, we were thinking of something like Panton=
e<br>
>> 5615 (dark green), but a brown or black would be OK as well. I'=
;d like<br>
>> to stress that we are not super picky about either sizes or colors=
,<br>
>> and as long as there is something close, we'd rather go with s=
omething<br>
>> you have in stock than wait for an order to come in.<br>
>><br>
>> Our names should be in TypoScript 24. Most of the rest of the text=
is<br>
>> Garamond 14 or 18, except for the numbers in the password, because=
<br>
>> Garamond zeros look too much like lowercase zeros. Any reasonable<=
br>
>> distinct zero character should be fine to use instead. We also not=
iced<br>
>> that you don't have bold-weight Garamond, which we used in our=
layout.<br>
>> Do you have any suggestions for what we could do instead to make t=
he<br>
>> dates stand out a bit?<br>
>><br>
>> We grabbed a random image for the APO logo. I assume you have<br>
>> something you can use for that.<br>
>><br>
>> The border image is meant to stand in for the leafy border pieces =
that<br>
>> I saw when I visited. We may be really off on the size of those pi=
eces<br>
>> relative to the text, in which case we can adjust our layout<br>
>> accordingly.<br>
>><br>
>> Jen<br>
</div></div></blockquote></div><br></div>
</blockquote></div>
</div></div></div><br>
--f46d0442879efbd79204bbbdd19c--
