Editing 2021.09.23.21:07
This commit is contained in:
parent
3b56845836
commit
e0a2ccf5c2
@ -55,7 +55,15 @@
|
||||
\@writefile{toc}{\contentsline {chapter}{\numberline {4}Miscellany}{27}{chapter.4}\protected@file@percent }
|
||||
\@writefile{lof}{\addvspace {10\p@ }}
|
||||
\@writefile{lot}{\addvspace {10\p@ }}
|
||||
\@writefile{toc}{\contentsline {section}{\numberline {4.1}A Scanner Darkly, but with a workflow}{27}{section.4.1}\protected@file@percent }
|
||||
\@writefile{toc}{\contentsline {section}{\numberline {4.2}Is This Really a Hack? Or Is It Just a Tip?}{27}{section.4.2}\protected@file@percent }
|
||||
\@writefile{toc}{\contentsline {section}{\numberline {4.3}What I Learned About \LaTeX \tmspace +\thinmuskip {.1667em} While Creating This Issue}{30}{section.4.3}\protected@file@percent }
|
||||
\@writefile{toc}{\contentsline {section}{\numberline {4.4}Coda: Why \LaTeX ?}{31}{section.4.4}\protected@file@percent }
|
||||
\@writefile{toc}{\contentsline {chapter}{\numberline {5}A Scanner Darkly, but with a workflow}{28}{chapter.5}\protected@file@percent }
|
||||
\@writefile{lof}{\addvspace {10\p@ }}
|
||||
\@writefile{lot}{\addvspace {10\p@ }}
|
||||
\@writefile{toc}{\contentsline {chapter}{\numberline {6}Is This Really a Hack? Or Is It Just a Tip?}{31}{chapter.6}\protected@file@percent }
|
||||
\@writefile{lof}{\addvspace {10\p@ }}
|
||||
\@writefile{lot}{\addvspace {10\p@ }}
|
||||
\@writefile{toc}{\contentsline {chapter}{\numberline {7}Coda}{34}{chapter.7}\protected@file@percent }
|
||||
\@writefile{lof}{\addvspace {10\p@ }}
|
||||
\@writefile{lot}{\addvspace {10\p@ }}
|
||||
\@writefile{toc}{\contentsline {section}{\numberline {7.1}What I Learned About \LaTeX \tmspace +\thinmuskip {.1667em} While Creating This Issue}{34}{section.7.1}\protected@file@percent }
|
||||
\@writefile{toc}{\contentsline {section}{\numberline {7.2}Coda: Why \LaTeX ?}{35}{section.7.2}\protected@file@percent }
|
||||
\@writefile{toc}{\contentsline {section}{\numberline {7.3}What's Next?}{37}{section.7.3}\protected@file@percent }
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian) (preloaded format=pdflatex 2021.9.5) 23 SEP 2021 19:04
|
||||
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian) (preloaded format=pdflatex 2021.9.5) 23 SEP 2021 21:06
|
||||
entering extended mode
|
||||
restricted \write18 enabled.
|
||||
%&-line parsing enabled.
|
||||
@ -101,11 +101,6 @@ LaTeX Font Info: Overwriting math alphabet `\mathfrak' in version `bold'
|
||||
(/usr/share/texlive/texmf-dist/tex/latex/base/makeidx.sty
|
||||
Package: makeidx 2014/09/29 v1.0m Standard LaTeX package
|
||||
)
|
||||
\@indexfile=\write3
|
||||
\openout3 = `codex-001.idx'.
|
||||
|
||||
|
||||
Writing index file codex-001.idx
|
||||
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
|
||||
Package: graphicx 2019/11/30 v1.2a Enhanced LaTeX Graphics (DPC,SPQR)
|
||||
|
||||
@ -809,8 +804,8 @@ LaTeX Info: Redefining \pageref on input line 68.
|
||||
LaTeX Info: Redefining \nameref on input line 68.
|
||||
|
||||
(build/codex-001.out) (build/codex-001.out)
|
||||
\@outlinefile=\write4
|
||||
\openout4 = `codex-001.out'.
|
||||
\@outlinefile=\write3
|
||||
\openout3 = `codex-001.out'.
|
||||
|
||||
LaTeX Font Info: Trying to load font information for U+jkpsya on input line
|
||||
70.
|
||||
@ -844,7 +839,7 @@ LaTeX Font Info: Trying to load font information for TS1+jkp on input line 7
|
||||
(/usr/share/texlive/texmf-dist/tex/latex/kpfonts/ts1jkp.fd
|
||||
File: ts1jkp.fd 2007/08/30 Fontinst v1.928 font definitions for TS1/jkp.
|
||||
)
|
||||
<images/ncsa4-0.png, id=151, 88.33pt x 31.11626pt>
|
||||
<images/ncsa4-0.png, id=159, 88.33pt x 31.11626pt>
|
||||
File: images/ncsa4-0.png Graphic file (type png)
|
||||
<use images/ncsa4-0.png>
|
||||
Package pdftex.def Info: images/ncsa4-0.png used on input line 74.
|
||||
@ -854,53 +849,41 @@ LaTeX Font Info: Trying to load font information for OT1+jkptt on input line
|
||||
|
||||
(/usr/share/texlive/texmf-dist/tex/latex/kpfonts/ot1jkptt.fd
|
||||
File: ot1jkptt.fd 2007/01/26 Fontinst v1.928 font definitions for OT1/jkptt.
|
||||
)
|
||||
Overfull \hbox (87.99597pt too wide) in paragraph at lines 80--81
|
||||
\OT1/jkp/m/n/10 layah from the Wiki-Me-dia Com-mons. The im-age is []over here[
|
||||
]: [][]\OT1/jkptt/m/n/10 https://commons.wikimedia.o
|
||||
[]
|
||||
|
||||
|
||||
Overfull \hbox (2.94096pt too wide) in paragraph at lines 80--81
|
||||
[]\OT1/jkptt/m/n/10 rg/wiki/File:4_RETAT_04_Linus_Torvalds.jpg[]\OT1/jkp/m/n/10
|
||||
. You can also find a link
|
||||
[]
|
||||
|
||||
[2 <./images/ncsa4-0.png>] (build/codex-001.toc [3
|
||||
) [2 <./images/ncsa4-0.png>] (build/codex-001.toc [3
|
||||
|
||||
])
|
||||
\tf@toc=\write5
|
||||
\openout5 = `codex-001.toc'.
|
||||
\tf@toc=\write4
|
||||
\openout4 = `codex-001.toc'.
|
||||
|
||||
[4]
|
||||
Chapter 1.
|
||||
[5
|
||||
|
||||
]
|
||||
Overfull \hbox (4.79448pt too wide) in paragraph at lines 115--116
|
||||
Overfull \hbox (4.79448pt too wide) in paragraph at lines 122--123
|
||||
\OT1/jkp/m/n/10 be-cause they had a go-back-through-all-your-steps-to-see-where
|
||||
-you-done-
|
||||
[]
|
||||
|
||||
[6]
|
||||
<images/casio.jpg, id=228, 303.1325pt x 552.0625pt>
|
||||
<images/casio.jpg, id=238, 303.1325pt x 552.0625pt>
|
||||
File: images/casio.jpg Graphic file (type jpg)
|
||||
<use images/casio.jpg>
|
||||
Package pdftex.def Info: images/casio.jpg used on input line 122.
|
||||
Package pdftex.def Info: images/casio.jpg used on input line 129.
|
||||
(pdftex.def) Requested size: 45.46791pt x 82.8058pt.
|
||||
[7 <./images/casio.jpg>]
|
||||
|
||||
Package multicol Warning: I moved some lines to the next page.
|
||||
(multicol) Footnotes on page 8 might be wrong on input line 157.
|
||||
(multicol) Footnotes on page 8 might be wrong on input line 164.
|
||||
|
||||
|
||||
[8]
|
||||
Underfull \hbox (badness 7595) in paragraph at lines 159--160
|
||||
Underfull \hbox (badness 7595) in paragraph at lines 166--167
|
||||
\OT1/jkp/m/n/10 1921 by Theodore and Mil-ton
|
||||
[]
|
||||
|
||||
|
||||
Overfull \hbox (1.41647pt too wide) in paragraph at lines 170--171
|
||||
Overfull \hbox (1.41647pt too wide) in paragraph at lines 177--178
|
||||
[]\OT1/jkp/m/n/10 Anyway, that Wednes-day af-ter-noon ex-pe-ri-ence was a real
|
||||
game changer
|
||||
[]
|
||||
@ -912,7 +895,7 @@ Chapter 2.
|
||||
] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21]
|
||||
Chapter 3.
|
||||
|
||||
Overfull \hbox (0.53847pt too wide) in paragraph at lines 368--369
|
||||
Overfull \hbox (0.53847pt too wide) in paragraph at lines 375--376
|
||||
\OT1/jkp/m/n/10 This di-rec-tory con-tains es-sen-tial com-mand bi-na-ries[][][
|
||||
] that need to be avail-
|
||||
[]
|
||||
@ -921,46 +904,69 @@ Overfull \hbox (0.53847pt too wide) in paragraph at lines 368--369
|
||||
|
||||
] [23] [24] [25] [26]
|
||||
Chapter 4.
|
||||
[27
|
||||
|
||||
Overfull \hbox (1.1366pt too wide) in paragraph at lines 495--496
|
||||
]
|
||||
Chapter 5.
|
||||
|
||||
Overfull \hbox (6.11798pt too wide) in paragraph at lines 491--492
|
||||
[]\OT1/jkp/m/n/10 My hard-ware is a Brother MFC-J805DW printer/scanner/fax ma-c
|
||||
hine.[][][]
|
||||
[]
|
||||
|
||||
[28
|
||||
|
||||
]
|
||||
Overfull \hbox (2.28105pt too wide) in paragraph at lines 523--524
|
||||
\OT1/jkp/m/n/10 hap-pens with [][]\OT1/jkptt/m/n/10 pdftk[]\OT1/jkp/m/n/10 . (S
|
||||
ee []www.pdflabs.com/tools/pdftk-the-pdf-toolkit/[].)
|
||||
[]
|
||||
|
||||
[29] [30]
|
||||
Chapter 6.
|
||||
|
||||
Overfull \hbox (1.1366pt too wide) in paragraph at lines 554--555
|
||||
[]\OT1/jkp/m/n/10 Rather, I'm talk-ing about the older mean-ing of the term ``h
|
||||
acker'' which
|
||||
[]
|
||||
|
||||
[27
|
||||
[31
|
||||
|
||||
] [28] [29]
|
||||
] [32] [33]
|
||||
Chapter 7.
|
||||
|
||||
Package hyperref Warning: Token not allowed in a PDF string (PDFDocEncoding):
|
||||
(hyperref) removing `\leavevmode@ifvmode' on input line 522.
|
||||
(hyperref) removing `\leavevmode@ifvmode' on input line 583.
|
||||
|
||||
|
||||
Package hyperref Warning: Token not allowed in a PDF string (PDFDocEncoding):
|
||||
(hyperref) \kern 1.66702pt
|
||||
(hyperref) removed on input line 522.
|
||||
(hyperref) removed on input line 583.
|
||||
|
||||
[30]
|
||||
Overfull \hbox (8.25641pt too wide) in paragraph at lines 537--538
|
||||
[34
|
||||
|
||||
]
|
||||
Overfull \hbox (8.25641pt too wide) in paragraph at lines 598--599
|
||||
\OT1/jkp/m/n/10 vent that, add [][]\OT1/jkptt/m/n/10 \counterwithout{foootnote}
|
||||
{chapter} []\OT1/jkp/m/n/10 to the pream-
|
||||
[]
|
||||
|
||||
[31] [32]
|
||||
Package atveryend Info: Empty hook `BeforeClearDocument' on input line 580.
|
||||
[33]
|
||||
Package atveryend Info: Empty hook `AfterLastShipout' on input line 580.
|
||||
[35] [36]
|
||||
Package atveryend Info: Empty hook `BeforeClearDocument' on input line 642.
|
||||
[37]
|
||||
Package atveryend Info: Empty hook `AfterLastShipout' on input line 642.
|
||||
(build/codex-001.aux)
|
||||
Package atveryend Info: Executing hook `AtVeryEndDocument' on input line 580.
|
||||
Package atveryend Info: Executing hook `AtEndAfterFileList' on input line 580.
|
||||
Package atveryend Info: Executing hook `AtVeryEndDocument' on input line 642.
|
||||
Package atveryend Info: Executing hook `AtEndAfterFileList' on input line 642.
|
||||
Package rerunfilecheck Info: File `codex-001.out' has not changed.
|
||||
(rerunfilecheck) Checksum: <no file>.
|
||||
Package atveryend Info: Empty hook `AtVeryVeryEnd' on input line 580.
|
||||
Package atveryend Info: Empty hook `AtVeryVeryEnd' on input line 642.
|
||||
)
|
||||
Here is how much of TeX's memory you used:
|
||||
8638 strings out of 483140
|
||||
121729 string characters out of 5965152
|
||||
380512 words of memory out of 5000000
|
||||
23315 multiletter control sequences out of 15000+600000
|
||||
8661 strings out of 483140
|
||||
121921 string characters out of 5965152
|
||||
380564 words of memory out of 5000000
|
||||
23317 multiletter control sequences out of 15000+600000
|
||||
592103 words of font info for 159 fonts, out of 8000000 for 9000
|
||||
36 hyphenation exceptions out of 8191
|
||||
34i,11n,45p,1104b,441s stack positions out of 5000i,500n,10000p,200000b,80000s
|
||||
@ -975,10 +981,10 @@ nts/type1/public/kpfonts/jkpbn8a.pfb></usr/share/texlive/texmf-dist/fonts/type1
|
||||
fonts/jkpmit8a.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/kpfonts/jk
|
||||
pmn8a.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/kpfonts/jkpmne.pfb>
|
||||
</usr/share/texlive/texmf-dist/fonts/type1/public/kpfonts/jkpttmn8a.pfb>
|
||||
Output written on build/codex-001.pdf (33 pages, 169630 bytes).
|
||||
Output written on build/codex-001.pdf (37 pages, 177219 bytes).
|
||||
PDF statistics:
|
||||
501 PDF objects out of 1000 (max. 8388607)
|
||||
451 compressed objects within 5 object streams
|
||||
135 named destinations out of 1000 (max. 500000)
|
||||
291 words of extra memory for PDF output out of 10000 (max. 10000000)
|
||||
557 PDF objects out of 1000 (max. 8388607)
|
||||
502 compressed objects within 6 object streams
|
||||
157 named destinations out of 1000 (max. 500000)
|
||||
307 words of extra memory for PDF output out of 10000 (max. 10000000)
|
||||
|
||||
|
||||
@ -29,7 +29,9 @@
|
||||
\BOOKMARK [1][-]{section.3.17}{usr}{chapter.3}% 29
|
||||
\BOOKMARK [1][-]{section.3.18}{var}{chapter.3}% 30
|
||||
\BOOKMARK [0][-]{chapter.4}{Miscellany}{}% 31
|
||||
\BOOKMARK [1][-]{section.4.1}{A Scanner Darkly, but with a workflow}{chapter.4}% 32
|
||||
\BOOKMARK [1][-]{section.4.2}{Is This Really a Hack? Or Is It Just a Tip?}{chapter.4}% 33
|
||||
\BOOKMARK [1][-]{section.4.3}{What I Learned About LaTeX While Creating This Issue}{chapter.4}% 34
|
||||
\BOOKMARK [1][-]{section.4.4}{Coda: Why LaTeX?}{chapter.4}% 35
|
||||
\BOOKMARK [0][-]{chapter.5}{A Scanner Darkly, but with a workflow}{}% 32
|
||||
\BOOKMARK [0][-]{chapter.6}{Is This Really a Hack? Or Is It Just a Tip?}{}% 33
|
||||
\BOOKMARK [0][-]{chapter.7}{Coda}{}% 34
|
||||
\BOOKMARK [1][-]{section.7.1}{What I Learned About LaTeX While Creating This Issue}{chapter.7}% 35
|
||||
\BOOKMARK [1][-]{section.7.2}{Coda: Why LaTeX?}{chapter.7}% 36
|
||||
\BOOKMARK [1][-]{section.7.3}{What's Next?}{chapter.7}% 37
|
||||
|
||||
Binary file not shown.
Binary file not shown.
@ -29,7 +29,9 @@
|
||||
\contentsline {section}{\numberline {3.17}usr}{26}{section.3.17}%
|
||||
\contentsline {section}{\numberline {3.18}var}{26}{section.3.18}%
|
||||
\contentsline {chapter}{\numberline {4}Miscellany}{27}{chapter.4}%
|
||||
\contentsline {section}{\numberline {4.1}A Scanner Darkly, but with a workflow}{27}{section.4.1}%
|
||||
\contentsline {section}{\numberline {4.2}Is This Really a Hack? Or Is It Just a Tip?}{27}{section.4.2}%
|
||||
\contentsline {section}{\numberline {4.3}What I Learned About \LaTeX \tmspace +\thinmuskip {.1667em} While Creating This Issue}{30}{section.4.3}%
|
||||
\contentsline {section}{\numberline {4.4}Coda: Why \LaTeX ?}{31}{section.4.4}%
|
||||
\contentsline {chapter}{\numberline {5}A Scanner Darkly, but with a workflow}{28}{chapter.5}%
|
||||
\contentsline {chapter}{\numberline {6}Is This Really a Hack? Or Is It Just a Tip?}{31}{chapter.6}%
|
||||
\contentsline {chapter}{\numberline {7}Coda}{34}{chapter.7}%
|
||||
\contentsline {section}{\numberline {7.1}What I Learned About \LaTeX \tmspace +\thinmuskip {.1667em} While Creating This Issue}{34}{section.7.1}%
|
||||
\contentsline {section}{\numberline {7.2}Coda: Why \LaTeX ?}{35}{section.7.2}%
|
||||
\contentsline {section}{\numberline {7.3}What's Next?}{37}{section.7.3}%
|
||||
|
||||
@ -4,7 +4,7 @@
|
||||
%\usepackage{amsfonts}
|
||||
\usepackage{amssymb}
|
||||
\usepackage{makeidx}
|
||||
\makeindex
|
||||
%\makeindex
|
||||
\usepackage{graphicx}
|
||||
\usepackage{kpfonts}
|
||||
\raggedbottom
|
||||
@ -63,7 +63,7 @@
|
||||
|
||||
\author{Kenneth John Odle}
|
||||
\title{{\Huge the codex}\\{\footnotesize Life with Linux — A Zine\\Typeset in \LaTeX}}
|
||||
\date{\begin{small}2021.09.16\end{small}}
|
||||
\date{\begin{small}2021.09.23\end{small}}
|
||||
|
||||
\begin{document}
|
||||
\maketitle
|
||||
@ -77,7 +77,14 @@ FYI, this is made in \LaTeX \,using the report document class. It then gets expo
|
||||
|
||||
I'm pushing this to my own git server as I write this. You can find it \href{https://git.kjodle.net/kjodle/the-codex}{here}: \texttt{https://git.kjodle.net/kjodle/the-codex}. New issues will be pushed after they are complete.
|
||||
|
||||
The image of Linus Torvalds on the front cover is courtesy JericoDelayah from the WikiMedia Commons. The image is \href{https://commons.wikimedia.org/wiki/File:4_RETAT_04_Linus_Torvalds.jpg}{over here}: \verb|https://commons.wikimedia.o| \verb|rg/wiki/File:4_RETAT_04_Linus_Torvalds.jpg|. You can also find a link to the Creative Commons CC BY-SA 3.0 license there, as well.
|
||||
The image of Linus Torvalds on the front cover is courtesy JericoDelayah from the WikiMedia Commons. The image is \href{https://commons.wikimedia.org/wiki/File:4_RETAT_04_Linus_Torvalds.jpg}{over here}:
|
||||
|
||||
\begin{verbatim}
|
||||
https://commons.wikimedia.org/wiki/File:4_RETAT_04_Linus_Torv
|
||||
alds.jpg
|
||||
\end{verbatim}
|
||||
|
||||
You can also find a link to the Creative Commons CC BY-SA 3.0 license there, as well.
|
||||
|
||||
The image on the back cover is one that I highly agree with. We built it, it's ours, and we shouldn't be charged for using it. I want my tax dollars to serve my needs. I don't want my tax dollars used to make rich white old men richer.
|
||||
|
||||
@ -101,7 +108,7 @@ I mean, \textit{sure} you can get your kid that Casio, which has all the same fe
|
||||
|
||||
\textbf{Oh my, a diversion already.}
|
||||
\begin{multicols}{2}
|
||||
A little off track here, but this begs two questions: 1) Why is it always a TI calculator that's required, and 2) Are we teaching kids to learn math or to learn how to operate a calculator? The answer to the first question is that Texas Instruments and the Major Textbook Publishers\texttrademark \, have colluded to produce expensive books that need to be replaced every two to three years [thereby costing the school district money] and that require expensive calculators\footnote{A few years ago, I bought a scientific calculator at the \textbf{dollar store} and tested it against my very expensive TI-92. It was just as accurate as the more expensive calculator, and cheaper by two orders of magnitude. Did I mention that this is a racket? I really should do a YouTube video or blog post about this.} [thereby costing you as a parent money]. It's a racket, but that's capitalism for you.
|
||||
A little off track here, but this begs two questions: 1) Why is it always a TI calculator that's required, and 2) Are we teaching kids to learn math or to learn how to operate a calculator? The answer to the first question is that Texas Instruments and the Major Textbook Publishers\texttrademark{} have colluded to produce expensive books that need to be replaced every two to three years [thereby costing the school district money] and that require expensive calculators\footnote{A few years ago, I bought a scientific calculator at the \textbf{dollar store} and tested it against my very expensive TI-92. It was just as accurate as the more expensive calculator, and cheaper by two orders of magnitude. Did I mention that this is a racket? I really should do a YouTube video or blog post about this.} [thereby costing you as a parent money]. It's a racket, but that's capitalism for you.
|
||||
|
||||
The answer to the second question is that we are teaching kids how to use calculators. Teaching them how to do actual math would require thought on both the parts of the teachers\footnote{To be fair, a lot of teachers would like to teach kids how to do actual math. But they also need to eat and when it comes down to the difference between doing what is right and doing what pays the bills, they will do the latter. It's not their fault, really; it's just that the system does not like anybody who sticks out. Keep your head down and the worksheets graded—that's what the system rewards.} and the parts of the students, not to mention on the parts of parents and especially of administrators, who would also be required to grow a spine—and learn how to use it. Again, education in the United States has become a racket, but that's capitalism for you.
|
||||
\end{multicols}
|
||||
@ -474,20 +481,72 @@ This directory contains files who content is expected to continually change duri
|
||||
|
||||
\chapter{Miscellany}
|
||||
|
||||
\section{A Scanner Darkly, but with a workflow}
|
||||
I suppose I should have been an archivist.
|
||||
\chapter{A Scanner Darkly, but with a workflow}
|
||||
I suppose I should have been an archivist. I am always trying to preserve the written word in digital form.
|
||||
|
||||
tips about pdftk. (What were these? from the man pages.)
|
||||
And this makes sense. It's easier to share a digital file of something than to share the thing itself, because as my experience with sharing books highlights, you rarely get them back. Also, the further you spread something, the more like it is to be preserved. \textit{Preservation through dissemination.}
|
||||
|
||||
So I scan a lot of things. Because this can be a messy, complicated process, I've developed workflows around this. (I am big into workflows, because once you have one down, it's easier to anticipate and deal with interruptions or disruptions. Unless you run into a mule.\footnote{If you've read Asimov's \textit{Foundation} series, you'll know what I'm talking about.} So here is my workflow for scanning things.
|
||||
|
||||
My hardware is a Brother MFC-J805DW printer/scanner/fax machine.\footnote{One day, we will eventually give up faxing, which is archaic at this point. I don't know if we'll just start calling these machines ``printer/scanners'' or if we'll continue to call them ``multi-function machines'' because they still can make copies. Futurists tend not to care about the details.} And this is where we run into problems, because while Brother does make Linux drivers for this machine, the printer driver works great and the scanner driver does not. If I install it, it works fine for three or four scans and then it starts to hang. I can uninstall it, reinstall it, and get a few more good scans out of it before everything goes pear-shaped again. I could live with this if I only did the occasional scan, but I scan on a regular basis.
|
||||
|
||||
Alas, this is the one case where I have had to rely upon commercial software: VueScan. The company which produces it, Hamrick Software, creates their own drivers, update it often, and respond to issues incredibly quickly. It costs me \$100 a year, but this is money that I am happy to pay. (And if there were an open-source version of this software, I would be happy to pay that \$100 to it, as well.)\footnote{It also has an auto-deskew function, which is handy when the paper I am scanning is narrower than the minimum width my document feeder can handle.}
|
||||
|
||||
My Brother scanner does \textit{not} have a duplex scanner. Since books are printed on both sides of a sheet of paper, this presents a problem. But before we dig into things, let's get some terminology out of the way.
|
||||
|
||||
A \textbf{sheet} of paper (also called a \textbf{leaf}) has two sides, which are called \textbf{pages}. If you open a book, you'll notice the pages on the right side have odd page numbers. This is the \textbf{front side} of the pages, also called the \textbf{obverse} side. The pages on the left side have even page numbers. This is the \textbf{back side} of the pages, also called the \textbf{reverse} size.
|
||||
|
||||
My basic workflow works like this:
|
||||
|
||||
\begin{enumerate}
|
||||
\itemsep-0.30em
|
||||
\item Separate the document to be scanned into groups of ten sheets.
|
||||
\item Scan the front side of a group.
|
||||
\item Scan the reverse side of a group.
|
||||
\item Interleave those two scans, so that the front sides and back sides are in order in a single pdf.
|
||||
\item Repeat until all sheets have been scanned.
|
||||
\item Concatenate all the two sided scans from step 4 into a single document.
|
||||
\end{enumerate}
|
||||
|
||||
It helps to be have a naming scheme for your files, because you're going to end up deleting a lot of them. So let's run through this again, and include file names.
|
||||
|
||||
\begin{enumerate}
|
||||
\itemsep-0.30em
|
||||
\item Scan the front side of the first group and name that file \verb|001a.pdf|.
|
||||
\item Scan the reverse side of the first group and name that file \verb|001b.pdf|.
|
||||
\item Interleave the two scans, and name the resultant file \verb|001.pdf|.
|
||||
\item Delete all files that have \verb|a| or \verb|b| in the file name.
|
||||
\item Concatenate all the remaining files into a new filename that \textit{doesn't} have numbers in its filename.
|
||||
\item Delete all files except the one we created in the previous step.
|
||||
\end{enumerate}
|
||||
|
||||
All of the scanning is done through VueScan. Afterward, the magic happens with \verb|pdftk|. (See \href{https://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/}{www.pdflabs.com/tools/pdftk-the-pdf-toolkit/}.)
|
||||
|
||||
\bigskip
|
||||
|
||||
\noindent{}Okay, how do we do all of this stuff with pdftk?\footnote{I won't bore you with how to install it, since there are multiple ways to install it. You can easily find this information online.}
|
||||
|
||||
\medskip
|
||||
|
||||
\noindent{}We can interleave two scans with the pdftk command \verb|shuffle|. The basic command looks like this:
|
||||
|
||||
\begin{verbatim}
|
||||
$ pdftk A=001a.pdf B=001b.pdf shuffle A B output 001.pdf
|
||||
\end{verbatim}
|
||||
|
||||
\noindent{}What's happening here? pdftk allows us to assign \textit{handles} to files whenever we want to use just parts of those files, whether it's a single page or a range of pages. In this case, we are assigning the file 001a.pdf (which contains the front, odd-numbered pages) to the handle `A' and the file 001b.pdf (which contains the reverse, even-numbered pages) to the handle `B'.
|
||||
|
||||
We are then telling pdftk to interleave the two files via the \verb|shuffle| command. So if A contains the pages 1 3 5 7 9 and B contains the pages 2 4 6 8 10, the output pdf (001.pdf) will contain the pages 1 2 3 4 5 6 7 8 9 10. Pretty nifty, huh?
|
||||
|
||||
However, there is a problem. When you flip the group of sheets over and run them through your scanner, the reverse sides will be scanned in reverse order, because the highest numbered page will be the first to be scanned. So 001b.pdf will actually contain the pages 10 8 6 4 2. This is a problem.
|
||||
|
||||
Fortunately, pdftk has a way around this. Take a look at this command:
|
||||
|
||||
\begin{verbatim}
|
||||
$ pdftk A=001a.pdf B=001b.pdf shuffle A Bend-1 output 001.pdf
|
||||
\end{verbatim}
|
||||
|
||||
\section{Is This Really a Hack? Or Is It Just a Tip?}
|
||||
\chapter{Is This Really a Hack? Or Is It Just a Tip?}
|
||||
The word ``hacker'' has a lot of definitions, and if you just google it, you'll find a lot of scary ones on the websites of companies that want you to be scared of ``hackers'' and then spend hundreds of dollars on their security products, some of which may actually protect you against actual threats, and some of which may provide protection against a threat which isn't actually real.
|
||||
|
||||
(And yes, there are bad people out there who use their advanced technical knowledge to attain access to systems that they shouldn't have in order to obtain information they're not supposed to have. I'm not talking about those people, who technically should be called ``crackers'' a l\'{a} ``safe crackers''.)
|
||||
@ -519,6 +578,8 @@ So let's look at some things that have been called ``hacks'' but may or may not
|
||||
|
||||
So, 15 ``cooking hacks'' and only two of them are actual hacks, and one of them is pretty questionable. I'm pretty much calling it a hack because I'm trying to be generous. The thing that strikes me is not so much that these aren't actually hacks, but the difference between a ``tip'' and a ``technique.'' Maybe I'm just tired, but it seems like it's a technique if you use it on a regular basis and a tip if you're in a jam and someone tells you about it. But that's an argument for another day in another zine.
|
||||
|
||||
\chapter{Coda}
|
||||
|
||||
\section{What I Learned About \LaTeX\, While Creating This Issue}
|
||||
|
||||
I'm still a relative newbie to LaTeX, so there's always something to learn. Here's a running list of what I've learned so far:
|
||||
@ -576,5 +637,6 @@ Also, there is no easy way to get a word-count from a LaTeX document, nor is the
|
||||
|
||||
I'm not there yet (and I definitely won't be for a while—I've got bills to pay) but perhaps the nicest thing about LaTeX is that while there are a lot of packages available, if you can't find one to do what you want to do, you can always create your own. It will be a while before I get to that point because first I need to find something I want to do in LaTeX that isn't covered by an existing package, but I someday might. Remember, with the level of control you get with Linux, you also get opportunity. And it's always good to have a challenge to look forward to.
|
||||
|
||||
\section{What's Next?}
|
||||
|
||||
\end{document}
|
||||
Loading…
Reference in New Issue
Block a user