It is preferable to receive scripts as a computer files as M.S. Word or Excel. @I.S. also works with prompts within code, so just let us know what kind of binary file you will be sending and what the prompt demarcation marks are. Note that Excel does not have spellchecks in many foreign languages, which is less important for audio scripts, but very important for anything appearing in print.

File names for each prompt need to be clear, and there may be a surcharge for re-typing and reverifying prompt file names. Some files and file formats cannot be used by foreign operating systems and software. Be sure to check with @I.S. if your company uses any software other than M.S. Word or Excel.

Large files are a problem. If the script is extremely large, heavy and laden with notes and miscellaneous other information not related to translation, those files may corrupt, crash, or cause significant extra work, especially with foreign operating systems. If the file is oversized, has too many columns or too much text, and you want to receive a bilingual file, clean out most information not needed by the translator, or divide the file into 2 or 3 parts. Or, conversely, you may wish to accept a file with only the foreign language and the prompt numbers, and no English. IMPORTANT: Many languages cannot view multiple tabs in Excel files. Only 1 tab will arrive or be viewable on many foreign operating systems. For this reason, documents with multiple tab spreadsheets will probably be reformatted.



If scripts are not properly marked for concatenation, confusion will lead to mis-translation, resulting in your system not concatenating properly in other languages. In other words, if @I.S. translators do not know what is attached to each concatenated prompt, they may guess incorrectly. Never assume "the obvious". What is obvious in English, may not be so obvious in another language.

Also needed is the programmed playback date and time stamps (all variations, with weekday, without, with year, without) and exact explanations of basic functions. Example: explain whether "page" is a pager, a loud speaker or a piece of paper.

These items seriously affect playback accuracy.

Lastly, if the system is not going to be re-programmed for the foreign language, nor data tables will be modified for the new language grammar, please be aware that certain concatenations will not work well in other languages, no matter how much "massaging" the @I.S. translators give the translations.


For a long term solution to all language issues, see the information on the System Localizer.