Open GoogleCodeExporter opened 9 years ago
Thank you for the bug report kkoleda.
Is the problem PDF specific? Export a group of pages to a different format and
see if
the problem persists.
If pdf specific a workaround is to print to a virtual pdf printer (e.g.
pdfcreator,
primo pdf both of which are free). This has solved many arcmap2pdf problems for
me in
the past with font and fill drop outs and inappropriate font subsitution (which
were
unrelated to mapbook).
If not pdf specific, and your project small and shareable, we could try
reproduce it
on my machine: Upload the .mxd and minimum data needed to demonstrate the
problem to
http://groups.google.com/group/arcmapbook/files.
Original comment by map...@gmail.com
on 29 May 2009 at 5:12
[deleted comment]
Have the same error as described above. Tried "printing" to 2 separate PDF
writers
(1 via Adobe suite, 1 via PDFCreator) -- Both returned printing errors (half
pages,
error messages, etc) and did not "workaround" the text color problem. ESRI
will not
help since MB is non-standard (although, the File->Export Map... does work
correctly,
but defeats the purpose of MB to automate some 200 maps in one MXD)
Original comment by jay...@gmail.com
on 18 Dec 2009 at 9:06
Do the same errors occur with the same text in the same places? (e.g. on Map#3
in the
lower left Fobbar River is always red). If you export/print in smaller batches
(e.g.
20 maps at a time instead of all 200) does it still happen? Do the problems
occur if
the maps are printed to a real printer? What about when printing to pdfcreator
and
the autosave output is set to an image format instead of pdf?
In the past I've had partial page output to real printers (hp designjet) when
I've
not had enough memory or disk space. Open the print queue and watch the print
job
spool, and make sure there is at least 3 times as much free space as the print
job.
Original comment by map...@gmail.com
on 19 Dec 2009 at 12:17
Original issue reported on code.google.com by
kkol...@gmail.com
on 29 May 2009 at 3:35