FontIncluder 2 and FontIncluder Pro Server

Manual

Kiss goodbye the missing font problem

The days of seeing Courier font substitution in your very expensive ad are over. Use this app to make sure that what your clients first saw is what they get.

Let you handle those TrueType fonts with ease

In an ideal world you would not have to use TrueType fonts but we like to deal with reality. FontIncluder 2 will now embed TrueType fonts in addition to Type 1 and Type 3 fonts.

Give you peace of mind

FontInspektor:This great new utility allows you to inspect your font before you embed and output the job. You no longer risk having to foot the bill of running the job again because you didn't know someone had modified the font but not the fontname...

Smooth the ad delivery process

FontIncluder 2 is just as easy to use as version 1.0. Simply drag and drop your file before you supply your files to your service bureau.

Take the headache out of cross-platform file transfers

File integrity is guaranteed as the font information can travel with the file. Even if the PC font information was not originally embedded on the Windows machine it can still be done on a Mac <Eth> and vice versa.

Streamline and automate your workflow

Let FontIncluder 2 be called up by our award-winning XTension MadeToPrint XT which batch generates PostScript and perfectly cropped EPS files from within XPress.

Remain a lawful citizen

Our approach to supplying font information is accepted by the majority of font vendors like Adobe, Agfa and Linotype, so you can stay within the law.

FontIncluder is not a software extension but a stand-alone application. It does not integrate directly with other applications as would an XTension for QuarkXPress or an Xtra for Macromedia Freehand or an Plug-in for Adobe Illustrator. This said, it is not possible to achieve embedding of fonts into files from within such applications. You wonÕt be able to use FontIncluder to embed fonts from within CorelDraw or QuarkXPress.

There is an exception to this, as FontIncluder in conjunction with MadeToPrint XT may be set up to embed fonts directly into EPS or DCS files generated from within QuarkXPress using MadeToPrint XT.

It is also not possible to embed fonts into files other than PostScript files. Embedding of fonts does not work with native files from QuarkXPress, CorelDraw, Macromedia Freehand, Adobe Illustrator, Microsoft Word, Adobe FrameMaker, Adobe PageMaker, WordPerfect, Ami Pro, Microsoft Excel, ClarisWorks, Adobe Acrobat, etc.

It may be important for you to check whether a particular software can embed fonts into the PostScript or EPS output they generate. For example, current PostScript printer drivers under Macintosh and Windows offer options to embed all needed fonts during printing. As you can also print to file, this may solve your problem. Of course, FontIncluderÕs options are in many regards much more flexible than what the PostScript printer drivers offer.

While FontIncluder now handles virtually any fonts commonly used in the Western world it does not handle 2-byte fonts, like eg. Chinese, Korean or Japanese fonts.

TrueType fonts:

FontIncluder can now embed TrueType fonts into EPS-, DCS- and PostScript files.

Type 3 fonts:

FontIncluder can now embed Type 3 fonts into EPS-, DCS- and PostScript files. Note: Type 3 fonts are rarely seen anymore though some ÔolderÕ software packages may still make use of them.

DCS files:

DCS files are a special version of EPS files which contain a composite portion in addition to the separated pieces. For multi-file DCS files each portion resides in its own file. For single file (DCS 2.0 only) files all pieces are put into one file <Eth> such a DCS file looks like an ordinary EPS file but actually contains several Ôfiles in a fileÕ.

FontIncluder will embed any needed fonts into the respective pieces of DCS files <Eth> regardless if they are single file or multi-file version, DCS 1.0 or DCS 2.0.

Use fonts from same folder as PostScript file

Commonly the very fonts that need to be embedded into a PostScript file sit in the same folder (or its subfolders) where the PostScript file itself can be found. ThatÕs why we added the option to search for fonts in that folder (and its subfolders) first before possibly scanning other folders for fonts, like the SystemÕs font folder or primary and secondary font folder (and their subfolders).

Force embedding of fonts from same folder as PostScript files

This option is a very powerful <Eth> and thus a very dangerous one: Please use it carefully. Some of our customers have reported that once in a while they run into PostScript files that do not carry proper information about the fonts needed. So while they <Eth> as human beings <Eth> do know that for example Futura Bold is needed, this cannot be detected by FontIncluder if it is a file without proper information. Usually a user is stuck in such a situation. Nevertheless, now you can turn on ÔForce embedding of fonts found in the same folder (and its subfolders) as the PostScript file. Most of the time it would not even do any real harm to your file if you embedded extraneous fonts that are not actually needed, but obviously your file size increases accordingly, and the RIP will need a little bit longer digesting font information which isnÕt actually needed.

Embed PC fonts on a Mac

The font identification and embedding mechanism of FontIncluder has been extended so that on a Macintosh any PC font (Type 1, Type 3 or TrueType) can be embedded. This is extremely useful if a Mac prepress shop receives PostScript files from PC based customer using PC fonts. Until now you had to get yourself a PC to embed the fonts, before you could handle that file on a Mac.

In conjunction with the ÒUse fonts from same folder as PostScript fileÓ approach this is very handy whenever you take in files from outside.

Embed Mac fonts on a PC

In a similar way it is now possible to embed Mac fonts on the PC. But how do you put Mac fonts on a PC? As you may know Mac font files consist of two ÔforksÕ (another name for files...) <Eth> and one of the forks potentially will be lost if a file is copied onto a PC. There are two ways around this though:
- if a PC floppy disk (or PC formatted Syquest Cartridge or ZIP disk or...) is inserted into a Macintosh, and a Mac font file is copied onto that disk, you will see two files for every Mac file once you read that disk on a PC (cf. the folder Resource.frk).

New features in version 2

- Something similar holds true when a Windows NT file server is set up to act as

Apple File Server <Eth> here again the two forks of a Macintosh file are stored in a systematic way. FontIncluder knows how to find both parts of such a Macintosh file and will be able to read the needed font data for a Mac font on a PC.

FontInspektor

If you ever ran into a situation where you had two fonts with the same fontname, but the files were obviously not identical you probably wished youÕd had an ÔinspectorÕ tool which would tell you the differences between the two.

The FontInspektor option of FontIncluder 2 lists a wide range of information about a given font <Eth> be it a Type 1, Type 3 or TrueType font. You can then figure out which one you'd like to use for a given job.

System Requirements

Installing FontIncluder

Macintosh Copy the FontIncluder 2 application onto your hard disk drive.

Windows Copy the FontIncluder 2 application onto your hard disk drive.

Macintosh Double click or open FontIncluder to launch it.

Windows Double click or open FontIncluder to launch it.

Macintosh

FontIncluder will run on any Macintosh with System 7.1.2 or greater (currently the most recent Mac OS version we tested is Mac OS 8.1). You will need at least 4 MB free RAM and at least twice as much free hard disk space for temporary files as the size of the biggest PostScript file you want to process.

For best performance we recommend running FontIncluder 2 with 9 MB RAM. As a general rule of thumb (true for any application, not just FontIncluder) at least
30 % of your hard disk should be free. On a Mac the internal SCSI-bus is usually twice as fast as the external SCSI bus unless you installed high performance SCSI card for your external SCSI devices. Think twice if you want to process fonts over the network, as FontIncluder obviously does a lot of reading and writing of (potentially huge) files: This tends to be rather slow over a network as compared to running the same process locally on your workstation.

Windows

FontIncluder will run on any Windows machine with Windows 95, Windows 98 or Windows NT 4.0. You should have at least 32 MB RAM installed and at least twice as much free hard disk space for temporary files as the size of your biggest PostScript file you want to process.

As a general rule of thumb (true for any application, not just FontIncluder) at least 30 % of your hard disk should be free. A fast hard disk over a fast interface (there are slow and fast flavors of both IDE and SCSI) may significantly speed up the embedding process. Think twice if you want to process fonts over the network, as FontIncluder obviously does a lot reading and writing of (potentially huge) files: This tends to be rather slow over a network as compared to running the same process locally on your workstation.

Launching FontIncluder

Before processing any files please set up your FontIncluder preferences <Eth> go to menu Edit and select Preferences..: the FontIncluder Preferences dialog box will be shown. The settings in the Preferences dialog box define how Font Includer will achieve your goals:

Embed all fonts or not?

You don't have to embed every font in your PostScript, EPS or DCS files. Depending on your needs you may prefer to include all fonts except the Standard 4 (Helvetica, Times, Symbol, Courier) or the Standard 35 (in addition to these: Avantgarde, Helvetica Narrow, New Century Schoolbook, Zapf Chancery Medium and Dingbats, and Palatino).

You could also decide to include all fonts except those listed as available fonts in a PPD (PostScript Printer Description). In this case, as well as selecting the respective radio button you will also have to choose the respective PPD file for your output device. Usually on a Macintosh these PPD files can be found in the folder Printer descriptions inside the Extensions folder inside the System folder.

In some instances you may have your own list of fonts which you never want to be embedded. In such a case you can create or modify an existing PPD file so that it contains a list of fonts regarded as not needed (because they are resident on the output device).

Keep original file?

The old PostScript (or EPS or DCS) file can be replaced by the new one, or you can decide to always create a new file, optionally with a pre-defined suffix.

Where to look for fonts

You have to tell Font Includer where to look for PostScript Type 1 or Type 3 or TrueType fonts.

In many instances it will be handy to first of all search in the same folder as the PostScript file currently being processed.

Next, it may make sense to look in the system folder.

As searching for font files in lots of folders and subfolders can be time-consuming it is wise to split the fonts you have into two folders:

A primary folder (and its subfolders) will contain your everyday fonts, while the secondary folder contains the rest. Of course in any case will FontIncluder 2 search through a defined folder and through all its subfolders of any nesting level.

Any of these four options can be turned on or off independently of each other. Nevertheless, it is not possible to change the order in which fonts are being searched.

Important note

FontIncluder does not know anything about font activation by Adobe Type Manager, Suitcase or Font Reserve. While a font may have been activated by such a tool, it will only be found by FontIncluder if it resides inside one of the chosen search paths.

Processing a file

In order to process a given file, you simply use FontIncluderÕs ÒOpenÓ command (either doing Command-O on the Mac or Control-O on Windows or selecting the menu entry ÒOpen...Ó under the ÒFileÓ menu) to select the file to be processed .

Right afterwards FontIncluder 2 will ask you where to save the new file to be created that will contain the embedded fonts. The suggested name will already carry a suffix according to your settings in the FontIncluder Preferences.

If you are not able to locate the font or simply do not have it, FontIncluder will continue its task anyway and will then ask you if you wish to save a file with only some of the fonts embedded, or if you prefer to skip the process altogether. You should be aware that if a font is missing and it is not loaded on the target device you will probably see Courier for that font.

You also have the option to run FontIncluder 2 again with that partially font- complete file and embed the till missing font(s) later on.

Once FontIncluder has found the required fonts and written the new font-complete file, it will tell you which fonts had been included.

In case at least one of the fonts could not be located, you will see dialog box telling you about the fonts that had not been included.

EPS files

As with version 1.0 of FontIncluder the new FontIncluder 2 of course still handles any well behaved EPS file. Since FontIncluder 1.0 was released more than two years ago, we have seen very few EPS files FontIncluder was unable to digest. We have slightly modified FontIncluder 1.0 during those two years to be able to handle certain strange flavors of EPS.

FontIncluder 2 uses the same EPS parsing algorithms as FontIncluder 1.0 <Eth> so we expect that you will hardly ever run into a EPS file that cannot be digested by FontIncluder 2.

If nevertheless you are ever confronted by such a situation, please make sure first, that the EPS file is well behaved, i.e. please try to output it without the fonts being embedded. If it causes PostScript errors or other problems, you may want to make sure that the EPS file can be used at all. If you then have reason to assume that the EPS file is well behaved but still is not handled properly by FontIncluder 2, please send it to us, and we will immediately try to analyse and <Eth> if possible <Eth> fix the problem.

DCS files

DCS files are a rather specific flavor of EPS files, invented by Quark several years ago. It addresses separation issues, and actually, any DCS file comprises several EPS files. For a single file DCS 2.0-file, these various EPS files have been put inside one file, and a digesting application like QuarkXPress will have to know at runtime, which of the ÔpiecesÕ to pull out when. For a multi file DCS-file (version 1.0 or 2.0), the pieces are kept as separate files, and a certain naming convention makes sure a digesting application like QuarkXPress knows which file to pick when.

In addition to the single file and multi file issues there is one other aspect with DCS files you may want to know about:
- DCS files can for example be exported from Photoshop. Such DCS files are image only files that will never require font embedding
- Some copy dot scanners use the DCS format to put the various scanned plates for a given page or artwork as 1-bit images into a (DCS-) EPS file. Again, as these files are image only, there is no need to run them through FontIncluder.
- Applications like QuarkXPress cannot only export pages as EPS files but also as DCS files. These DCS files may well need font embedding.

Note: It will not cause any problems if you process image only DCS files with FontIncluder, as FontIncluder will find there are no fonts needed for such a file.

PostScript print files

While today's PostScript printer drivers on Mac and Windows machines offer an easy way to embed fonts while printing to a PostScript file you may run into situations where you have to take in files from outside that do not have the fonts embedded. On condition that the party submitting that file provides you with the fonts you can use FontIncluder to embed those fonts into that PostScript print file.

Non-PostScript files

FontIncluder will not process files other than PostScript files, EPS files or DCS files. It is not possible to process files such as XPress files, Word files, CorelDraw files, WordPerfect files, ClarisWorks files, etc. You have to create PostScript, EPS or DCS files from such files and then embed fonts into these PostScript/EPS/DCS files. Nor can FontIncluder embed fonts into PDF files.

Font locations

Fonts can be searched for in four locations: á The same folder containing the PostScript file currently being processed. As files that are taken in from outside often come in a project folder that also contains some other files like to original application file from which the EPS file was generated, as well as any imported images, logos, etc. and of course <Eth> the fonts.

If the respective option has been activated in FontIncluder's preferences FontIncluder will first of all scan this folder and all its subfolders (even nested several levels deep). á The second option where FontIncluder looks for fonts is the System's font folder.

These fonts are those currently active in the system, though FontIncluder will not regard fonts activated by Adobe Type Manager, Suitcase, FontReserve or other similar tools unless the fonts reside inside the SystemÕs font folder. á The third and fourth option <Eth> named primary and secondary font folder <Eth> can be set up to point to any folder or volume on the local workstation or the network. For our own stress testing we inserted a CD-ROM with hundreds of Megabytes of fonts into the CD-ROM drive of the test workstations and pointed the secondary font folders to this CD-ROM.

You should store often needed fonts in the primary font folder (and its subfolders), sitting preferably on your workstationÕs hard disk drive. Seldom used fonts may be burnt onto a CD-ROM which can then be inserted into the CD-ROM drive and be pointed to as the secondary font folder. Such a setup will give you the best trade-off between not wasting too much disk space but nevertheless having all fonts online.

Embedding PC fonts on a Macintosh

FontIncluder now also handles PC fonts on a Mac <Eth> just copy them to either the same folder as the file to be processed or to the primary or secondary font folders. While they probably will not cause any trouble if copied to the SystemÕs font folder they wonÕt do you any good either, and it is always preferable to keep the system as clean as possible.

Embedding Macintosh fonts on a PC

You can also embed Mac fonts on a PC though you have to make sure they get there without being corrupted:
á Either copy the Mac fonts into a folder on a PC formatted removable disk (floppy, Syquest, ZIP etc.) and then copy that folder (sic!) with all the stuff in it onto your PC. Point the primary or secondary font folder in the FontIncluder preferences to this folder. Or copy that folder into the same folder where the PostScript files reside that are to be processed.

á Set up a Windows NT server to offer Apple file sharing, mount that NT server volume on Macintosh and copy the font files into a folder on that file server volume. Then mount that same volume on your Windows workstation. Point the primary or secondary font folder in the FontIncluder preferences to this folder.

Force embedding of certain fonts

This option has be used carefully: It allows you to embed any font <Eth> needed or not by the PostScript file <Eth> into the PostScript file. While usually not at all necessary, you may once in a while run into a file, that needs certain fonts which is not clear when reading the so called DSC comments (DSC: Document Structuring Conventions, part of the Adobe's PostScript specification). In such a case FontIncluder won't be able to know which fonts are needed for that PostScript file. In case you do know, throw the required fonts into the same folder as the PostScript file, enable the check box Force embedding of fonts in the FontIncluder preferences and process the file:

Special font handling options

FontIncluder will embed all PostScript Type 1, Type 3 and TrueType fonts found in that folder and its subfolders into the PostScript file.

You should use this option extremely carefully, and among other things make sure you do not put the Type 1 and TrueType version of a given font into the folder at the same time, because FontIncluder will pick these in random order, and it will not be predictable which of the two will actually be used by a RIP to image the PostScript file. If the wrong one happens to be used type may look rather ugly.

FontInspektor offers an easy way to learn more about a given font. Choose the menu item Display Font Info... under the FontInspektor menu, and FontIncluder will ask you to select the font about which you would like to learn more.

A dialog box will then open with a list of all the information that could be found in the font file by FontIncluder. Among other things, you may easily figure out if you have got two versions of the same font from the same foundry, and will be able to tell which is the more recent one.

Looking at two fonts with the same names you will also be able to tell the original version from a bastardized one (that had been created by somebody using a font creation and modification tool who did not follow the rules of good font naming, as otherwise heÕd have given a new name to the modified version of the font).

Note: For TrueType fonts you may see more than one font listed in the FontInspektor dialog box <Eth> this is absolutely no problem, though you will have to scroll the list in the FontInspektor dialog box to see the information for the second and following fonts. For Type 1 and Type 3 fonts there is always only one font inside a font file.

Macintosh: AppleScript

FontIncluder 2 is scriptable. When being run by an AppleScript it will always use the preferences as currently having been set up manually. The following AppleScript commands open up ways to automate the functioning of FontIncluder:

Syntax:

tell application FontIncluder open file reference end tell

Example: tell application "Font Includer" open file "Macintosh HD:PostScript.PS" end tell

This example opens the file PostScript.PS on the hard disk ÒMacintosh HDÓ and embeds the needed fonts (according to the currently set up preferences). Any further processing of the files can be done through common AppleScript commands or Scriptable Finder commands.

A self-running folder watch function would have to check for the presence of a file in a pre-defined folder. Such a file can then be opened and processed by FontIncluder and then be moved to some other folder. FontIncluder returns an error value and a error message if it cannot find needed font files. It would be the responsibility of your AppleScript to handle such an error and move the PostScript file to a problem folder.

Windows: Command line batch processing

In a similar way as with an AppleScript it is possible to run a simple batch under Windows as follows containing the following call:

Example: fontincluder2.exe c:\files\PostScriptFile.ps

This line will launch FontIncluder 2 and ask it to process the indicated PostScript file Òc:\files\PostScriptFile.psÓ. Currently no error code is returned by FontIncluder2. If the preferences are set up in a way that a new file is to be created you will know there is a problem if no new file is created.

Automating FontIncluder

Although it is possible to optimize your workflow with AppleScripts on Macintosh or with batch processing on Windows, this does not realize the full potential of an automated workflow. callas software has developed FontIncluder Pro Server for high-volume workflows.

FontIncluder Pro Server offers you three different configuration settings for watched folders/hot-folders. These have been tested to ensure smooth interaction and optimized conditions for your workflow.

For Mac users only: FontIncluder Pro Server can be monitored by Rebound!, a utility from Sophisticated Circuits (for more information see Sophisticated Circuits, www.sophisticated.com) which checks for any system problems or crashes. If it detects a problem it will restart the Mac and relaunches FontIncluder Pro Server.

Last but not least, it only takes a few minutes to configure the settings for FontIncluder Pro Server whereas it requires experience, time and testing to write AppleScripts or batch processes.

FontIncluder Pro Server is the ideal tool for removing the whole font embedding process from the users so they can get on with the real work.

FontIncluder Pro Server runs on any Macintosh with OS Version 7.1.2 up to Mac OS Version 8.1. You need 6 MB RAM minimum, 10 MB RAM is optimum.

For continuous operation, FontIncluder Pro Server should be installed on a separate computer since some of the tasks do not only run in background mode. This will be a handicap if you want to use this computer for other operations at the same time.

Copy the FontIncluder Pro Server application onto your hard disk drive.

Double click or open FontIncluder to launch it.

The server version of FontIncluder has basically the same structure as the standard version, though with an additional menu item to activate the server.

When opening this dialog the first time, no jobs will be listed. Once you have defined a job, it will be added to the list.

In order to create a new job for FontIncluder, click the button ãNewÒ. In the dialog box that follows, you enter a name for the job, choose the watched folder (IN) as well as OUT, ERROR and DONE.

FontIncluder embeds fonts in the original files by default and moves the files afterwards in the OUT or ERROR folder. If the option ãKeep OriginalÒ is activated, a copy of your original file as put in the IN folder will be moved in the specified DONE folder.

As a last step you choose the process mode that you want to use as basis for the files and folders in your watched folder (IN) to be processed. The functionality of the three different modes FontIncluder Pro Server offers you is based on requirements identified at our clients workflows. FontIncluder Pro Server offers you three options:

Process mode FileÒ

If the process mode File is chosen, FontIncluder Pro Server processes all PostScript, EPS and DCS files in the IN folder. Other than these target file formats all other files will be ignored <Eth> even if a folder contains a PostScript file.

Choosing the File mode makes sense if you want to process files independently of each other. You may either put the original PostScript file or an Alias in your IN folder. If you put an Alias in the IN folder, your original file remains in its orgin location, only the Alias will be moved to the OUT folder after the fonts have been embedded.

For example, the production of a magazine requires an undefined number of different fonts. They are all on one central file-server. Working with FontIncluder Pro Server it does not matter how many people are involved in production or how many fonts they use, once a page is put together, it can be moved as EPS file to the IN folder. FontIncluder will embed all the fonts needed. This leaves your typesetters free from repetitive tasks.

Process mode Project Folder

If the process mode Project-Folder is chosen, FontIncluder Pro Server only takes FOLDERS within the IN folder into consideration. FontIncluder Pro Server ignores single files as well as folders that do not contain PostScript, EPS or DCS files. They remain in the IN folder.

FontIncluder searches for PostScript files in the project folders inside the IN folder recursively, i.e. it does not matter where exactly the PostScript file in the project folder is positioned. Please note, that only one file from within a project folder will be processed by FontInlcuder Pro Server, namely the one FontIncluder finds first or the file with the highest priority (for Mac users only, setting priorities by labels).

The only exception are DCS files since they are treated as one unit and therefore processed as complete file. (Please see also Additional information for running FontIncluder Pro Server.) As soon as all fonts have been embedded, FontIncluder Pro Server moves the whole folder with all files to the OUT folder.

You also have the opportunity to put only an Alias of your project-folder in the IN folder. After having processed the folder, FontIncluder Pro Server moves the Alias into the OUT folder <Eth> your original folder remains at its orgin position.

Example: An advertising agency files ads by client in project folders. The project folder contains the original file, the EPS file and all fonts needed as well as other files, e.g. correspondence or media data as text files. In this case it is useful to configure the preferences so that FontIncluder Pro Server searches for fonts in the folder where the PostScript file is first. The whole project folder is moved to the IN folder FontIncluder Pro Server identifies the PostScript file and ignores all the other files in the folder. FontIncluder searches for the fonts in the project folder and embeds them. After all fonts have been embedded, the whole project folder is moved to the OUT folder.

Process mode Hierarchy

The process mode Hierachy offers you the option to process single PostScript, EPS or DCS files within a fixed folder structure. The whole folder structure that is put in the IN folder will be replicated to the OUT folder after the fonts have been embedded. Thus, you find the processed file on exactly the same position within the folder's hierarchy as it was before the embedding process started <Eth> you alway keep track where your files are and where they belong.

Example: A publisher produces brochures for three major clients. Each client has a number of different departments, each of them providing the publisher with jobs. One client has seven departments, onother has three, and the third one has nine departments. This adds up to a total number of 19 departments and three clients. In order to keep the overview of what departments and clients belong together, you can establish a folder hierarchy that mirrors the structure of your clients, i.e. G1 (1 2 3 4 5 6 7) G2 (1 2 3) G3 (1 2 3 4 5 6 7 8 9). This structure is put in FontIncluder Pro Server's IN folder.

If now one of the 19 departments of one of the 3 clients sends a job/file, you put the PostScript file in the respective subfolder. In the OUT folder, the processed file occuers at the same position within the hierarchy. This ensures quick and definite classification of job, client and department.

Additional information for running FontIncluder Pro Server

- You may accelerate the font embedding process if you run two or even more copies of FontIncluder Pro Server in parallel and let them watch for the same folders. This speeds up the whole procedure especially if you have a large number of files where you want to have fonts embedded.

- Within the processing modes File and Hierarchy, the parts of a multiple DCS files are considered as single files and, therefore, are processed separately. Within the processing mode Project Folder, FontIncluder Pro Server treats a DCS file as a single unit. Running several copies of FontIncluder Pro Server in combination with the the processing mode File or Hierarchy allows you to accelerate the file processing.

- You do not lose any of your original files, even if you have files with identical names. They will neither be deleted nor overwritten when moved in the OUT folder since FontIncluder Pro Server saves these files while adding a suffix from 000 to 999. In combination with multiple DCS files you have to be extremely careful, especially when running several FontIncluder Pro Server: Parallel processing of DCS files with identical names means that a classification on basis of the suffix is not possible.

- Use only one processing mode (File, Project Folder or Hierarchy) for supervision of a single IN folder. The combination of two different processing modes <Eth> i.e. two different logical concepts <Eth> leads to undesirable interactions. This is ecspecially true for the combination if you run the processing modes Project Folder and Hierarchy on the same IN folder.

- Generally speaking, you can always put an Alias instead of the actual file or folder into the IN folder. Nevertheless, we advise you not to work with the Hierarchy mode when using (convoluted) Aliases, because FontIncluder Pro Server moves the original file in the replicated folder structure to the OUT folder. This can lead to a confusing folder structure in the OUT folder.

Launching FontIncluder Pro Server

As soon as you click the Start button in the dialog box (see screenshot below),

FontIncluder Pro Server starts to check for files in your IN folder and processes them with your pre-defined processing modes and settings.

Currently <Eth> as of August 1998 <Eth> there is no homogeneous legal situation in terms of forwarding font files together with documents to a person or company that does not own a license for these fonts. It is pretty obvious though that in legal terms it is not acceptable to forward fonts as separate files.

Nevertheless, some of the major font vendors have agreed that it is acceptable to forward fonts to a person if and only if they are embedded in a document <Eth> e.g. a PostScript file <Eth> and if they can only be used for viewing or printing the file (i.e. not for editing the file). As an example we cite a piece from Adobe's type licensing policy statement:

What is Adobe's type licensing policy?

[...]

AdobeÕs licensing policy on transporting typeface software with print jobs to service bureaus is unchanged. Customers are allowed to give their typeface files to a service bureau along with a print job IF AND ONLY IF the service bureau already owns a valid license for the typeface. The reason for allowing this to happen is to ensure that the customerÕs revision of the typeface software is the one used to image the print job. Adobe does revise its typefaces periodically. Customers are not allowed to give typefaces to service bureaus who do not already own a valid license for the typefaces.

[...]

When is it legal to embed typefaces into documents?

Adobe permits embedding certain typefaces into documents for the purposes of viewing and printing only. Documents with embedded typefaces may not be edited unless those embedded typefaces are licensed to and installed on the computer doing the editing. The reason for this is that editing the file adds value to the file. For this, the customer is obtaining value from the typefaces and is therefore required to have a valid license for the typeface.

In general, embedding certain typefaces is legal if the typefaces are embedded but cannot be used to edit documents or accessed as typefaces for use in other documents. Printing to a PostScript-language file and embedding typefaces into PDF files are legal ways to embed typefaces. Sending typefaces on floppies along with print jobs is not legal, since they can be installed and used as typefaces with other documents.

Which typefaces may be embedded if the above rules are followed?

Typefaces in the Adobe Type Library that were created by Adobe, Linotype, ITC, Monotype, Agfa, and Fundicion Tipografica Neufville may be embedded in the file with a document for viewing and printing the document. Adobe is negotiating with all its other type foundries to obtain this permission. Until the contracts with the other type vendors are final, users must contact the company which licensed them their typefaces to determine if embedding is legal.

[...]

IMPORTANT: It is up to the user to check if her or his license allows for embedding typefaces into a PostScript file.

Further informations

A word about font licensing issues...

Please read this License and limited warranty agreement carefully, before breaking the diskette seal. By breaking the diskette seal or using the software, you agree to the terms of this License. If you do not agree to the terms of this License, do not break the diskette seal.

Definitions of terms used in this License:

The following definitions are valid for this License: Software refers to the program(s) on the enclosed diskette(s); use consists of either loading the software into the computer memory or running it in a CPU; install means, to copy the software to a hard disk drive or similar storage device.

1. License

The producer retains title to the software -- the customer does not receive title to the software. The customer is granted a non-exclusive License to use the software subject to the restrictions and terms set forth in this License Agreement.

The software may be installed and used on as many computer systems as is agreed upon in the separate order/licensing contract. The number of computer systems defaults to one computer system. The software may be copied for backup and archival storage under the condition, that the copy contains all files that came with the original software, and that these backup or archive copies are not used at any time and must remain in the possession and control of the customer.

The software and the enclosed documentation may not be copied, sold, hired out, lent or leased. The customer may not alter, translate, disassemble or decompile the software or the enclosed documentation. The customer may not transfer the software without the prior written approval of callas software gmbh, Berlin.

2. Customer communication of License agreement

The customer agrees to to communicate the restrictions contained in this License agreement to all persons under his or her employment, direction, or control.

3. Unauthorized use and compliance

The customer will use all reasonable efforts to see that employees, agents, assigns, or other persons under the direction or control of the customer abide by the terms and conditions of this License agreement. The customer agrees to notify callas software gmbh, Berlin, in writing of unauthorized use.

4. Termination

Each violation to the terms of this License will terminate this License automatically and immediately. Upon termination the customer must destroy the software, the accompanying documentation and all copies thereof.

5. General provisions and limited warranty

callas software gmbh, Berlin, warrants that for ninety (90) days after purchase of the software by the customer (or for the minimum period required by the local law where the product is sold to the customer, if longer) (hereinafter, Òwarranty periodÓ) that the software shall reasonably conform to the standards defined in the accompanying documentation (i.e. manuals and/or computer aided instructions). callas software gmbh, Berlin, do not warrant that the software will operate uninterrupted or error- free. The sole and exclusive remedy for a failure of the software to perform in accordance with the accompanying documentation is for the customer to return the software to callas software gmbh, Berlin, and to notify callas software gmbh, Berlin, in writing of the nonperformance within the warranty period. callas software gmbhÕs, Berlin, sole obligation shall be to provide the customer, within a reasonable time after receiving notification of nonperformance, with a performing copy of the software, or in the event of a performing copy being unavailable for whatever reason to refund the purchase price to the customer. callas software gmbh, Berlin, does not guarantee, that defects in the software will and may be corrected.

6. Disclaimer of other warranties

The limited warranty set forth in paragraph five is in lieu of any other warranties. The implied warranty of merchantability is limited. callas software gmbh, Berlin, disclaim any implied warranty, including, but not limited to, any implied fitness for a particular purpose or merchantability. callas software gmbh, Berlin, disclaims all warranties including, but not limited to, warranties provided by distributors, dealers and retailers of the software.

7. Other warranty rights

Some areas or countries do not allow limitations on implied warranties, so the above limitation may not apply to particular customers.

8. Software updates

At callas software gmbh's, Berlin, sole discretion callas software gmbh, Berlin, may provide the customer with updates to the software. callas software gmbh, Berlin, retains the right to provide the updates for a fee. The customer may refuse to accept the updates. The terms and condition of this agreement apply to any and all updates.

9. Customer responsibility for selection of the software

The customer is solely responsible for selection of the software to achieve the customer's intended results or for particular applications.

10. Disclaimer

In no event shall callas software gmbh, Berlin, be liable to a customer for any special, indirect, incidental, or consequential damages in any way relating to the use or arising out of the use of the software or accompanying documentation however caused and on any theory of liability. callas software gmbh's, Berlin, liability shall in no event exceed the total amount of the purchase/License fee actually paid by the customer for the use of the software. These limitations will apply even if callas software gmbh, Berlin, or an authorized distributor or dealer has been advised of such possible damages. The customer acknowledges that the License fee reflects this allocation of risk.

Some areas or countries do not allow the exclusion or limitation of incidental or consequential damages, so the limitation or exclusion included in this License agreement may not apply o particular customers.

11. Severability

If any provision of this License and limited warranty agreement is declared by a court of competent jurisdiction to be invalid for any reason, such invalidity shall not affect the remaining provisions.

12. Governing law and jurisdiction

This License agreement shall be governed by the laws of Germany. The courts of competent jurisdiction at Berlin, Germany, shall have the exclusive jurisdiction over any dispute arising out of o in connection with this License agreement, without prejudice to the right of callas software gmbh, Berlin, to initiate legal proceedings in the courts of the country where customer is established or where customer has a center of business activities. Any costs which callas software gmbh, Berlin, has to incur in or out of court, should callas software gmbh, Berlin, become involved in legal proceedings or disputes with the customer, shall be for the customer's account.

Idea: Olaf Drümmer

Implementation: Stefan Haack, Heiko Bock and Andreas Dippe Quality assurance: Heiko Bock

Manual: Olaf Drümmer, Karin Schuller and Andreas Arcularius Special thanks to: Peter Miles, Paul Antoine, ZMG and Print Online Page 2

© 1990-99 by callas software gmbh