Has anyone noticed that the PRS-500 has VERY POOR support for pdf's? I have spent a couple of days testing existing pdf's and re-distilling pdf's and most cannot be read on the reader, despite tweaking page size etc.

Don't believe the Sony reader's advertising "native pdf support." I can see that I will have to spend massive amounts of time to get pdf content (let alone anything in html, pdb, or chm) onto this reader, and I am very disappointed. Same thing happened with the Gemstar device (I own 2 of them), and this whole thing is starting to remind me of Gemstar's attempt to get you to buy "content." I've already spent much time over the years acquiring decent pdf conversion software like BCL and Iceni Gemini, but I really don't want to spend time to convert pdf's to another format so that I can look at them on the prs-500.

Sorry, not all of what I want on a portable reader will be bought from the Connect store. I am extremely disappointed. Sony needs to do something to fix this poor pdf support.

Seems to me that the Reader supports pdf pretty well, the problem is the screen size is too small to get a good view of a regular sized pdf page (the typical case). But it has been helpful for people with other character sets, for example, to use embedded fonts. Or if you want a particular page layout, it can probably be useful to do pdf. And if you have sharp eyes, the landscape mode does let you see some pdfs clearly enough to read the fine print.

But, I agree with what you are saying, in the sense that you shouldn't expect to take the average pdf file and plop it onto the Reader and be able to read it normally. Just doesn't work that way for most documents.

On the other hand, I love the way it handles rtf files. Have you tried coverting your documents to rtf instead?

Yeah, I have settled on importing .rtf using connect. Works fairly well, but there are some problems (connect has disappeared from the screen on occasion). The .rtf produced (from PDF) by BCL seems to work best, but Iceni Gemini and Acrobat exports work okay.

I am also going to look into creating the Sony format books using software posted on the Yahoo group. I still think Sony needs to improve PDF support, and is going to hear from alot of dissatisfied users over the current situation.

At this point, it takes me less effort to get a fairly readable pdf-derived doc on my Palm using Repligo. The more e-book readers I buy, the more jaded I get about the whole thing <G>. The first company that produces a good reader and makes it easy to get READABLE self-owned content on the device will take this market.

Look at it like an Ipod- do you think the Ipods would be so successful if it was extremely difficult to load songs on? It's easy to load content, easy to use, and- while Apple may want you to buy stuff at their store- it is not a requirement.

Sony should publish information about their e-file format, and provide programs that will take common formats like .chm, .pdf, and .pdf, and convert- and do the conversion well. I have been dealing with these problems since the days of the Rocketbook, and just don't understand why a big player like Sony can't get it right.

Sony should publish information about their e-file format, and provide programs that will take common formats like .chm, .pdf, and .pdf, and convert- and do the conversion well. I have been dealing with these problems since the days of the Rocketbook, and just don't understand why a big player like Sony can't get it right.
They promised they'd open up soon. *holding thumbs*

For what it's worth, if one has the material in an editable format (rtf, txt, .doc, etc.), one can run it through Open Office and then export it to PDF with the page and font set for a more satisfactory reading experience on the Sony screen.

I've been playing (without much success so far) with extracting text from PDF files, editing them in Open Office, and then exporting them back to PDF after formatting for the screen.

Right now, it appears that it will be a difficult process, but, for long-term document use (persistant technical docs and references), doing so once may be worth the effort. I have a significant library of specifications and such, and some presentations, that would be very handy to have in a portable, instant-on form.

I'm going to check out pdftohtml as a possible time-saver, but not until tomorrow.

Text rendering in PDF files looks a little off to me. Serif fonts come out too faint and "skinny". Sans serif fonts look good, though. Somehow, serif fonts in BBeB files look better.

I just got mine. I'm hoping for the best. I think the whole idea of a portable reader is a great idea.

I have been trying out pdftohtml to see if it would work to help generate more Reader-friendly documents, and I'm afraid it's not working well.

I haven't really studied up on the PDF file structure, but I'm beginning to think that, as a page description file format, some of the niceties are not known about, such as paragraphs.

All of the tools I've tried so far have treated every line of 'data' in the pdf file as either its own paragraph, or as something with line-breaks, but no paragraph markers. (that would be pdftohtml). Trying to subsequently munge the output text to re-group paragraphs is going to be a fairly manual operation. I'm going to try to work up an OOo macro that will let me select a block of text, and remove all line-break and paragraph markers from the middle of it, and add a paragraph tag at the end. I'll still have to go through the entire document and rebuild it, but at least I'll be able to re-flow paragraphs to reformat for the Reader screen.

I think this will be acceptable for moderately sized pdfs, but not for any book-length docs.

p.s.: I know there are web-based pdf conversion services, but a lot of my reading is proprietary information, and I can't toss it out on the internet to convert it.

PDF is essentially a "literal" layout format and contains virtually no semantic information such as paragraphs and list structures that you find in HTML.

Until better tools are found, I select all the text in a .PDF, paste into Word, convert to 16 point font, and save as an RTF document. I then send the RTF document to my reader and it looks pretty good. No pictures of course, but the text is readable.

With most PDFs the best solution is to completely forget about the format. So, no 'converting' into RTF, HTML or DOC.

I do this every day at work, believe me: either copy and paste for selected text or save to TXT for large files. Of course, you will probably have to reformat, but it's easier with a plain TXT file than with a hideous-looking RTF full of section breaks and what-not.

On my Mac, I've started using "File Juicer" (google it). I'd use Word except that I didn't want to shell out the clams for Office. I already paid enough for my MacBook Pro, thank you!

Indeed, RTF is a much better option than having to resize each and every PDF page. The lack of images is a mild bummer, however.

I quite agree the reader does not work well with PDF documents but I have had no problems converting the documents either directly to word or through txt versions and then as a word document and into the reader. So far, so good with several different efforts. Am also finding it works well with pod casts that I have pulled into I tunes and then into the reader. At this point I am delighted with the thing.

I have created a couple of ebooks from pdf files that seem to display well. Here is how I did it:

1. Open pdf in Acrobat and export to .rtf. For some reason, exports in Gemini and BCL don't work well.

2. Open the .rtf in BookDesigner (the latest) and create an LRF from it, then import to your sony reader. Use the default settings for LRF creation.

I have tried many other methods- re-distilling pdf's with Distiller and Docucom, using Ghostscript, etc. I am in no mood to mess with changing font sizes etc. in a word processor.

The pdf's I used for commercial, non-encrypted. Have no idea why rtf's created from other software don't work well. I used to use Gemini to export to html for the Rocketbook, and it always seemed to work wel....

SPAM!

I have created a couple of ebooks from pdf files that seem to display well. Here is how I did it:

1. Open pdf in Acrobat and export to .rtf. For some reason, exports in Gemini and BCL don't work well.

2. Open the .rtf in BookDesigner (the latest) and create an LRF from it, then import to your sony reader. Use the default settings for LRF creation.

I have tried many other methods- re-distilling pdf's with Distiller and Docucom, using Ghostscript, etc. I am in no mood to mess with changing font sizes etc. in a word processor.

The pdf's I used for commercial, non-encrypted. Have no idea why rtf's created from other software don't work well. I used to use Gemini to export to html for the Rocketbook, and it always seemed to work wel....

I wish the expensive Acrobat would do a better job. However, when it converts PDF to RTF or HTML, it doesn't keep all formatting tags even RTF and HTML support them. It doesn't even keep Italic style. That's a major drawback.

I am going PDF->HTML->BD->LRF route, and have not found a satisfatory way to do the first step. pdftohtml kinda works, but it treats each line as a paragraph and also there is no option to remove header/footer (including page number).

Maybe somebody will write a special version of pdftohtml for the Book Designer.

To throw another dog on the pile: have you tried pdflrf (http://www.mobileread.com/forums/showthread.php?t=13135)?

Hey, that was a good dog! :D

To throw another dog on the pile: have you tried pdflrf (http://www.mobileread.com/forums/showthread.php?t=13135)?

Yep. pdflrf is a good tool, especially for very complex PDF files. I have used it for a few documents. However, it has limitations. It basically converts PDF to images and thus results in very big files. You can not resize fonts, and you can not add your own custom TOC either.

Book Designer still the best tool to create good looking and small lrf files. If only we can find a better way to import pdf into Book Designer without losing most styles.

Book Designer will import PDF. It will lose the ToC, graphics, and styles. And it won't handle DRM or protected PDF. But if you don't mind going through the PDF and then fixing the BD file to match, it'll work.

Book Designer will import PDF. It will lose the ToC, graphics, and styles. And it won't handle DRM or protected PDF. But if you don't mind going through the PDF and then fixing the BD file to match, it'll work.

I know that. That's why I want to convert PDF to HTML first to preserve images and styles.

I know that. That's why I want to convert PDF to HTML first to preserve images and styles.
The other way to try it is to install libprs500 and use pdftohtml and see how it goes. It does keep styles and images (I think).

SPAM!

Hahahah! Finally, someone who has negative karma. Sweet! Teach that 'ol spam monkey! :smash: :rofl:

I am a translator and in my work I sometimes need to convert PDF into more editable format (rtf and doc mostly). I have found out, and my colleagues support that observation, that the best tool to do it is Abby Finereader. It is an OCR program, but with PDF it extracts the text directly from the file.

The big advantage is that you can select exactly what you want to be extracted (for example to skip headers and footers) and how much of the original format is to be maintained.

I realize that it may be expensive for some who do not need to use it often, but I guess Reader users will sooner or later put to use their scanners and digital cameras anyway? An OCR software will be handy, then...

Note: make sure that you draw all the frames manually on the pages (or draw one which suits all the pages, save it and apply to other pages). The automatic recognition is not that great... It make seem to be tedious at first, but it saves a lot of work later.

I wish the expensive Acrobat would do a better job. However, when it converts PDF to RTF or HTML, it doesn't keep all formatting tags even RTF and HTML support them. It doesn't even keep Italic style. That's a major drawback.

I took back my comment regarding Acrobat styles. If you remove all embedded fonts (by PDF Optimizer tool) before converting, it does keep all styles.

I may have missed this somewhere in the threads, but I don;'t see that anyone has figured out how to modify the defaut font so that it starts at 16pt. For my tiured eyes that really is a minimal requirement. If I could do this I wouldn't hve to mess around nearly as much reformaing doc file to single space and 16 pt fonts.
Thanks

I may have missed this somewhere in the threads, but I don;'t see that anyone has figured out how to modify the defaut font so that it starts at 16pt. For my tiured eyes that really is a minimal requirement. If I could do this I wouldn't hve to mess around nearly as much reformaing doc file to single space and 16 pt fonts.
Thanks
There's really no need. You can save the file as RTF and then use rtf2lrf (part of libprs500) to easily and quickly convert it and then you don't need to worry. Besides, you may get the links (not sure) and graphics. Plus you will have a true LRF and it'll be good.

Try this:

www.pdfcropper.com (http://www.pdfcropper.com)