Hacker News new | ask | show | jobs
by massar 3275 days ago
Rendering a Microsoft Word/Powerpoint document as a PDF is a good thing as then one does not need a Doc/Docx/PPT/pptx viewer anymore while most devices come with a PDF viewer builtin (eg. Chrome :) (and as a bonus it kills the anims if they are there) this while keeping the formatting intact (some minor color changes though depending on one export it).

I tend to keep a whole bunch of things I want to 'read later' in my iBooks collection, just save as PDF and transfer to phone, or if already a PDF just download it directly; zooms great too. I got all kinds of device manuals, but also PADI and other diving reference books; always good to quickly check up on it when in doubt and then to reinforce that information with the knowledge of your dive buddy.

Indeed, for content that does not really need a layout outside of some headers (<h1>) and paragraphs (<p>) HTML is perfectly fine.

Quite a few text portions of conference papers (read: Tex :) can be rendered as markdown and then easily converted to HTML, but it won't feel 'as well', thus PDF is a easier format that also reflects the original intent and format.

IETF RFCs typically can be rendered in a myriad of ways thanks to xml2rfc, then again, one mostly will end up reading them from tools.ietf.org or to keep local, render as PDF and load it into iBooks.

2 comments

On the topic of MS Word, I really wish their export to html function was more simplistic. Most of the time I just want to export the document structure (headings, tables, bold, italic, etc.) and not include all of the styles and extra markup.
Pandoc?
That is what I use lately. It's not perfect but it's the closest thing I have found.
Reading PDF on mobile is possible, but far less comfortable than EPUB / MOBI...
I would have agreed until I got an ipad mini 2 (for safari testing), screen resolution is high enough that it's close to print experience.
I think robert-zaremba is talking about screen size ? Not screen resolution.

IMO, reflowing text is big advantage if you're going for "portability accross screen sizes".

> IMO, reflowing text is big advantage if you're going for "portability accross screen sizes".

It's a big advantage of your content is all pretty simple text; it's less useful for any other content. For complex content, you really need human attention to size-specific layout to getting anything better than just zooming content designed for one size.

Indeed. I love my iPad Mini and I use it for pdf's quite regularly (GoodReader is great for this), but it's just a tad too small to comfortably read A4-size documents, even on a retina screen. For many eBooks this is fine, but scientific papers are usually A4 and can be hard to read and annotate.

In some cases this can be fixed by cutting the margins, but aside from a certain unpleasantness I feel reading an almost-marginless document, it's often still not enough to comfortably read.

So for the most part, whenever possible, I go for ePub documents using Marvin (also an excellent app), and I print the larger documents.

It's one of the main reasons I'm considering getting a normal-sized iPad though.

I'm currently considering getting an iPad pro 12" for reading piano partitions. I'm sick of the stacks of large heavy old books laying on my piano and muffling the sound.

Does anyone here have a similar experience for that use case ? An iPad Pro seems large enough, but I don't really know. I've seen the Sony dpt-s2, but it seems very expensive given its limitations.

yes, screen size.

Most of the people will agree with me that straining your eyes is not a good solution ;) Little letters are not comfortable neither healthy.