4 ms·
I'd go for the SVG format instead of rasterizing to PNG. It's going to be lighter and give you a similar crisp feeling. Have you tried passing the pages throug
by nonoesp 4y ago
I'd go for the SVG format instead of rasterizing to PNG. It's going to be lighter and give you a similar crisp feeling.
Have you tried passing the pages through a OCR transcription system like tesseract? You also get this with the text-parsing feature of the reMarkable 2 for free, and I was thinking you could use the [link title] syntax to mark links and have some sort of automatic mapping to the links so you don't have to specify the links "by hand."
Anyhow, great idea. It's a bit small to read on iPhone.
A cool idea would be to convert each word to an individual image and put each of them inside of an inline div to make the article responsive.
- OneLessThing 4y agoI experimented with this approach on my blog[1]. I had an image of the handwritten blog post and used a feature in Inkscape to get SVG and make clickable text. I decided to place a little plain text in there to help Google search crawlers know what content is on the page. I really would prefer handwriting more. My problems boil down to just that flow of the tools sucked. I didn't want to have to attach multiple pages together. Inkscape was honestly a bit clunky to work with and I didn't have any personal tools to generate the full html from the svg. I might just be inspired to try again though. [1] https://blog.alew.is/insertionsort.html https://blog.alew.is/insertionsort.html
- nonoesp 4y agoNice! A solution could be to OCR the site and overlay the actual recognized text on the site as HTML items that can be hidden but useful for Google index the contents. I can see the pain and friction that doing that manually would entail though.