2,432 karma · joined May 6, 2009
[ my public key: https://keybase.io/pronoiac; my proof: https://keybase.io/pronoiac/sigs/OVIao7idCIz-0TbJHFDdwc1E8qrXTElDPhDzDjtijyU ]
My email is pronoiac@gmail.com.
The "internal links" thing is a pain, admittedly. I have an idea for a workaround:
* sprinkle hidden, unique <a id="ch1.2"></a> around
* on GitHub, use links like chapter1#ch1.2
* for Pandoc, preprocess to remove the filename before the #
I'm working with a big enough book that it's an undertaking, so I haven't done this yet.
I tried out Laya's Horizon, but my main device isn't powerful enough to play it, so it's been a while.
I didn't use this either, as I worried about wearing down the camera heads, and DVD-R's were cheaper and more plentiful.
#! /usr/bin/env nix-shell
#! nix-shell -i python3 -p python3Packages.pillow python3Packages.ansicolor
# scale image by 50%
import sys, PIL.Image, ansicolor
path = sys.argv[1]
image = PIL.Image.open(path)
factor = 0.5
image = image.resize((round(image.width \* factor), round(image.height \* factor)))
path = path + ".s50.jpg"
image.save(path)
print(ansicolor.green(f"done {path}")) cat -v
For a very short file, I might reach for hexdump -C> Apple Feedback Assistant reports are not public. To help other developers discover existing reports, copy-paste your submitted Feedback Assistant report into a new issue. Make sure you include everything.
> This is similar to Open Radar, but it's easier to fill out the report and GitHub has better search. Also, Open Radar doesn't yet support Feedback Assistant.
> Instead of voting on issues opened here (which Apple won't see anyway), file a new Feedback Assistant report and copy-paste the contents of the report you found here and link to the original report. Apple encourages duplicates.