The following links will take you to various resource sites throughout the web. We've categorized them into design resources, webmaster resources, software resources and miscellaneous resources for your convenience. If you know of any sites that you feel should be on this page, please let us know by posting a suggestion to the Dispatch Technical Forum.
Because most FTP clients will not automatically recognize the QuarkXPress xtg file format (.xtg) as ASCII text files, they must be configured to do so. Incorrect configuration will result in the files being transferred as binary, which cannot be read by Dispatch. Instructions are provided here for proper configuration of Fetch for the Macintosh.
Because most FTP clients will not automatically recognize the QuarkXPress xtg file format (.xtg) as ASCII text files, they must be configured to do so. Incorrect configuration will result in the files being transferred as binary, which cannot be read by Dispatch. Instructions are provided here for proper configuration of WS_FTP for Windows.
Dispatch manages certain directories (folders) within your web site, specifically the dated issue folders and the "current" folder. Each dated folder contains a unique issue and all of its files (stories and images). The "current" folder always contains a copy of the latest issue in your publication. A typical directory tree created by Dispatch looks like this:
/2000-02-01/ All of the dated folders have the format of yyyy-mm-dd, which is year-month-date. "2000-02-01" contains all of the files for the issue of February 1, 2000. "2000-02-08" contains the files for the issue of February 8, 2000, and so on. The "current" folder always contains a copy of the latest issue in your publication. In this case, the "current" folder contains a copy of the "2000-03-01" folder, which is the latest issue in this example. This is a common directory structure for online publications and hopefully one you are already familiar with.
Dispatch manages all of the folders we have discussed so far. Beyond that, you are free to create whatever additional folders you would like. For example, you will probably create a folder named "images" that will house all of the common images throughout your site, and maybe another for includes or style sheets. Something like this:
/2000-02-01/
Dispatch uses a file-naming convention to help import stories and images into the database. This naming convention is based upon the column each story or image belongs to.
Typical naming conventions look like this: music_feature1.xtg The basic format is: column_base_nameN.xtg Note: You may name files any way you want. If Dispatch doesn't recognize a file name, you will be prompted to identify it during the importing phase.
Images also use a naming convention which is defined as follows:
column_base_nameN-N.gif or column_base_nameN-N.jpg Using the file set from above, notice how the images are named to lock to the correct files (stories):
music_feature1.xtg This format allows for perfect file locking. Dispatch will prompt you if an image is named incorrectly and ask what column or story to lock it to.
Dispatch file import includes a feature which allows multiple QuarkXPress Xtg files to be merged together to create one master document for a story. This is useful in circumstances where elements of a story are in separate, unlinked text boxes. The following guideline is for naming extended Xtg files prior to uploading to the Dispatch server:
The secondary name slot -- the part after the plus sign (+) -- can be comprised of any word characters (0-9, A-Z, a-z and underscore), but there must be a number to end the file name. Files with extended names will be appended to the end of the original story in alphanumeric order. The combination of files happens during the import into Dispatch, so you will not see the extra files listed on the "Files Found" page. You will, however, see the original file name, example1.xtg, for instance.
Extended file naming should only be used in cases where elements of a story -- such as the headline, byline, subhead, or description -- are in text boxes that are not linked to the story body itself within QuarkXPress (not really recommended in desktop publishing). It can also be used if the jumped portion of a story has been laid out using separate, unlinked text boxes. Uploading these elements with extended file names will allow the information to be properly converted to HTML (especially important with special characters). It also gets all data in one place, which is, in most cases, easier to manage. NOTE: Simply using extended file names will not fill your Dispatch database. Quark styles must still be used for automatic importing into Dispatch data fields. Information that is appended to the original story without proper styles will appear as part of the story and will have to be cut from the story field and pasted into the correct data fields. Unless Quark styles are being used consistently throughout your publication, it is not advisable to append additional files in this manner. CAUTION: Cutting and pasting information from another text source into the Dispatch interface may result in the inclusion of some characters which are not fully supported by HTML. Such characters may include, but are not limited to, "smart" quotes, accented and other foreign characters, and copyright and trademark symbols.
Step by Step FreeBSD InstallationThe following directions outline how to prep a Dispatch server for installation of the full OS--FreeBSD--and Dispatch Automated Publishing Solutions software. Once the following steps are completed, DesertNet will access the machine and take over the installation. This installation requires that the you have an IP address to use for this machine, and have the computer connected to the Internet. This install will download needed components--totaling about 30 MB--via ftp from a remote server, so you'll want to have high bandwidth available. If you have questions at any point in this process, please email us at support@desert.net.
Your first step will entail procuring FreeBSD installation disks. The following links will initiate downloads of the files you need to create these disks.
Once downloaded, put the three files in a directory labeled "FreeBSD." [BTW, this process should be taking place on a Windows or DOS based Intel machine of some sort.] You'll need two formated 3.5" 1.44MB floppy disks. Access a DOS prompt either within Windows, by exiting Windows to the prompt, or by working from your standard command line if you are a DOS user. From the DOS command line, change directories to the location you've stored the three downloaded files in. Label one of the disks "Kernel" and place the floppy in the "a" drive (assuming the 3.5" drive is your "a" drive--alter instructions accordingly if it has a different drive letter).
Enter the following command: fdimage kern.flp a: When that disk is done and you are again at the DOS command line, label the second disk "MFS Root" and place the floppy in the drive. Enter this command: fdimage mfsroot.flp a: This is a screenshot example of the above two steps:
![]() Congratulations. You now have the disks to boot the machine into a FreeBSD install.
Boot from the Kernel floppy by placing the first disk you made--labeled "Kernel"--into the "a" drive of the computer and starting/restarting the machine. By the way, you may want to make sure the computer's bios is setup to check the "a" drive for bootable media and set that drive first in the search chain of bootable devices. Insert the MFS Root floppy when the install routine asks for it. You'll want to bypass the "Kernel Configuration Menu" by hitting enter.
Move the cursor down to Express and use the space bar to activate it.
![]()
We're going to reformat the disk using FDISK. The first screen shows a typical Windows disk partition. You want to delete all the partitions and create new ones for FreeBSD.
![]()
Move the cursor down to the "fat" partition and press "D" until there is a single unused "partition" on the disk as shown in this screen.
![]()
Hit "A" to use the entire disk and answer the resulting dialog box in the affirmative (the default).
![]()
Now the screen should look something like this. Hit "Q" to quit FDISK and continue with the installation.
![]()
You want the machine to boot directly into FreeBSD; move the cursor down to the line for the standard MBR and the space bar to select it. Hit enter to continue.
![]()
Now you need to define subsections within the FreeBSD partition using the FreeBSD Disklabel Editor. Hit "A" to use the default slice settings for your disk and memory configuration.
![]()
The defaults it gives you should be fine. Hit "Q" to quit out of the Disklabel editor and continue with the installation.
![]()
You will be installing only a small portion of FreeBSD at this time. Scroll down to the "Minimal" distribution and use the space bar to put an X next to it. Then hit enter to continue to the next screen.
![]()
Scroll down to "Install from an FTP server" and hit the space bar.
![]()
In addition to the primary site there are six US mirrors near the bottom of the list. You can use traceroute or ping from another computer to determine which one will be the fastest.
![]()
Use the arrow keys and space bar to choose the one which looks most like an ethernet adapter. If two or more ethernet cards appear in the list, you will have to figure out which one is plugged in.
![]()
You want to answer "No" here. DHCP is really neat, but you probably don't have it set up to always use a static IP address for this computer.
![]()
Put the relevant values into the fields. Use tab to cycle through the fields and buttons. The host and domain names are not as important as the other values. You won't need to give any extra options for ifconfig.
![]()
The download is about 30 megabytes. If it goes too slowly, you can abort the process by any means necessary and use a faster FTP server the next time around.
![]()
Hurray, the download is finished and there are only two more things left to do! Hit enter to continue.
![]()
Move the cursor down to the Root Password line and use the space bar to choose the menu item.
![]()
An ideal password is a random collection of letters, numbers and punctuation. Be sure to remember it! The password won't appear when you type it. Repeat this process if you mistype the password the second time.
![]()
Next you need to make a user account for the dispatch user. Scroll down and select the menu item with the space bar.
![]()
![]()
Fill in the values as needed. It's important to make the dispatch user a member of the "wheel" group, and to set the home directory to "/home/dispatch".
![]()
Congratulations! You are done! Use the "Exit" menu item and then the "Exit Install" button to exit completely out of the installation program. The system will reboot and should boot cleanly into FreeBSD, with the process ending at a FreeBSD login prompt. After you restart the machine, contact Dispatch Support (support@desert.net) and let them know the machine is setup and ready for us to install Dispatch. We will also need to know the root password and dispatch user's password so we can access the machine and finish the installation.
One of the import formats Dispatch supports is the QuarkXPress tag format. XPress tags contain stylesheet and formatting information that Dispatch can use to pre-fill out database fields, saving you time. Due to the way QuarkXPress handles text boxes, stories need to be individually extracted as XPress tags. This is the only way to separate stories from ads or miscellaneous text boxes within your QuarkXPress documents.
Once the save text dialog appears (see above right), give the file a distinctive name with the extension ".xtg" (ie: film.xtg, film2.xtg). Change the format to "XPress Tags" (you'll only have to do this on the first story you save; Quark should remember this setting). Press save to save the story.
|
| Home: Support: Print Friendly Version (appendices) | Questions? Comments? Post them to the Dispatch Technical Forum. |