We also need to get some sanity with hyphenation and re-flow, and, I am disappointed that my reader doesn't seem to do a good job of kerning, or do ligatures at all.
Disclaimer: I am a technical writer, and have a lot of experience with publishing workflows.
I love the ease of obtaining books for my e-book reader. I also love the space savings I get from e-books and not having to choose which physical book to dispose of when I get a new one.
Given good content to work with, any programmer could figure out how to make it beautiful using LaTeX. There are even several excellent packages for typesetting novels out there on CTAN. However, there isn't a mature, standardized workflow to get from LaTeX to epub. I sort of expected this by now. It'd be nice if XeLaTeX had an output driver for epub. Everything on planet LaTeX revolves around PDF output, and it doesn't do tagged PDF output, which means that paragraphs cannot be reflowed. So, you can generate a beautiful document for your e-book reader, as long as you don't plan to zoom, and you have to generate a different PDF file for every size of device out there.
That's not to say that LaTeX and friends haven't come a long way. Synctex and TeXworks make editing a joy. XeTeX and fontspec make font selection easy-cheesy.
However, I pine for the day when I can just do epublatex document.tex or taggedpdflatex document.tex and get awesome output. I don't want to have to rasterize my graphics either... I just want it to work. It's coming, I'm sure.
The right thing to do with something that isn't yours is not to pick it up and sell it. Duh. He will learn a lesson from this.
From the US-CERT "About Us" page:
US-CERT's mission is to improve the nation's cybersecurity posture, coordinate cyber information sharing and proactively manage cyber risks to the nation while protecting the constitutional rights of Americans. US-CERT vision is to be a trusted global leader in cybersecurity - collaborative, agile, and responsive in a complex environment.
Information is available from the US-CERT web site, mailing lists, and RSS channels.
US-CERT also provides a way for citizens, businesses, and other institutions to communicate and coordinate directly with the United States government about cyber security.
Who runs US-CERT?
US-CERT is the operational arm of the National Cyber Security Division (NCSD) at the Department of Homeland Security (DHS).
Where is US-CERT located?
US-CERT is located in the Washington DC Metropolitan area.
What is US-CERT's relationship to NCSD and DHS?
US-CERT is the operational arm of the National Cyber Security Division (NCSD) at the Department of Homeland Security (DHS). The NCSD was established by DHS to serve as the federal government's cornerstone for cyber security coordination and preparedness, including implementation of the National Strategy to Secure Cyberspace .
Most web sites run on name-based virtual hosts. This allows multiple web sites to use the same instance of the web server (Apache, IIS, etc.), reducing costs.
This presents a chicken-an-egg problem with TLS/SSL (the encryption used for https).
When the web server receives the initial request from the browser, it sends back a certificate for it's domain that says to the browser, "Yes, I am really where-ever.com, because I paid money to GoDaddy, Comodo, Verisign or whoever and they'll corroborate."
The problem is, when that first request comes in, and you are using TLS/SSL and name-based virtual hosting, the server can't read what domain name was requested to present the correct certificate. You haven't finished negotiating the TLS/SSL connection yet, so you can't read the URI embedded in the request.
So, you need a different IP for each domain that you are going to serve (IP addresses are becoming rare) or use some other hack to accomplish this.
Do you remember this: http://tech.slashdot.org/story/09/08/22/1246248/Google-Brings-SVG-Support-To-IE ?
I remember when Google announced the svgweb javascript library to enable SVG support in IE. That sort of reinforced the notion that Microsoft was playing catch-up in the browser technology arena. Microsoft is now, at least trying, I think, to present the appearance that Google is the company that is behind. Not to mention it doesn't hurt MS to have value added to Chrome when it runs on Windows. They're not going to make this happen for Chrome running on GNU/Linux.
Jennings: I'll take CAPTCHAs for 1000, Alex...
Big Blue: Damnit.
PURGE COMPLETE.