Re: indesign CS3 PDF export on 10.5
Re: indesign CS3 PDF export on 10.5
- Subject: Re: indesign CS3 PDF export on 10.5
- From: Håvard Graudo <email@hidden>
- Date: Mon, 14 Apr 2008 13:30:49 +0200
Den 14. apr. 2008 kl. 12.41 skrev Wayne Melrose:
On 14. april. 2008, at 12.28, Håvard Graudo wrote:
Den 12. apr. 2008 kl. 20.49 skrev Wayne Melrose:
On 9. april. 2008, at 10.50, Håvard Graudo wrote:
I am updating and correcting my own posting here:
The errors on output are *not* only on 10.5.
I got missing images in PDFs from a 10.4 Mac Pro yesterday.
Prime suspect is currently InDesign 5.02 update.
Statistics:
Yesterdays job was 12 pages, One layer with 309 pictures. + 10
layers with only text.
Output was 10 similar 12 page PDFs, with only text different. 6
random pictures was missing on random PDFs
This is very, very bad. Is anyone reliably exporting PDFs from
InDesign 5.02?
Håvard
Den 4. apr. 2008 kl. 16.43 skrev Håvard Graudo:
I have a couple of similar scripts that have been running on
InDesign CS3 on OS 10.4.
They have exported thousands of pages for print and are
considered tried and tested.
When moving users to OS 10.5 I sometimes get horrible errors.
Most of the time it works, but I can get any of these:
A random picture missing in the PDF
Clipping paths ignored on some pictures
Pictures are upside down (!)
I am in the early stages of investigation, but I have found this:
* It only happens when I script the PDF export.
* It seems to happen at random
* error rate is low with <1% of the pictures effected
* errors are not consistent.
* Pictures are EPS with JPEG encoded data and clipping paths
* I have only run into this on Intel-boxes
Has anyone else seen this?
Håvard
Here is a boiled down script that will export every open
InDesign document. Saved as an app and run from Script panel.
I removed all the errorchecking so I may have screwed up
something as well. This approach has worked flawlessly on OS 10.4.
---
property convertSpotToProcess : true
my main()
on main()
tell application "Adobe InDesign CS3"
set alleExportFormater to name of every PDF export preset
set alleDok to name of every document
tell document 1
set valgtExportFormat to (choose from list
alleExportFormater with prompt "Hvilken utskriftsMal skal
brukes?")
if valgtExportFormat = false then error number -128
set targetmappe to my velgmappe()
end tell -- doknavn
set valgtExportFormat to PDF export preset (valgtExportFormat
as text)
repeat with ggg in alleDok
set doknavn to ggg as text
tell PDF export preferences
set page range to all pages
end tell
set filnavn to doknavn
if filnavn ends with ".indd" then set filnavn to text 1 thru
-6 of filnavn
set filnavn to filnavn & ".pdf"
tell document doknavn
if convertSpotToProcess then set convert to process of
(every ink whose is process ink is false) to true
set targetfil to (targetmappe & filnavn) as string
with timeout of 40 * 60 seconds
export format PDF type to targetfil using
valgtExportFormat without showing options
end timeout
delay 1
end tell
end repeat
say "Your PDFs are ready"
end tell
end main
on velgmappe()
try
tell me to activate
end try
return (choose folder with prompt "Hvor skal PDFene legges?")
end velgmappe
---
Hey Håvard,
We're using indesign 5.02 / 10.5 and intel boxes all day to
export pdfs.. Have not seen anything of the sort. Considering
that you're office is less than 5km from where I work, I guess
it's not a problem with Oslo ;)
Mind, we do not really use eps files with clipping paths, THIS
would be my place for starting.. I'd be checking those images,
checking those images exported normally (not using applescript)
then trying to re-create those errors with applescript, Would
also suggest resaving your images in photoshop, see if that helps
at all?
If you want to, you can send me a copy of a problem file/links,
and i'll try and re-create the error here too.
Lykke til!
Wayne
Takk Wayne!
Do you export by script or manually?
Errors are too rare and random to be linked with a specific image.
It has happened with photoshop EPS, Illustrator EPS and
Illustrator .ai files. It has happened when I have the same image
file twice on a page; One is OK - its twin missing. It can happen
when I have all images in one layer + many text only layers ('same
products different prices'), then when I script export of the
image layer + each of the text layers in succession I can have a
random image exporting perfectly OK on 19 out of 20 PDFs, and
missing on one. Next export is OK.
The error rate is very low, maybe 1 in every 5000 images.
The PDFs with missing images are all valid PDF/X-1a files and I am
unable to flag them by PitStop Server.
Pictures are usually quite big, 30-60MB, often with hand-drawn
clipping paths (sometimes complex like bicycles), and there may be
hundreds of images in a single InDesign file. But the missing file
may be a 50k logo. I am currently suspecting a memory related
error in InDesign 5.02 that is easiest triggered when a script is
exporting large amounts of data. There are no traces in any logs.
Macs have around 5GB RAM. One script may use over 1 hour to export
one batch of PDFs. Image and logo server is Helios UB+ on Solaris.
No traces in server logs either.
This workflow has been error-free for months, but I now have at
least one error every week.
I am currently unable to reproduce the errors predictably.
I have still only seen it on InDesign 5.02
Am I the only one seeing this?
Håvard
Bare hyggelig!
well, it sounds pretty random ;) and you say when you re-produce
that single page again, the error is gone?
1. Do the image names exist in more than one place (do you have
different images called the same thing)
2. Do the image names contain "æ" "ø" "å"?
3. I assume that they are already corrupt before then get to
Helios? Can you rule out Helios?
Haven't seen anything like this.. We do have a script similar in
code to yours, although we have actually scripted the export
preferences rather than using an export style.
Wayne
Yes it is very random, and that makes is difficult to catch.
Exporting again and the error is gone.
1) There are plenty of identical filenames on our server - (every
file has an OPI files for once!), but I cannot see how this should
suddenly be a problem. We do use descriptive file names, not
'IMG0001' etc. (We do not use OPI with InDesign, and I am *very* sure
this is not caused by placing an OPI file in InDesign by mistake)
2) strictly lowercase, low ascii. <31 characters.
3) PDFs ar bad right out of InDesign. I cannot rule out Helios during
creation of PDFs.
If nobody else is seeing this with applescript/InDesign 5.02 it could
be server-related.
Håvard
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden