Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!mailrus!uwmcsd1!ig!agate!labrea!decwrl!sun!imagen!geof
From: geof@imagen.UUCP (Geoffrey Cooper)
Newsgroups: comp.lang.postscript
Subject: Re: PostScript compatible printers
Summary: UltraScript/Scribe problems
Message-ID: <1755@imagen.UUCP>
Date: 28 Jul 88 17:19:13 GMT
References: <6085@pyr.gatech.EDU> <1902@stpstn.UUCP>
Organization: IMAGEN Corporation, Santa Clara, CA 95052-8101
Lines: 35

In article <1902@stpstn.UUCP>, aad@stpstn.UUCP (Anthony A. Datri) writes:
> >the word "PostScript" such as Imagen's line (they call their
> >implementation "UltraScript").
> 
> When I worked at Scribe Systems (aka Unilogic), I heard from my co-workers
> that Ultrascript had problems with Scribe output.  My experiences with

The scribe problems were mostly experienced during beta test and
fixed.  Our customers use scribe with ultrascript daily.

> ...but there has
> to be *some* reason why they don't call it PostScript...

Let us be fair.

The reason is the US (and international) trademark laws.  "PostScript"
is a trademark of Adobe systems, and they have sole control over the
use of the name.  UltraScript (trademark by IMAGEN) was designed to be
and <is> no more or less than PostScript; we refer to it (legally) as a
PostScript compatible language.  Another way of saying this is that
UltraScript interprets PostScript programs correctly.  The difference in
names is the same one you see between IBM-PC's and the "compatibles."

Differences of functionality between UltraScript and PostScript are
always considered to be bugs and are fixed in subsequent releases of
the software.  UltraScript follows the LaserWriter where it differs
from the RedBook (e.g., take the length of a name).  Those we have
found to date are minor enough that we have been able to distribute
PostScript code that lives at exitserver level as workarounds until the
next software release.

- Geof Cooper
  Project Mudslide
  IMAGEN Corporation, a subsidiary of QMS Inc.
-- 
{decwrl,sun,saber}!imagen!geof