Title: | T&N Pubs Systems and Tools Notes Conference |
Moderator: | ISOISA::HAKKARAINEN |
Created: | Thu Jun 29 1989 |
Last Modified: | Fri Dec 30 1994 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 91 |
Total number of notes: | 315 |
+---------------------------+ TM INTEROFFICE MEMORANDUM | | | | | | | | | d | i | g | i | t | a | l | *** DIGITAL INTERNAL USE ONLY *** | | | | | | | | +---------------------------+ DATE: 12-July-1993 FROM: Jae W. Kim DTN: 241-3437 NODE: WMOIS::KIM_J SUBJECT: EDMS V4.0 Tools Release Announcement This is to announce the official release of the EDM and EDMatic V4.0 applications. The EDMS version 4.0 applications are major revisions of the EDMS tools which provide the foundation for future tools releases and are not backward compatible with prior versions of the EDMS tools (V3.3A and lower). As of July 19, 1993, all sites submitting documents to the SSB for EDMS Electronic Document Submissions should install and utilize the EDMS V4.0 tools. Files processed prior to July 19, 1993, with the EDMS V3.3A tools will be accepted for an interim period. The major enhancement of the EDMS V4.0 tools is that it accepts industry compliant PostScript files from applications from various platforms (see below for a list of valid applications). VAX DOCUMENT V2.0 (and lower) is no longer supported by the EDMS tools. The executable VMSINSTALable kits, users' guides, installation guides are available in a public directory (B17::SYS$PUBLIC) and as individual kits orderable through the SSB. Release and installation notes for the EDMS tools are also available in a public area. The kit locations and part numbers along with the list of major enhancements to the tools, as well as installation recommendations for PUBS are attached. If there are any questions, feel free to contact me. Regards, Jae EDMS V4.0 Kits and Documentation Location: __________________________________________ The location of the savesets and documentation are available in B17::SYS$PUBLIC under the following filenames: Saveset/doc Filename Part Numbers ----------- -------- ------------ EDM V4.0 kit EDM040.A AQ-PEKFC-RE EDMATIC V4.0 kit EDMATIC040.A AQ-PEKKC-RE EDM user's guide EDM_V40_UG.MPS AA-PEKGE-RE EDM install guide EDM_V40_IG.MPS AA-PEKHD-RE EDMatic user's guide EDMATIC_V40_UG.MPS AA-PEKLE-RE EDMatic install guide EDMATIC_V40_IG.MPS AA-PG7GD-RE EDMS compliant file EDMS_V40_PG.MPS AA-PEKJE-RE production guide EDMS release notes EDMS_V40_RELEASE_NOTES.TXT EDMS installation notes EDMS_V40_INSTALL_NOTES.TXT EDMS V4.0 Major Enhancements: _____________________________ Some of the major enhancements for the EDMS V4.0 applications are as follows: - support for PDSC V3.0 (and some PDSC V2.0) formatters (the list of valid, but not limited to, applications and formatters from various platforms for EDMS compliance is as follows; Black and White support unless indicated by an *) - VAX DOCUMENT Version 2.1 and higher * - DITROF - Interleaf * - DECwrite - Arbortext - PC Windows applications (with Microsoft or Adobe Systems print drivers) - Microsoft Word - WordPerfect - AmiPro - Framemaker - Pagemaker - others - Macintosh applications (with Adobe Systems print driver) - Microsoft Word - Framemaker - Pagemaker - others - Adobe Photoshop * - Adobe Illustrator * - Aldus Freehand * - Mechanicals V3.0 and higher * - RAGS V4.1 and higher * - CorelDraw - Existing functionalities from prior EDMS versions - EDM Printspec link to the new DOCspec V3.0 RdB database via the EPIC server (integration with the CUBE program) - EDMatic Motif user interface and enhanced character cell interface - EDMatic customization features - Document size and type designation feature within EDM - Enhanced PostScript Printer Description (PPD) file accessibility within EDMatic - Flexible VMSINSTAL installation procedures for EDM and EDMatic For further details on the changes, refer to the EDMS V4.0 release notes. For further details surrounding the new list of EDMS compliant applications and formatters, refer to the EDMS Compliant File Production Guide. EDMS V4.0 Installation Recommendations for PUBS: ________________________________________________ The recommended installation for the EDM application for PUBS is as follows: - on a local disk (versus the system disk - some system managers prefer to have applications resident on a local disk) - LINK TO PRINTSPEC mode of operation (the U.S. Printspec node location is SSBKIT; for other geographies, see your CUBE system manager - the standalone mode of operation is intended for proofing purposes only until further notice) - Motif/DCL or DCL user interfaces (depending upon system setup whether workstation or terminal based) The recommended installation for the EDMatic application for PUBS is as follows: - on a local disk (versus the system disk - some system managers prefer to have applications resident on a local disk) - with ONLY THE 6 MOST USED PPD FILES (153 PPD files are included but PUBS will most likely only use the 6 Digital specific PPD files and this limits the amount of disk space used) - Motif/DCL or DCL user interfaces (depending upon system setup whether workstation of terminal based) For further details around the installation of the EDM and EDMatic applications, refer to the EDMS V4.0 installation notes or the EDM and EDMatic Installation Guides.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
87.1 | Local shopping... | ISOISA::HAKKARAINEN | Metal questions for metal heads | Thu Jul 15 1993 10:15 | 4 |
The EDMS documentation described in .0 is located in tools$disk:[tools.edms]. /kh | |||||
87.2 | Interleaf->EDMS?? | TNPUBS::HALLOWELL | Mon Jan 24 1994 09:34 | 18 | |
Has anyone successfully submitted a book written in Interleaf through EDMS? I mean a book written using the existing Interleaf templates. Last week I walked through the instructions for converting my .PS files to an EDMS suitable format, but the resulting hardcopies, complete with crop marks, shows the information ill-fitted with the top fifth of the pages shaved off. Even components like the title page, which I created using the same Interleaf template I've used for ages. Experienced and talented professionals came to my aid only to conclude that the margins for the Interleaf documents were not compatible with EDMS. I worked four hours Friday just modifying the title page with little success; and now the crop marks fail to appear in the final _COM.PS file. I'm actually losing ground in this effort. If anyone else has experienced this, I'm willing to listen. Rikk | |||||
87.3 | Updated instructions for EDMS/Interleaf | ISOISA::kh | Cogito, ergo, er, um ... | Tue Feb 01 1994 13:55 | 90 |
Return-Path: tnpubs::smaug::kimball Date: Thu, 27 Jan 1994 11:17:48 -0500 From: tnpubs::smaug::kimball To: tnpubs::o_oneil, tnpubs::phalen, tnpubs::noones, tnpubs::hakkarainen Cc: TNPUBS::FORTEN, KIMBALL Subject: Interleaf through EDMS Procedure This memo describes the process for producing EDMS-compliant Interleaf PostScript output. The process covers both 8.5X11 and 7X9 size documents. 1) Preparing your document for PostScript output generation. You must correctly prepare your book or document before creating the Interleaf PostScript file. There are two things that you must do: a) Set the correct page size for the book or document. You do this by selecting the page properties menu and changing the page size to 7x9 or 8.5x11. You MUST set the page size explicitly. If you have not been using a true 7x9 page size up to this point, you will have to adjust your document's margins to obtain an acceptable-looking page. These properties do not propagate from Catalogs, so you'll have to do it in every chapter of every book. b) Turn off all header pages in all documents. These are the things that generate revision information in the front of Interleaf printed output. For example: For: Jones on September 29 1993 blah blah... If you leave the header pages turned on, Interleaf will generate incorrect PostScript code, and EDMS processing will fail. <Note to Analyst> This failure had been caused by extraneous NULL characters in the PostScript file. Now it seems that leaving header pages in actually causes PL2PS to generate non-Adobe Red Book compliant PostScript! It places parentheses around arguments that should not have them, but only when Headers are present. Although they have been informed about the NULL character problem numerous times, Interleaf Output Engineering may not know about this latest problem. 2) Create a PostScript file using Interleaf The EDMS software operates by reading PostScript files as input. Therefore, you must create a PostScript file of the Interleaf book or document you intend to submit electronically. You do this by selecting one of the DESKTOP print queues from the Printers pull-down menu inside Interleaf. You can use any of the DESKTOP queues for 8.5X11 documents, although we recommend that you use either DESKTOP_GNU or DESKTOP_KODAK. You MUST use the queue DESKTOP_DECLASER for ALL 7X9 documents! There is an inherent limitation in the printing capabilities of the other queues that precludes their use for 7X9 document processing. 3) Processing the Interleaf PostScript output with EDMS By now you should have a PostScript output file of your document on your Interleaf desktop. We suggest that you move this to another directory using the DCL COPY command so that you can work on it from the command line. The DCL command you use to process the Interleaf PostScript file is as follows: $ EDMS /NOFIN postscipt-file-name or /KEY=2-5-2-number The qualifier you use depends on what stage of the electronic submission process you are in. If you are doing a final submission, you should use the 2-5-2 number for you product with the KEY qualifier. If you simply need to test your file before final submission, or before a 2-5-2 number has been assigned to your product, use the NOFIN qualifier. EDMS reads the Interleaf PostScript file and produces a master PostScript output file. This file will have the same name as the original, but with a .MPS (Master PostScript) file type. 4) Reviewing EDMS Composite or Color Separation Output To proof your processed book or document, you must further process the .MPS file with the EDMATIC utility. EDMATIC reads the .MPS file and lets you create composite or color separation proofs that you can print out. Please see the EDMATIC User's Guide issued by the Electronic Print and Publishing Group in the SSB for more information on how to use EDMATIC to produce proof copy. |