|
HOW DESKTOP PUBLISHING TOOLS SERVE DIFFERENT MARKETS |
| No
single desktop publishing program is suitable to address
the broadly differing needs of every customer and/or every
project. Therefore, in order to decide which program will
fit each project and customer, many factors will need to
be considered. These factors may include the design and
publishing requirements of the job, the publisher's training,
the customer's budget, company resources, and the project
workflow. The following is a quick overview of the most
widely used tools for desktop publishing: |
| TRANSIT
TIP: PROCESSING ADOBE PAGEMAKER 6.5 FILES |
| Adobe
PageMaker 6.5 can be one of the most difficult file formats
to process in Transit. By using the following tips, you
can save yourself time and avoid potential problems when
working with PageMaker files:
1.
If you running PageMaker from a network or from a different
location other than the default installation path, opening
PageMaker first before doing the import in Transit can simplify
the import process. Also, when importing, if both the PageMaker
program and the PageMaker files are located on the local
hard drive, the files will process much quicker on import.
2.
A common error encountered when importing PageMaker files
is "Cannot Process Table Index". This error generally
occurs when some index entries are "booked" to
separate stories. To correct this error, unbook the file
in PageMaker, then reimport the file in Transit. If you
do not make this correction, the story will drop the index
on export.
3.
Another common error encountered is "Incorrect Story
Ignored". This error generally occurs when there is
an empty story in the PageMaker file that is not being imported
into Transit. This error rarely causes problems and can
usually be ignored.
4.
If you are importing PageMaker files and are pre-translating
into multiple languages, you can avoid re-importing the
original files by doing the following: First, import the
files under one target language, such as Brazilian Portuguese.
Next, copy the Transit source language files (generally
English files, being "ENG") and the "COD"
files to a separate directory. Then, "re-import"
the ENG files for pretranslation into the other target languages
by selecting only the "pretranslation" option
and deselecting the default segmentation and filter options.
5.
When exporting PageMaker files from Transit back to PageMaker,
you may receive an error similar to the following: "Cannot
open the file" after 2501 objects have been processed.
If this error occurs, do the following:
- ·
Open the original PageMaker file in PageMaker.
· Divide the file into two equal parts and save
these parts as two separate files.
· Re-import both pieces using the translated Transit
files as reference for pretranslation.
· Re-export the files from Transit back to PageMaker.
If
the files still do not export, divide the file into 4 equal
parts and repeat the steps above.
|
| DTP
TIP: ORGANIZING STYLES |
| PROBLEM:
When
importing Microsoft Word or other word processor files into
a page layout program such as QuarkXPress, the style menu
or palette is filled with extraneous styles from the imported
text. How can I avoid this?
SOLUTION:
Often,
when importing word processor text into a page layout program
such as QuarkXPress, Adobe PageMaker, or Adobe InDesign,
the text structure from the original file should be preserved,
while also employing your current document's styles. By
doing this, the document style listing will swell with new
and unnecessary styles, which may be difficult to differentiate
and remove.
To
avoid this problem, before importing the word processor
text, rename of all your document's "native" styles
with a rarely used leading character, such as a tilde (e.g.,
"~Body", "~Heading1"). After importing
the new text, all of the styles will be ordered alphabetically,
making the "non-native" styles easy to find and
remove.
You
can also use this naming method to create new styles based
on previous document styles. For example, if you have a
current style named "Body", and you want to create
a new style named "Body2" based on "Body",
first, copy the "Body" style and title it "~Body".
Next, base the new "Body2" style on "~Body".
That way, if the "Body" style is ever redefined
in the future, it will not affect the new "Body2"
style.
|
| MULTILING'S
EXPANSION |
| In
response to a steady growth occurring over the last couple
of years, MultiLing Corporation has moved to a new location.
MultiLing, working with leading architects and remodeling
experts, planned carefully to create an atmosphere with
the perfect mix of traditional craftsmanship and leading-edge
technology.
Moreover,
the new facilities will be able to more comfortably accommodate
the in-house staff, which has increased substantially to
meet a continuously growing demand. This integrated office
space provides individual privacy for all employees, but
also allows ample access to other team members. The layout
and design of the new offices will facilitate team integrity,
communication, and coordination, which are key factors that
support MultiLing's networked talent model.
This growth, resulting from a widely recognized effort to
provide incomparable customer support, has also led MultiLing
to increase its in-country translation capabilities. Over
the past six months, MultiLing has increased its global
resources by more than 20%.
The
new facilities of MultiLing Corporation are located at:
55
North University Ave.
Provo, UT 84601
Tel:
(801) 377-2000
Fax: (801) 377-7085
http://www.multiling.com
|
|
|
