- About Griffin Press
- Major Publishers
- Small & Self Publishers
- Showcase
- Resource Centre
- Request a Quote
- Environment
- Community
File Naming
An extremely important part of File Preparation is the way the files/images/links are
named. If a file is named in a manner that is not compatible with the majority of
systems that Pre-press departments use globally, then it can cause many issues which may very well endanger the delivery date, final correct production, final book legability!
If you follow the very basic instructions listed below, then you can avoid the above
problems;
• All file names must be no more than 31 characters in length, this includes the 4
character file extension identification at the end of every file, e.g. “.pdf”. If a file
contains more than 31 characters, then it will potentially stop the file from transferring
across, or will be unable to copy across to our server, meaning the file names will
need to be shortened, making the files supplied no longer final, and when native files
are supplied, we then run the risk of re-linking, (as all renamed files will cause a break
in the link identification), we may possibly link an incorrect image, if the names are
similar to others supplied.
• No special characters should be used in any file name, the only characters that
should be used in a file name should be numbers 0-9, letters a-z, hyphens ‘-’,
underscores ‘_’ and spaces (but no file name should have a double space, as this will
cause file to corrupt or not transfer via FTP). The only fullpoint/fullstop that should be
used in a file name is the one used to separate the file name and the file extension. A
file should never start with a space, hyphen, or underscore, this may cause it to corrupt.
• All file names should be relevant to the job title, if internal file naming is used, i.e
‘46589_txt.pdf’, then this will make it very difficult for operators to identify or relate to a
job, especially when the files are sent through via FTP, as there is more than a handful
of jobs going through this system at the same time. A good method to follow is as
follows The_Job_Title_TXT.pdf This method allows for quick identification of the
job by title and the component.
named. If a file is named in a manner that is not compatible with the majority of
systems that Pre-press departments use globally, then it can cause many issues which may very well endanger the delivery date, final correct production, final book legability!
If you follow the very basic instructions listed below, then you can avoid the above
problems;
• All file names must be no more than 31 characters in length, this includes the 4
character file extension identification at the end of every file, e.g. “.pdf”. If a file
contains more than 31 characters, then it will potentially stop the file from transferring
across, or will be unable to copy across to our server, meaning the file names will
need to be shortened, making the files supplied no longer final, and when native files
are supplied, we then run the risk of re-linking, (as all renamed files will cause a break
in the link identification), we may possibly link an incorrect image, if the names are
similar to others supplied.
• No special characters should be used in any file name, the only characters that
should be used in a file name should be numbers 0-9, letters a-z, hyphens ‘-’,
underscores ‘_’ and spaces (but no file name should have a double space, as this will
cause file to corrupt or not transfer via FTP). The only fullpoint/fullstop that should be
used in a file name is the one used to separate the file name and the file extension. A
file should never start with a space, hyphen, or underscore, this may cause it to corrupt.
• All file names should be relevant to the job title, if internal file naming is used, i.e
‘46589_txt.pdf’, then this will make it very difficult for operators to identify or relate to a
job, especially when the files are sent through via FTP, as there is more than a handful
of jobs going through this system at the same time. A good method to follow is as
follows The_Job_Title_TXT.pdf This method allows for quick identification of the
job by title and the component.
