I'm converting pages documents to PDFs with the export function no problem but when the content of the PDF is copied and pasted to somewhere else (like Notes), I'm getting exclamation points at the end of every line. Any ideas why or how to correct that? I have Pages 5.2 and Preview 7.0 . Thanks
MacBook Pro with Retina display, OS X Mavericks (10.9.4)
I know it is a years-old post, but I think there is a easy fix for a bad.pdf file that has the exclamation-mark problem. I think it should work in most cases. In a nutshell: Print the pdf as a postscript (.ps) file, then open the bad.ps, and Preview will convert it back to a (fixed) Untitled.pdf file that does NOT have the exclamation-point problem. Below is a step-by-step illustrated procedure ...
Finder: Prefs: Advanced. Make sure you have checked (enabled) "Show all filename extensions" (for your sanity!)
Open bad.pdf in Preview.
File -> Print
In Print dialog at lower left, under "PDF" select "Save as Postscript..." (see screenshot below). This will create a new file bad.ps (same name as the pdf file except ends in .ps instead of .pdf).
Double-click bad.ps to open in Preview, and Preview will convert the .ps to a new Untitled.pdf file that does not have the exclamation-point problem.
I know it is a years-old post, but I think there is a easy fix for a bad.pdf file that has the exclamation-mark problem. I think it should work in most cases. In a nutshell: Print the pdf as a postscript (.ps) file, then open the bad.ps, and Preview will convert it back to a (fixed) Untitled.pdf file that does NOT have the exclamation-point problem. Below is a step-by-step illustrated procedure ...
Finder: Prefs: Advanced. Make sure you have checked (enabled) "Show all filename extensions" (for your sanity!)
Open bad.pdf in Preview.
File -> Print
In Print dialog at lower left, under "PDF" select "Save as Postscript..." (see screenshot below). This will create a new file bad.ps (same name as the pdf file except ends in .ps instead of .pdf).
Double-click bad.ps to open in Preview, and Preview will convert the .ps to a new Untitled.pdf file that does not have the exclamation-point problem.
FWIW, my bad.pdf with the exclamation-mark problem was created in Pages, with Preview showing "PDF Producer:
Mac OS X 10.10.5 Quartz PDFContext".
Notes seems to be showing exclamation points where there are multiple paragraph returns in a row.
This maybe the pdf parser in Preview not getting what is happening at the double returns, because it is hiding or misplacing the text between the multiple returns.
A quick test in TextEdit doesn't reproduce the problem however, Pages has something else at those paragraph returns.
I'm curious why your workflow requires this however.
Peter
Thanks for the quick response Peter.
As for work flow, I'm sending copy to my web developer that will used on sales pages he is creating for me. It's important to me that aspects of the fonts, colors, capitalization and spacing stay consistent when he transfers it to the page. A PDF that he can simply cut and paste the content makes it easier.
Is that what you were looking for? Maybe there is a better way to do that considering he (and others on my team) are not using a Mac.
Why not give it to him as a Word, .rtf or txt document?
Pages is not essential, but it does export to all of those (Pages 5.2 does not export to .rtf)
Peter
With all the other document types, the layouts of the content get messed up to varying degrees. I guess I may just have to convert the document to word or something and then go in and change everything back to the way I want it. Kind of a waste of time.
Hi Brad we are experiencing the same issue , we are producing scripts as pdf then sending these to our client who is cutting and pasting onto a website.
We have tested exporting from pages as a word doc, but still experiencing the same issue.
We also noticed this when cutting and pasting from a pdf produced by pages and pasting into our ibooks.
Have just sent a plain text format to our client so will keep you posted.
On OS X 10.9.4, using Pages v5.2.2, Preview 7.0, and Notes 2.0. English language and keyboard.
Export 5 pages of Lorem Ipsum text in Baskerville to PDF from Pages. Open the PDF in Preview, and launch Notes. Copy and paste 3 paragraphs of content from Preview to Notes. Formatting is retained. No exclamation points found. Notes paste undo. Paste and Match Style from Preview to Notes. Formatting lost, and no exclamation marks.
I repeated the above with 3 paragraphs of content that contained an image, strike-through, and hyperlink styling. The image and styling were stripped from the paste, which retained paragraph format. Paste undo. Paste and match style lost format, but in either case, could not reproduce your exclamation marks.
It is a bad idea to send a Web developer content in MS Word documents. The wrong copy/paste behavior between MS Word, the browser, and the web content editor (e.g. Drupal 7 editor) can embed Microsoft document styling code into the web content, where it decidedly does not belong. This adversely impacts web page layout, behavior, testing, and developer productivity. From personal experience, I expended much time cleaning up MS Word web artifacts during a large site migration in 2013.
Exclamation points on every line.
