Package for print

Hi all,
I'm creating a javascript that makes a package for print in Indesign CS5. All goes well, the package gets created, but afterwards the fonts in the package seems to be in use until I quit Indesign. Has anyone had this problem, or can anyone help me with this.
Thanks a million.
Best regards,
Jan.
var doc = app.activeDocument;
var ThePackagePath = Folder("~/Desktop/input/test");
doc.packageForPrint(ThePackagePath, true, false, false, false, false, false,false,"",false);

Hi Harbs,
The problem is that we can't process the package in our workflow because
the fonts in the package are still in use by Indesign on the client
machine.
Jan.

Similar Messages

Help! 'Package for Print' Script

Hi all,
I have a specific 'Package For Print' script, that needs a small modification, and and I was hoping someone could help me.
Essentially, I need to OMIT 'Include PDF' option when packaging, since this makes things a bit wonky on my script (see below).
Let me know if you need to see the script, and I'll post it.
Thank you.

Here you go, and thank you. I know notes are also included in it. Sorry about this.
//Package the active document and setup the dockets folder structure.
//The active document shouldn't have been saved (has no name), so provide a name
//taken from the first and only link. After creating the dockets folder structure,
//close and delete the original file and open the file in the docket's originals
//folder.
#target InDesign
//Constants
const PROOF_PREFIX = 'Proof_';
const OUTPUT_SUFFIX = ' Folder';
const ORIGINALS_FOLDER = 'Originals';
const PRINT_FOLDER = 'Print';
const DIGITAL_PROOF_FOLDER = 'Digital Proof';
const CLIENT_FOLDER = 'Client Provided Files';
const DEFAULT_MAC_DOCKETS = '/Users/parham/Desktop';
const PDF_PROFILE = 'Linx_Proof'
function Err() {}
//Use a more user-friendly version than throwing an error.
Err.FatalError = function (msg) {
alert(msg, 'Fatal Error', true);
exit();
function makeShowUI(runtime) {
var doc = runtime.doc;
var window = (function () {
var windowDef = "Window {\
type: 'dialog', \
properties: { \
resizeable: false, \
closeButton: true, \
maximizeButton: false, \
minimizeButton: false \
text: 'Dockets Package', \
orientation: 'column', \
var w = new Window(windowDef);
//Folder name
w.add("StaticText { text:'New Folder Name', alignment: 'left' }");
var defaultName = doc.name;
if (defaultName.slice(-5) == '.indd') {
var origlength = defaultName.length;
defaultName = defaultName.substr(0, origlength - 5);
w.folderText = w.add("EditText { alignment: 'left', characters: 30, justify: 'left', " +
"text:'" + defaultName + OUTPUT_SUFFIX + "'}");
//Destination dir
w.add("StaticText { text:'Save To', alignment: 'left' }");
var dirGroup = w.add("Group { orientation: 'row', alignment: 'fill' }");
w.dirText = dirGroup.add("EditText { characters: 30, justify: 'left', " +
"text:'" + DEFAULT_MAC_DOCKETS + "'}");
w.dirBrowseBtn = dirGroup.add("Button { text: 'Browse...' }");
w.dirBrowseBtn.textBox = w.dirText;
//Package Options
w.options = w.add("Panel { orientation: 'column', alignment: 'fill', \
text: 'Package Options', alignChildren: 'left'}");
w.options.fonts = w.options.add("Checkbox { text: 'Copy Fonts' }");
w.options.links = w.options.add("Checkbox { text: 'Copy Linked Graphics' }");
w.options.profiles = w.options.add("Checkbox { text: 'Copy Color Profiles' }");
w.options.update = w.options.add("Checkbox { text: 'Update Graphic Links In Package' }");
w.options.hiddenContent = w.options.add("Checkbox { text: 'Include Fonts and Links From Hidden and Non-Printing Content' }");
w.options.ignore = w.options.add("Checkbox { text: 'Ignore Preflight Errors' }");
w.options.report = w.options.add("Checkbox { text: 'Create Report' }");
w.options.fonts.value = true;
w.options.links.value = true;
w.options.profiles.value = true;
w.options.update.value = true;
w.options.hiddenContent.value = true;
w.options.ignore.value = true; //Parham's request for true
w.options.report.value = false; //Saeed's request for false (no instructions)
//Digital Proof
w.proof = w.add("Panel { orientation: 'column', alignment: 'fill', \
text: 'Digital Proof', alignChildren: 'left'}");
w.proof.make = w.proof.add("Checkbox { text: 'Make PDF Proof' }");
w.proof.viewAfter = w.proof.add("Checkbox { text: 'View PDF' }");
w.proof.make.value = false;
w.proof.viewAfter.value = false;
//OK / Cancel
var buttonDef = "Group { orientation: 'row', alignment: 'right', alignChildren: 'right' }";
w.bg = w.add(buttonDef);
var okDef = "Button { text: 'OK', alignment: 'right' }";
var cancelDef = "Button { text: 'Cancel', alignment: ['right', 'center'] }";
w.okBtn = w.bg.add(okDef);
w.cancelBtn = w.bg.add(cancelDef);
return w;
runtime.window = window;
window.dirBrowseBtn.onClick = (function () {
var result = Folder.selectDialog('Choose destination directory');
if (null !== result) {
//Replace string with selected path
this.textBox.text = result.fullName;
return window.show();
function deleteFolder(folder) {
if (!folder.exists) {
return;
var children = folder.getFiles();
for (var i = 0, im = children.length; i < im; i++) {
if (children[i] instanceof Folder) {
deleteFolder(children[i]);
} else {
children[i].remove();
folder.remove();
//Main path
try {
var a = app.activeDocument;
} catch (e) {
Err.FatalError("No document open");
var runtime = {};
var doc = app.activeDocument;
runtime.doc = doc;
if (doc.saved) {
//Document has already been saved (already has a name), so stop.
Err.FatalError("Document has already been saved");
//Ensure at least one link, since multipaged PDFs end up as more than 1 link.
if (doc.links.length < 1) {
Err.FatalError("Document has " + doc.links.length + " links.");
//Save the existing file in a temporary place, same dir as first link.
//Take the name from the first link
var link = doc.links.firstItem();
var defaultName = link.name;
if (defaultName.slice(-4) == '.pdf') {
var origlength = defaultName.length;
defaultName = defaultName.substr(0, origlength - 4);
} else {
//Placed item is not a pdf, as per Parham's request, don't warn about it.
//Just take the filename best guess and go with it.
// if (confirm('Linked item is not a PDF. Package anyways?',
// true, 'Package non-PDF')) {
//break on the last '.'
var lastIndex = defaultName.lastIndexOf('.');
if (lastIndex > -1) {
defaultName = defaultName.substr(0, lastIndex);
} else {
defaultName = defaultName;
// } else {
// alert('Did not package.');
// exit();
//filePath should be a File, but is actually a string, so make a file.
var linkFile = new File(link.filePath);
var origFile = new File(linkFile.path + '/' + defaultName + '.indd');
if (origFile.exists) {
//Folder already exists, get user to confirm
if (confirm("File " + defaultName + '.indd already exists. Replace?',
true, 'Replace File')) {
//Erase the temp file
origFile.remove();
} else {
alert('Did not overwrite existing files, did not package.');
exit();
doc.save(origFile);
if (2 == makeShowUI(runtime)) {
//User pressed cancel
exit();
//Main code, do the packaging and make the directories.
//But first check for existing folder.
var folderName = runtime.window.folderText.text;
var destinationPath = runtime.window.dirText.text;
if (destinationPath.slice(-1) == '/') {
var newFolderPath = destinationPath + folderName;
} else {
var newFolderPath = destinationPath + '/' + folderName;
var outputRoot = new Folder(newFolderPath);
if (outputRoot instanceof Folder && outputRoot.exists) {
//Folder already exists, get user to confirm
if (confirm('Dockets folder ' + folderName + ' already exists. Replace?',
true, 'Replace Folder')) {
//Erase the destination directory
//Get all contained files + folders, then delete them.
deleteFolder(outputRoot);
} else {
alert('Did not overwrite existing files.');
exit();
} else if (outputRoot instanceof File) {
//Destination folder exists as a file, fail.
Err.FatalError('File named ' + folderName + ' already exists, cannot make folder.');
//Destination doesn't exist, create it.
if (!outputRoot.create()) {
Err.FatalError('Error creating folder ' + folderName);
//We have an empty directory, now do the packaging and everything else.
var printFolder = new Folder(newFolderPath);
printFolder.changePath(PRINT_FOLDER);
if (!printFolder.create()) {
Err.FatalError('Error creating Print folder.');
var digitalProofFolder = new Folder(newFolderPath);
digitalProofFolder.changePath(DIGITAL_PROOF_FOLDER);
if (!digitalProofFolder.create()) {
Err.FatalError('Error creating Digital Proof folder.');
var clientFolder = new Folder(newFolderPath);
clientFolder.changePath(CLIENT_FOLDER);
if (!clientFolder.create()) {
Err.FatalError('Error creating Client folder.');
var originalsFolder = new Folder(newFolderPath);
originalsFolder.changePath(ORIGINALS_FOLDER);
if (!originalsFolder.create()) {
Err.FatalError('Error creating Originals folder.');
//Do the package
var f = runtime.window.options;
if (doc.packageForPrint(originalsFolder, f.fonts.value, f.links.value, f.profiles.value, f.update.value, f.hiddenContent.value, f.ignore.value, f.report.value, false, true)) {
} else {
Err.FatalError('Failed to package.');
//Do the PDF proof
if (runtime.window.proof.make.value) {
var proofname = PROOF_PREFIX + doc.name;
if (proofname.slice(-5) == '.indd') {
var origlength = proofname.length;
proofname = proofname.substr(0, origlength - 5);
proofname = proofname + '.pdf';
var proofFile = new File(digitalProofFolder.fullName + '/' + proofname);
if (proofFile.exists) {
Err.FatalError('Digital proof already exists.');
} else {
var exportProfile = app.pdfExportPresets.itemByName(PDF_PROFILE);
//We get an object even if the profile doesn't exist, have to check isValid
if (!exportProfile.isValid) {
Err.FatalError('PDF profile ' + PDF_PROFILE + " doesn't exist, digital proof not created.");
//Explicitly set to export all pages.
app.pdfExportPreferences.pageRange = PageRange.ALL_PAGES;
//Set view preference
app.pdfExportPreferences.viewPDF = runtime.window.proof.viewAfter.value;
doc.exportFile(ExportFormat.PDF_TYPE, proofFile, false, exportProfile);
//Open the Originals folder .indd, close the current file and delete it.
var newFile = new File(originalsFolder.fullName + '/' + doc.name);
if (!app.open(newFile)) {
Err.FatalError("Failed to open packaged .indd");
doc.close();
origFile.remove();

Packaging .AI file to PDF ready for printer - MAC Tiger user

Hallo, I need some help please about sending artwork to printer who is using a FUJI colour Laser printer. (like most printers who are using laser here they reply to me to simply send them PDF, when I ask about embedded profiles or not to embed they tend to look at me blankly and say just send them a proof for me to compare colours)?!?!?!?
So, Please could someone confirm wether or not I have applied the best setting in my PDF conversions: I am running CS3 creative suite and acrobat version 8.0. thanks.
When you get the PDF options window on the " save Adobe pdf", On the first GENERAL page I set this to PDF/x-1a, (but why is there also the standard tab where I can do the same thing? so I set this also to PDF/x-1a. The compatibility goes to acrobat 4.0.
I now go to OUTPUT. here I set the following:
Colour conversion -- convert to destination preserve numbers
Destination (since this is laser I set it to -- Generic cmyk profile
Profile inclusion policy is grayed out.
In PDF/X box under output intent profile name is set to Generic cmyk, and that is all.
Before i did all this my global colour settings management policy is set to FOGRA27 (iso 12647-2:2004) and adobe RGB 1998 for the photos from photoshop cs3 of course. I then convert the document to the generic cmyk profile before packaging it into PDF and assigning these settings.
I have searched everywhere for detailed tutorials about precisely how to pakage your work for an outside printer, but the web is silent when it comes to laser printing. I would love to know if there are any resources which cover all the issues of preparing your artwork for print since this side of the job is a minefield of complicated presets and flattening and font changing techniques.
I am a memeber of Lynda.com and while they are excellent teachings and professional, I have unfortunately not been able to learn the gritty detailsof printing from them, only the basics.
I appreciate the person who takes the time to reply to this.
I thank you.
Kind regards
Chris Watts

Your settings should do the job adequately, but there is a much simpler and more reliable method. Get Acrobat Professional. Generate your artwork in AI and save it as an .eps file. Then use Acrobat Distiller to generate the .pdf file. The advantages are that AD produces MUCH smaller file sizes, much better .pdf files and has a number of presets from which to choose, depending on the intended purpose of the file.
Another hint as far as quality control is concerned - you should be working in the CMYK color space in Photoshop, if you are going to produce CMYK images in the .pdf file. CMYK is a narrower color space than RGB, so there is often a color shift upon conversion. You may have the image exactly the way you want it, as an RGB, but be disappointed in the printed version because of the shift in color during conversion. If you work in CMYK, you can adjust it to get the results you want.

Failed to package book for print - now hundreds of links are broken

Hi,
I have a book document with 32 pages (newspaper) locally on my mac. As I always do after finishing my document, I chose to package the book for print, and save it to CC files server. The packaging process never finished, so after 30 minutes I had to force shut-down on InDesign. When re-opening the book file, I discover that ALL the documents has broken links. Some of the links belongs to the master pages, and most are specific to only this document, and they are located in several different folders on my mac. It will take hours to re-locate all of this links for each page.
I think I have been experiencing this before, but miraculously it all changed back to normal. Now, however, a restart of my mac didm´t do anything.
Why is this happening, and do anyone have a quick solution to fix this?
Thank u in advance

Are you talking about what I said - "Seems like in the past, I saved a copy of my book, then packaged the copy for print?"
I thought that was the only way around it. I feel certain I will not make this mistake again. Luckily, most printers I work with prefer pdfs. It's just an insane bug. If it's not a bug, it's a major flaw in the program. People do package books. The option wouldn't be in there if we didn't do it sometimes.

CS3 - Broken hyperlinks after Package Book For Print

I've posted a similar problem here a few weeks ago, but no answers, so hopefully I can get some help here with a more specific problem description...
I have created a an INDB, including several "chapter" INDD files, linked PNG images and hyperlinks to text and URL anchors throughout. Once I have everything complete, I select all the INDD files and do a "Package Book for Print", making sure the Preflight finds no problems, and then save the packaged INDB folder in a new directory on my local drive.
All works fine in the new INDB, EXCEPT that any hyperlink that points to a text anchor in a different INDD is broken.Apparently, the hyperlink is still pointing to the original INDD's absolute location rather than the new INDD text anchor within my newly packaged INDB. All Hyperlinks that point to a text anchor in the same INDD are fine.
I do not see any option to change this behavior. Strange though, that if I go to edit one of these "broken" hyperlinks, as soon as I choose the correct INDD that it should point to, then it correctly chooses the right link destination automatically in the edit dialog, so obviously it has stored the correct text anchor info, but just loses the document it should point to.
Is there any way to avoid this problem? It is a real pain to keep fixing hyperlinks every time a package my INDBs. I've heard some people use a 3rd party plugin to remedy this and other InDesign link problems (but I forget the plugin name). Suggestions??
Thanks!

Are you talking about what I said - "Seems like in the past, I saved a copy of my book, then packaged the copy for print?"
I thought that was the only way around it. I feel certain I will not make this mistake again. Luckily, most printers I work with prefer pdfs. It's just an insane bug. If it's not a bug, it's a major flaw in the program. People do package books. The option wouldn't be in there if we didn't do it sometimes.

Packaging typekit fonts for print

When you're collecting for output/packaging a print project from InDesign and you're using Adobe Typekit, the Typekit fonts will not be packaged. Will there be any sort of warning or message so that both the artist and the print vendor are aware those fonts need to be replaced? It would also be helpful if the message mentioned Typekit so that the vendor knew where to obtain the fonts. I speak from experience, being both a designer and working for a commercial printer. Knowing whether to apply our Typekit fonts or to go back to the client for the fonts is very important.

http://forums.adobe.com/community/indesign
This forum is about the Cloud as a delivery process, not about using individual programs
If you start at the Forums Index http://forums.adobe.com/index.jspa
You will be able to select a forum for the specific Adobe product(s) you use
Click the "down arrow" symbol on the right (where it says ALL FORUMS) to open the drop down list and scroll

AUR package for konica minolta laser printer (CUPS)

Hi there,
currently I'm writing a AUR package for the Konica Minolta Magicolor 5430 Desklaser.
I have a question to put the ICC profiles files and special KM files to the cups tree.
The Konica Minolta makefile put the binary "rstertokm5430" to the directory "/usr/lib/cups/filter/" which is completely correct but the *.ppd file and *.icm files are going by default to /usr/share/KONICA_MINOLTA/mc5430DL/Profiles (icm files) and to
/usr/share/cups/model/KONICA_MINOLTA/km5430dl.ppd.gz (ppd file)
The directory in my running archlinux is
usrsharecupsmodel*.ppd and
usrsharecupsprofiles*.icm
Additionally there are "Halftones" files (*.bmp)
usrshareKONICA_MINOLTAmc5430DLHalftones*.bmp
I think about to put the Konica Minolta files in to this (new) directory tree:
usrsharecupskm5430dlmodel*.ppd
usrsharecupskm5430dlprofiles*.icm
usrsharecupskm5430dlhalftones*.bmp
How do I have to copy these files to be archlinux compliant ?
best regards,
Frank

frigg, my apologies for overlooking an important point in my last post. The three magicolor drivers have different version numbers, unlike the other examples of multiple printer drivers in one PKGBUILD. This means you will need one PKGBUILD for each driver, in order to have the correct Arch version number. There is still value in doing them together, since they have many common elements.
As a consequence of this change, I think it might be best to put the single PPD file in /usr/share/cups/model/, rather than have a directory with one ppd file in it. It appears that the KM_PPDDIR variable in the configure script controls this location, so I have added a sed command to the build script accordingly.
As another consequence, the package names need to be changed. I would suggest cups-mc2430dl, etc. This uses the short internal names used by the drivers, and Arch package names are supposed to be lower-case. This means that your awk script no longer works for all three drivers. Rather than write three different awk scripts, I have ported your directory change to a sed command. When you package a stand-alone script with the PKGBUILD, you have to also maintain its md5sum, so it is simpler to do everything inside the build script if you can.
Following are the three incomplete PKGBUILD scripts incorporating these changes. They are complete enough that when you run makepkg, they will download the tarball (if it isn't already present), check its md5sum, copy it into the src directory, uncompress it, and modify the configure script. One way for you to proceed from here is to add lines to the build script, run makepkg, check that the right things happen in the src directory, and then that the correct things are put into the correct place in the pkg directory. The next line in the build script runs configure, which won't finish on my system due to the lack of libjbig.
# Contributor: Frank Ickstadt (frank dot ickstadt at gmail dot com)
# For Konica Minolta magicolor 2430 Desklaser
pkgname=cups-mc2430dl
pkgver=1.6.0
pkgrel=1
pkgdesc="CUPS driver for Konica Minolta magicolor 2430 Desklaser printer"
url="http://konicaminolta.com/"
license="GPL"
depends=('cups' 'gcc')
source=(http://www.linuxprinting.org/download/printing/konicaminolta/magicolor2430DL-$pkgver.tar.gz)
md5sums=('a97b4ee5c949ca791764457ead3a5b9c')
build() {
cd $startdir/src/magicolor2430DL-$pkgver
sed -i '/KM_PPDDIR/s//KONICA_MINOLTA//' ./configure
sed -i "/KM_DATADIR/s/KONICA_MINOLTA/$pkgname/" ./configure
#./configure --prefix=/usr
#make || return 1
#make prefix=$startdir/pkg/usr install
# Contributor: Frank Ickstadt (frank dot ickstadt at gmail dot com)
# For Konica Minolta magicolor 5430 Desklaser
pkgname=cups-mc5430dl
pkgver=1.8.0
pkgrel=1
pkgdesc="CUPS driver for Konica Minolta magicolor 5430 Desklaser printer"
url="http://konicaminolta.com/"
license="GPL"
depends=('cups' 'gcc')
source=(http://www.linuxprinting.org/download/printing/konicaminolta/magicolor5430DL-$pkgver.tar.gz)
md5sums=('1460477f2dd195c301e961a6cbfe1f54')
build() {
cd $startdir/src/magicolor5430DL-$pkgver
sed -i '/KM_PPDDIR/s//KONICA_MINOLTA//' ./configure
sed -i "/KM_DATADIR/s/KONICA_MINOLTA/$pkgname/" ./configure
#./configure --prefix=/usr
#make || return 1
#make prefix=$startdir/pkg/usr install
# Contributor: Frank Ickstadt (frank dot ickstadt at gmail dot com)
# For Konica Minolta magicolor 5440 Desklaser
pkgname=cups-mc5440dl
pkgver=1.2.0
pkgrel=1
pkgdesc="CUPS driver for Konica Minolta magicolor 5440 Desklaser printer"
url="http://konicaminolta.com/"
license="GPL"
depends=('cups' 'gcc')
source=(http://www.linuxprinting.org/download/printing/konicaminolta/magicolor5440DL-$pkgver.tar.gz)
md5sums=('abd54f32517ebeb7a56f902b159c7dea')
build() {
cd $startdir/src/cups-mc5440DL-$pkgver
sed -i '/KM_PPDDIR/s//KONICA_MINOLTA//' ./configure
sed -i "/KM_DATADIR/s/KONICA_MINOLTA/$pkgname/" ./configure
#./configure --prefix=/usr
#make || return 1
#make prefix=$startdir/pkg/usr install

HP Instructions for Printing and Scanning Under Snow Leopard

HP has posted instructions for Snow Leopard users for printing, faxing, and scanning on HP printers.
While the scan button (and installed HP printer management software) may no longer work on the printer, you can still scan if you go through the Preview or Image Capture programs on your Mac to access the scanner.
I tried it on my HP Officejet Pro 8500 wireless printer that was unable to scan after upgrading to Snow Leopard, and it worked.
HP has posted the printer instructions for Snow Leopard at: http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01846935&cc=us&lc=en&dlc=en &product=1153481
Hope this helps some of you. It worked for me.

You can download VueScan as a trial without paying for it unless you want to.
As for enabling scanning with Image Capture you need the proper driver. As a start I would ask HP's tech support if they can help you get it working. Apple does not write any printer or scanner drivers. They are provided by HP or other printer manufacturers. Apple packages them for distribution with OS X. It's quite possible that the current scanner driver for your model isn't compatible with SL.
If you understand modern technology then you have to appreciate the fact that most things become obsolete within months. This is certainly true of computers and their peripherals. Software developers cannot keep up the pace with the hardware. A two year old printer has been obsolete for more than a year already. Unless HP still sells and manufactures that model, they tend to lose interest with them. SL only arrived in October 2009 which is after your model was released. So HP needed to provide compatible drivers. If they have then perhaps the problem with yours is related to something else, but I don't know what that would be beyond completely uninstalling all the HP software then letting the OS figure out what to install. SL automatically discovered both my printer and scanner, then installed the drivers for each.

Find exact package for saving the workbech request for std SAP object

Hello friends I have edited a std SAP prog for printing the import PO(got access key from market place).After editing while creating transport request I am not able to find the package to which it should be saved.now the problem is that How to move that program to our quality server.
the program is
/1BCDWB/LSF00000063TOP

Hi achal,
are you sure you modified a standard SAP object. /1BCDWB/ prefix is common with all quick view reports - they are local and user-specific. You can convert a quickview to query to report. Using a modification key you may add it to the standard - choose a package as you prefer. But better copy the generated query report to customer name space - because it never was and never will be SAP standard. If it is in customer name space, release changes are no problem at all.
Regards,
Clemens

RE: what is the standard driver program for printing PO form in ECC 6.0EHP5

Hi Guys,
For printing Purchase order smartform in MM module , earlier i used SMBA0 package i.e /SMBA0/AA_FM06P Driver program in Ecc 6.0 Ehp4 . But now my client is using Ehp5 ,here we could n't find SMBA0 package . So, can any one suggest me what is the relavant package for SMBA0 in Ecc 6.0 EHP5.
Thanks in advance.
Regards,
Bala.

Hi Bala,
Those are available in client 000, you have to copy these Smartforms and driver programs from client 000.
Client 000
Original program: /SMBA0/AA_FM06P
Original Form: /SMBA0/IN_MMPO
Regards,
Surya

Cropping for print

I have looked all over for this information but can't seem to find it - sooo if you are cropping a photo to send to a lab for print, I have heard that you need to make it a little smaller than the required output size because the labs allow a certain leeway for printer 'error'. In other words, a 4 X 6 inch print should be sized 3.89 X 5.68 (I made these numbers up!). My question is (are) then is there a formula for deciding how much smaller to make the print size? Is there a chart? Is each lab noticibly different?
Thanks for advice,
j.

First time I ever used their service. So Noobie lessons for me. lol.
The more I use their machine the better I'll understand all the options. And thanks thats good to know.
For now I am using the fuji machine at Walmart. (Oh I can see the shuttering faces)
I figure it the best for me at the moment until I need a pro service.
Do you know if it can handle a picture package. I thought I saw that option for a single image on the machine. I am assuming that you just pick the 8 x 10 size and it should handle a jpg of that size.
Though the file size would be huge. I just got the Canon 40D about a month ago. So lessons there as well.
BTW does anybody know why the Kodak machine can not read a compactFlash card. But the Fuji Machine can?
Sorry for getting a little off topic.

Arranging the placement and order of photos for print or web

This is something I was expecting with the first Lightroom and it still seems to be clunky in 2.3...
Basically, there doesn't seem to be a way we can simply click and drag photos we want to be together and have them in orders of our choosing. The closest I've been able to find is when in picture package mode in the Print section. What is frustrating is that when I select most other templates, I can't just move the photos I want grouped together to where I'd like them to be. On the flip side, when in the picture package mode and I populate the frames by dragging photos to them, unlike contact sheet/grid mode, one can't move the photo around within that frame...
My understanding of Lightroom was that it made it easy for photographers to deal with their photos. For me, I like to be able to just move and group fluidly for print and web to see how pictures complement and flow regardless of tag, filename, or random selected order.
I can't imagine I'm the only one with this frustration, is there a remedy?

Thanks for that everyone you were right! I was being super-DUper sMart and Brilliant there and had only been trying to re-arrange within the layout window of the Print and Web areas. I think I was just assuming I was having the same trouble from Lightroom 1 and just stopped trying since it seemed the files either never moved or didn't stick (can't remember now). In any case, Thank you!

Flatten an image for printing

I have been working on my logo with Illustrator CC and I needed to print my logo. And I used the .ai file and placed into a InDesign CC document and exported it as PDF for print.
But this is the result of the printed PDF:
and I was talking to the people at the printing place and they said it wasn't flattened properly. So they flattened it on their printer and came out the way it should.
I used Package feature on InDesign and used High Quality Print preset from PDF presets and I also tried PDF/X-1a:2001 preset too with same issue.
I was wondering does this feature doesn't flatten images? Or is there other way of flattening on Illustrator or InDesign. My logo consists of lines with stroke.

marrto wrote:
I thought placing a .ai file of the logo in InDesign would be the proper way of doing it.
You are correct about that.
And the lines of my logo are actually a rectangle tool with rounded corners effect.
Okay well, at least that explains the difference between the two images in your original post. The output reported to be "not flattened properly" appears to have lost the live Round Corners effect. A logo graphic should never include a live effect. You could apply Object > Expand Appearance to those elements to make the results of the effect permanent.
The printing company didn't explain it to me very well.
That's true. The term "flattening" was misused.

Package or Print PDF?

I'm sure there are situations where packaging the indesign document and sending over all the files is better than exporting a high res PDF for print, but what would these be? Simply when the printer needs to make changes? What changes would these be that can't be done by me or to a PDF?

" (but be sure you ask for the settings they want you to use if they do take
PDF)."
Could you please explain this a bit further? Do you mean, selecting 'press
quality' or 'high quality print' etc., plus other settings? What are the
best for a mixed text/image doc where most images are screenshots and there
are some photos?
We have to send some docs to the printer soon and while we sent a batch a
while ago and the printer didn't ask for settings, and the finished product
was fine, perhaps the product would be even better with the exact required
settings (if our printer knows what those are).
Thank you!

Are typekit fonts available for print?

Can typekit fonts be packaged up as per fonts on my desktop?

Hello patcsant,
Thanks for your interest in Typekit. The Typekit Services Agreement does not permit Typekit desktop fonts to be transferred to another user or computer that isn’t already licensed for that font. This means that anyone you wish to share the document with (e.g. a colleague or a printer) needs to have their own license for the font, either through Creative Cloud or as a traditional desktop license.
You can read more on packaging fonts here:
http://help.typekit.com/customer/portal/articles/1166052
Synced font data may be embedded in PDF and other digital documents, though. Creating a PDF file is, in most cases, the best and most reliable way to ensure typographic fidelity in documents destined for print output.
I hope that this helps; let me know if you have any other questions. Best,
-- liz

Package for print

Similar Messages

Maybe you are looking for