Dup Goto 📝

Errata

MetaProd/ 02-05 18:20:40
To Pop
47 lines, 454 words, 2647 chars Thursday 2026-02-05 18:20:40

I wrote the manuscript for these books in \(\LaTeX\). For one thing, it makes enforcing consistency of notation, maintaining tables of contents, and such, an easy task. Alas the source is edited in a text editor, in my case Vim, which has no built-in spelling or grammar checker, let alone some modern AI-driven affair. Despite my best efforts, some typos slipped the net and made what got published. Thankfully not many. I've listed them here.

If you're wondering why I used \(\LaTeX\), for one thing, it makes enforcing consistency of notation, maintaining tables of contents, and such, an easy task. Alas the source is edited in a text editor, in my case Vim, which has no built-in spelling or grammar checker, let alone some modern AI-driven affair. Despite my best efforts, some typos slipped the net and made what got published. Thankfully not many. I've listed them here. (Often these crept in during the process of final tweaks after the majority of the proof reading was done. For example the typo in the figure caption arose because the caption was rewritten and the image updated when it didn't look right originally.) These have all been corrected in the e-book editions, which were uploaded after the PDF manuscript for the print version was given the OK. The issue here was that it is a nontrivial task to convert from \(\LaTeX\) to a Kindle e-book. One has to first convert the \(\LaTeX\) source to Word .docx, and I use markdown as an intermediate step (I have a Python script to convert the \(\LaTeX\) to Markdown, which then needs a little manual fixing, and then Pandoc is used to translate the Markdown into .docx, which can then be imported into Amazon Kindle Create. Kindle Create is very limited in its ability to edit, for example it is unable to edit the contents of bulleted lists. So changes to the Kindle version must be made upstream, and then everything re-imported and reformatted, hence I only do this after the print version is submitted.)

That I use Vim as my editor, and use the key sequence jk to switch from insert mode (when text can be entered) to normal mode (used for other editing tasks), resulted in a spurious letter j on the end of exclamationj.

Hopefully my workflow improves with future books so that these few errors don't slip through.

Part I - Attitude

Part II - Learning

Part III - Workflow