I had originally planned on black for the food tables, but it bothered the crap out of me for them to be a different color than the tables. I'm weird, I know. So, white it is. Shades of white, ivory, cream, champagne, tans and of course, black.
{image from the knot.com}
Over the weekend, I started working on our invitation designs. I'm too critical for my own good, but I feel like we are making progress toward compromise. Anyway, my printer crapped out on me. I've had my HP for something like 6 years. I printed almost my entire Sr. Thesis on that thing!
I wanted another HP and did a little digging on the net to come across this AWESOME offer at Staples. For a limited time, you can trade in your old printer for a $50 credit toward any printer that is regularly priced at $199.00 or above. Luckily, the printer I wanted was not only $199 reg price, but $75.00 off! Cha-ching!

If you go to the Hermitage Staples, be warned that not all of their associates realize that you qualify for both the sale and the credit. One of the associates told me that I couldn't get the $50 credit because it was on sale. Big Spoon (he's so smart) told me to go find a sales ad. It's plain as day on the front of the ad!
I walked out of there with a $200 printer for $80! I also recycled two print cartridges toward my Staples Rewards balance.
Yay for bargain shopping!
I'm using Samba to let the Mac and Windows laptops see the printer that's attached to my Linux server. However, there's a problem with the way Samba handles job requests from both boxes - or at least the way Samba interfaces with CUPS, the program I use to actually print on the Linux server. Since version 1.2, CUPS has only accepted input from the UTF-8 character set. However, both Mac and Windows laptops were sending requests in the iso-8859 character set; because CUPS 1.3.8 couldn't translate the requests, it spewed 'CUPS-Get-Classes client-error-bad-request' errors in the access log and 'Unsupported character set "iso-8859-1"' errors in the error log every time I tried to print a test page.
I solved the problem by adding the following line as root to the end of the [global] section of my smb.conf file:
display charset = utf-8
After I put that line in and restarted Samba (using the command
/etc/init.d/samba restart
on my Linux server), everything worked just fine from both laptops. All that needs to be changed is the "display" character set in Samba; the "unix" and "dos" charsets can be left at their defaults. Test pages and graphics now print just as they're supposed to, and I now have the following output in my error log:I [16/Aug/2009:15:46:59 -0500] [Job ???] Request file type is application/octet-stream.
I [16/Aug/2009:15:46:59 -0500] [Job 622] Adding start banner page "none".
I [16/Aug/2009:15:46:59 -0500] [Job 622] Adding end banner page "none".
I [16/Aug/2009:15:46:59 -0500] [Job 622] File of type application/octet-stream queued by "sbenning".
I [16/Aug/2009:15:46:59 -0500] [Job 622] Started backend /usr/lib/cups/backend/hp (PID 24338)
I [16/Aug/2009:15:47:39 -0500] Started "/usr/lib/cups/cgi-bin/help.cgi" (pid=24388)
I [16/Aug/2009:15:47:42 -0500] [Job 622] Completed successfully.