Live data from Hacker News

The surprisingly complex journey to text-selectable client-side generated PDFs

sdocs.dev

61–66 of 66 posts

Re: The surprisingly complex journey to text-selectable client-side generated PDFs

#61
post #50
post #43

Earlier quoted context omitted.

For the mac there's TextSniper which does just that.

On mac, I just do a quick screenshot and use the builtin OCR in Preview to select and copy text all the time.

Textgrabber does that without needing a screenshot. Found it here on HN, never looked back.

Re: The surprisingly complex journey to text-selectable client-side generated PDFs

#63

There was a plug of smalldocs intro in that post, regarding that, Dont we need the md files on the wikis and documentations in the central project management tools, instead of client side anything?

SmallDocs person here, IMO the location of Markdown files and the reading of them are separate things. SmallDocs is just about reading not about storing. Eg if you are working in ~/code/my_project, and have a README.md, you (or your agent) can `sdoc README.md`. This opens up the file for reading (in the browser, but 100% privately). It doesn’t change the stored location of the Markdown file.

Is that what you were getting at or something else?

Re: The surprisingly complex journey to text-selectable client-side generated PDFs

#64

There was a plug of smalldocs intro in that post, regarding that, Dont we need the md files on the wikis and documentations in the central project management tools, instead of client side anything?

SmallDocs person here, IMO the location of Markdown files and the reading of them are separate things. SmallDocs is just about reading not about storing. Eg if you are working in ~/code/my_project, and have a README.md, you (or your agent) can `sdoc README.md`. This opens up the file for reading (in the browser, but 100% privately). It doesn’t change the stored location of the Markdown file. Is that what you were get…

Ah its a reader, okay, great tool!

Re: The surprisingly complex journey to text-selectable client-side generated PDFs

#65
post #6

Software engineers drastically underestimates GUI - Web layouts, mobile app layouts, and even PDF layouts are non-trivial pieces of work to get right in all circumstances.

Nobody who has actually worked on those things think that. You might want to qualify if you're only talking about people who have never worked in this area. In my experience it's the NON software engineers who tend to underestimate the complexity

I didn't qualify.

And the reason was that majority of backend engineers have never worked on frontend.

At almost all big companies, the team working on the frontend problem is relatively small +and that's how it should be).

> In my experience it's the NON software engineers who tend to underestimate the complexity

Yeah. That too as well.

Re: The surprisingly complex journey to text-selectable client-side generated PDFs

#66
post #50

Earlier quoted context omitted.

On mac, I just do a quick screenshot and use the builtin OCR in Preview to select and copy text all the time.

Textgrabber does that without needing a screenshot. Found it here on HN, never looked back.

> Textgrabber does that without needing a screenshot.

There seems to be a product or two using that name: can you give a URL to the legitimate one?

Post reply on HN