-
Recent Posts
Links
Archives
- July 2026
- June 2026
- May 2026
- April 2026
- March 2026
- February 2026
- January 2026
- December 2025
- November 2025
- October 2025
- September 2025
- August 2025
- July 2025
- June 2025
- May 2025
- April 2025
- March 2025
- February 2025
- January 2025
- December 2024
- November 2024
- October 2024
- September 2024
- August 2024
- July 2024
- June 2024
- May 2024
- April 2024
- March 2024
- February 2024
- January 2024
- December 2023
- November 2023
- October 2023
- September 2023
- August 2023
- July 2023
- June 2023
- May 2023
- April 2023
- March 2023
- February 2023
- January 2023
- December 2022
- November 2022
- October 2022
- September 2022
- August 2022
- July 2022
- June 2022
- May 2022
- April 2022
- March 2022
- February 2022
- January 2022
- December 2021
- November 2021
- October 2021
- September 2021
- August 2021
- July 2021
- June 2021
- May 2021
- April 2021
- March 2021
- February 2021
- January 2021
- December 2020
- November 2020
- October 2020
- September 2020
- August 2020
- July 2020
- June 2020
- May 2020
- April 2020
- March 2020
- February 2020
- January 2020
- December 2019
- November 2019
- October 2019
- September 2019
- August 2019
- July 2019
- June 2019
- May 2019
- April 2019
- March 2019
- February 2019
- January 2019
- December 2018
- November 2018
- October 2018
- September 2018
- August 2018
- July 2018
- June 2018
- May 2018
- April 2018
- March 2018
- February 2018
- January 2018
- December 2017
- November 2017
- October 2017
- September 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- February 2017
- January 2017
- December 2016
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- September 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
Categories
Meta
The Publishing Workflow for ProGit v.2
As most of you know, I’m fascinated by publishing workflows. These days, my preferred scheme is write in Emacs/Org-mode and export to whatever final format I need. This strikes me as ideal.
Not everyone agrees, of course. Scott Chacon, one of the original GitHub developers and coauthor of Pro Git v. 2 has a different workflow. Unsurprisingly, he uses the Atom editor so he doesn’t write in Org markup. Instead, he uses Asciidoc, which is similar to Org but independent of any editor. Of course, these are just details. What makes his workflow different is how he leverages GitHub and the O’Reilly Atlas publishing toolchain.
Most of us won’t have access to Atlas but we can all use GitHub and leverage the methods that Chacon describes for collaboration and working with technical editors. I’ve written before about working as a technical editor and dealing with Word documents. I would much rather use the methods Chacon describes.
If you’re planning on writing a book—especially with one or more collaborators—be sure to check out Chacon’s post. He’s got a lot of good ideas. His workflow could easily be adjusted to work with Emacs and Org.
Org Ellipsis
It’s a bit silly, I suppose, but I really like this. It really does make things less cluttered.
Capturing Links with org-protocol
A year ago, I wrote about how I quickly grab browser links and site links directly from Emacs. My solution leverages applescript so it’s usable only on OS X. Since I do all my writing on OS X, I’ve never bothered to figure out how to make it work in other environments.
Sacha to the rescue. She’s implemented something similar by using org-protocol. Her solution is for the Windows platform but should work, mutatis mutandis, for other platforms. If you’d like to do something along the lines that I did, Chua’s post may be a good jumping off place. I keep wanting to figure out org-protocol myself but every time I try, I get bogged down. Perhaps Chua’s post will help me finally figure it all out.
Short History of Typesetting
If you enjoyed yesterday’s story about the vacation memo, you may also like another video by Professor Brailsford on a short history of typesetting. The Mergenthaler Linotron 202 that was the subject of my last post could be said to be a third generation typesetter. Bell Labs’ original CAT typesetter, with its optical fonts, was an example of a second generation typesetter. The Mergenthaler Linotype, a mechanical typesetter, is an example of the first generation.
Brailsford starts with an explanation of manual typesetting where the individual pieces of type were set by hand. He briefly covers the Linotype and then moves on to the second and third generation typesetters. They were all amazing machines but the most amazing, by far, was the Linotype.
It was completely mechanical but was able to take input from a keyboard, cast a line of (justified) type from molten lead, and then redistribute the type molds to the machine for reuse. If you want to see it in action you can watch the first 6 minutes of this 1960 film about the Linotype. That will give you a good idea of how complicated it was. If you have the time and want a real treat, watch the whole thing (it’s 35 minutes). After the short 6 minute introduction, the film explains in detail how it worked. It’s an astounding machine and by far the most complicated that I’ve ever seen. At the very end, they talk about the “future,” which involved driving the Linotype with paper tape.
The production values of the film are very dated by today’s standards but it’s still entertaining and informative. If you’re a nerd, you really have to watch it.
The Vacation Memo
In the summer of 1979, Bell Labs purchased a Mergenthaler Linotron 202 typesetter so they could typeset their own documents. The Mergenthaler was an example of the generation of typesetters just previous to laser printers. They were hideously complex and the process of producing typeset copy involved a complex and smelly photographic routine.
One of the first things that the Labs wanted to do was to produce their own fonts. Ken Thompson was especially eager to have a chess font that he could use to publish a book about chess. Mergenthaler, however, refused to give them the specs for the fonts citing the usual “proprietary nature” of the information.
But, of course, this was Bell Labs so they set out to reverse engineer the 202 and its fonts. Although Mergenthaler doubted that they would be able to do so, Ken Thompson, Joe Condon, and Brian Kernighan had everything figured out in about 6 weeks and were able to produce their own fonts and completely replace the Mergenthaler software that drove the typesetter. All this was done during “summer vacation.”
Afterwards, Brian Kernighan decided to write up what they did and how they did it in a Bell Labs memorandum later called The Vacation Memo. Mergenthaler sicced their lawyers on Bell Labs and the memo was suppressed for many years. In 2013, Professor David Brailsford, Steve Bagley, and Kernighan decided to reproduce the memo. They wanted to make it as accurate a reproduction as possible. Later, Brailsford, Bagley, and Kernighan published a paper on their reproduction in the Proceedings of DocEng 2013. Professor Brailsford tells the story of the memo and its reproduction in a very interesting and entertaining Computerphile video. It’s just under 20 minutes but if you enjoy seeing our history come alive and want to appreciate how easy we have it today with our laser printers, take the time to watch it. You won’t be sorry.
LPR Cameras Exposed Online
The government that claims it can safely manage backdoor keys to our communications has once again demonstrated its fecklessness at securing sensitive data. Sans Newsbites is reporting that several license plate reader cameras were exposed online. In some cases, the live streams could be accessed. They link to the original EFF report that has screenshots of some of the exposed pages as well as some of the actual camera sites.
As scandals go, this isn’t a huge deal but it does demonstrate why trusting the government with the keys to your communications is something only the foolish would consider. If they can’t do the easy stuff—this was not a break in, they just exposed the cameras to the Internet—why would you think they’ll be able to take care of the important stuff? Oh, that’s right; they can’t do that either.
What Metadata Really Is
Edward Snowden cuts through the baloney and reminds us of the real meaning of Metadata.
"Metadata" means records about your private activities and associations. It's an activity dossier. The novelty is in the lack of warrants.
— Edward Snowden (@Snowden) November 2, 2015
Are
your readers having trouble understanding the term
"metadata"? Replace it with "activity records."
That's what they are. #clarity
—
Edward Snowden (@Snowden) November
2, 2015
"It's only communications data" = "It's only a comprehensive record of your private activities." It's the activity log of your life. #IPBill
— Edward Snowden (@Snowden) November 4, 2015
This is really obvious when someone points it out but notice how the nosey Parkers who are intent are tracking our lives in detail always dismiss the significance of Metadata as if it were just some harmless data that they collect for some sort of technical reason that we needn’t worry about.
Textified Web Pages in Emacs
If you have lynx installed, here’s a handy tip from Mike Sample:
#Emacs #Orgmode is awesome for research notes. Pull text-ified webpages into the buffer with #nomouse C-u M-! lynx –dump <URL-to-good-page>
— Mike Sample (@mikesample) September 28, 2015
New Maintainer
Emacs has a new maintainer. Thanks to John Wiegley for taking on a hard, and often thankless, job.
Wiegley has been very active in Emacs development—including authoring the wonderful use-package and eshell packages—and has lots of good ideas. If you’re not familiar with his work, take a look at his chat with Sacha about Emacs or his chat with Sacha on Elisp development. There’s also a video with Sacha about organizing your Emacs configuration with use-package that I didn’t get a chance to write about.
I was excited when Wiegley expressed interest in the job and hoped he would be chosen. For his part, Wiegley is promising to make Emacs development a better place:
To all wishing to improve #emacs: Join me on the emacs-devel ML. We will make it a fun place again. Calling back all those who left!
— John Wiegley (@jwiegley) November 4, 2015