Lotus Development Corp. v. Borland International, Inc.

831 F. Supp. 223 (1993)

LOTUS DEVELOPMENT CORPORATION, Plaintiff,
v.
BORLAND INTERNATIONAL, INC., Defendant.

Civ. A. No. 90-11662-K.

United States District Court, D. Massachusetts.

August 12, 1993. As Amended August 19, 1993. Permanent Injunction August 19, 1993.

James C. Burling, Jeffrey B. Rudman, Hale & Dorr, Boston, MA, Henry B. Gutman, Kerry L. Konrad, O'Sullivan, Graev & Karabell, New York City, for plaintiff.

Peter E. Gelhaar, Donnelly, Conroy & Gelhaar, Boston, MA, Gary L. Reback, Peter N. Detkin, Andrew G. Konstantaras, Isabella E. Fu, Wilson, Sonsini, Goodrich & Rosati, Palo Alto, CA, for defendant.

Opinion

KEETON, District Judge.

A nonjury trial was held in this action in two phases. Phase I was tried on February 1-3, 1993; Phase II, on March 31-April 2, 1993. An Opinion of June 30, 1993 (the "Phase I Opinion") stated the court's findings and conclusions on issues raised in Phase I of the trial. The present Opinion states my findings and conclusions for the Phase II trial.

I. Introduction.

This Opinion assumes the reader's familiarity with, and follows the terminology set forth in, the Phase I Opinion. Background information appears also in Lotus Dev. Corp. v. Borland Int'l Inc., 799 F. Supp. 203 (D.Mass.1992) ("Borland II"), Lotus Dev. Corp. v. Borland Int'l Inc., 788 F. Supp. 78 (D.Mass.1992) ("Borland I"), and Lotus Dev. Corp. v. Paperback Software Int'l, 740 F. Supp. 37 (D.Mass.1990) ("Paperback").

As explained in the Phase I Opinion, the Phase I trial concerned issues of infringement raised in Lotus's original complaint, i.e., infringement by Borland's copying of Lotus's menu tree into the 1-2-3 emulation interface of Borland's Quattro and certain Quattro Pro spreadsheet programs.

Phase II of the trial concerns the full range of liability issues, including affirmative defenses, with respect to Lotus's supplemental complaint. The supplemental complaint alleges that Borland's "Key Reader" infringes Lotus's copyrights in its 1-2-3 programs.

II. Does Key Reader Infringe?

A. What is Key Reader?

The Phase I Opinion and the court's earlier Memorandum and Orders have focused on the 1-2-3 emulation interfaces in the Quattro and Quattro Pro programs. After executing the command that invokes the emulation interface in one of Borland's products, the program uses copies of the Lotus menu tree for display to the user, interaction with the user (i.e., interpreting the keystrokes typed by the user), and running macros.

The Key Reader is not a part of the emulation interface. The Key Reader feature may be turned on while the user continues to use another (e.g., the Quattro) menu tree. When Key Reader has been turned on, the program continues to behave as it had before, with one exception. With Key Reader on, when the program encounters a slash key ("/") in a macro, the program interprets everything that follows the slash key as though it were part of a macro written for use with Lotus 1-2-3. Thus with Key Reader on, the program uses Quattro Pro menus for display, interaction and macro execution, except when a "/" key is encountered in a macro. Then, the program runs macros as though they were written using the 1-2-3 menu tree.

A more detailed explanation of 1-2-3 "macros" is essential to explaining Key Reader.

Generally, a 1-2-3 macro consists of some text contained in a spreadsheet cell. When the macro is invoked, the program begins at the left end of the text and treats each character in the text as though the user had typed that character into the 1-2-3 program. For example, consider a macro that consists of the text "/wp". When the macro is invoked, the program behaves precisely as though the user had typed into the regular interface a "/" (calling up the first menu) followed by "w" (selecting the "Worksheet" branch of the menu tree) followed by "p" (selecting the "Page" leaf; this executable operation inserts a page break into the spreadsheet).

In writing a macro, the user may use special commands not found in the 1-2-3 menu tree. For example, the character "" in a macro is interpreted as though the user struck the Enter key on the keyboard. Consider a macro consisting of the text "/rfc". When invoked, this macro has the same effect as the user's typing into the 1-2-3 interface "/", "r", "f", "c", followed by striking the Enter key twice. That is, the program follows the "Range" branch, then the "Format" branch, then selects the "Currency" leaf. When the "Currency" leaf has been selected, the program asks the user to specify the number of decimal places and the block of cells whose appearance is to be altered to that of monetary units. The first "" is equivalent to striking the Enter key; the program accepts the default number of decimal places (two). The program then asks for the range of cells. The second "" is equivalent to striking the Enter key a second time; the program accepts the default range (one cell).

Other sequences of symbols in a Lotus macro have a special meaning. Of particular interest is "{?}". When the program encounters this sequence of characters in a macro, the program pauses and waits for the user to strike keys appropriate for the menu tree. Thus, consider a Lotus macro consisting of the text "/rf{?}". When invoked, this macro would follow the "r" command ("Range" from the first level of the Lotus menu tree), then the "f" command ("Format" in the Lotus menu tree). The program then encounters the "{?}" characters. Here, the program pauses and allows the user to input a menu command. The program will interpret what the user inputs as a choice from the Lotus 1-2-3 submenu corresponding to "Range" "Format". Thus, the user might strike the "c" key (followed by Enter) to format a cell as currency. If the user strikes the Escape key instead of striking "c", the program backs up the menu tree from the "Format" submenu to the "Range" submenu. The user may continue maneuvering up and down the Lotus 1-2-3 menu tree until striking the Enter key. When the user strikes the Enter key, the program returns to reading the text of the macro as though the user were continuing by striking the keys found in the remaining text of the macro. A macro consisting only of "/{?}" permits a user to select any executable operation by typing keys precisely as though the user were using one of Borland's emulation interfaces, but without display of the menus.

Lotus 1-2-3 macros may also contain more advanced commands. Thus, a macro may contain text such as "{if ...}" or "{let ...}". In these strings of characters, the ellipses refer to additional text or "arguments" the user would provide. When the program encounters an advanced command such as this, the program follows whatever procedures that command calls for. For example, the text "{blank A1..G45}" would cause the program to erase each of the cells from "A1" (first column and first row) through "G45" (seventh column and forty-fifth row). "if", "let", and "blank" are all labels in the Lotus 1-2-3 macro language that do not appear in the 1-2-3 menu tree.

In sum, when Key Reader is on and a slash key is encountered in a macro, the program follows the text of the macro as though the characters were being typed during the program's use of a copy of the 1-2-3 menu tree (and with some other means for interpreting the various special Lotus 1-2-3 macro language commands). When Key Reader is off, or no "/" key is encountered in a macro, the program interprets macros by reference to a different (e.g., the Quattro) menu tree. With Key Reader off, Borland's programs cannot correctly interpret 1-2-3 macros.

Quattro and Quattro Pro version 1.0 did not contain the Key Reader feature; they contained only the emulation interface. Thus in these programs, the user could execute Lotus macros only when the user was employing the emulation interface; i.e., using Lotus 1-2-3 menus for display, interpreting user commands, and executing macros.

The Key Reader was first introduced in Quattro Pro version 2.0. Quattro Pro version 2.0, 3.0, and 4.0 contain both the emulation interface and the Key Reader feature (which is used from the native menus).

Borland removed the emulation interface from Quattro Pro version 4.01 (and subsequent releases of Quattro Pro) after the Borland II decision in this case allowed partial summary judgment for Lotus. Thus, Quattro Pro versions 4.01, SE, and Quattro Pro for Windows contain the Key Reader feature but have no 1-2-3 emulation interface.

B. Copying.

In developing Key Reader, Borland modified portions of the earlier Quattro Pro programs that contained the full 1-2-3 emulation interface. Accordingly, I begin with a review of how the Lotus menu tree was copied into the Quattro Pro emulation interface before analyzing how that was, in turn, incorporated into Key Reader.

1. The 123.MU file.

The actual menu tree for the Quattro Pro emulation interfaces (versions 1.0, 2.0, 3.0, and 4.0) was in a file labeled "123.MU". Thus, when the program was running and the user had selected the 1-2-3 emulation interface, the program would refer to the 123.MU file to determine the form of menu commands and menu structure used to present the set of executable operations to the user, interpret user commands, and interpret macros. If the user had selected a different interface, e.g., one using the Quattro native menus, the program would refer to a different file for the menu commands and menu structure for display, interpretation of commands, and macro execution.

A text print-out of portions of the 123.MU file is in evidence under seal as Exhibit 13. The parties have included, however, the first page of this print-out in the public record. See Docket 311, Exh. A. An examination of the print-out demonstrates that the entire Lotus menu tree is copied into the file, with differences in indentation detailing the menu structure. That is, the structure of the menus and submenus is recorded in the file by changes in indentation. As explained in the Opinion for Phase I, when the program is using the 123.MU file as the source for its menus, it presents to the user a virtually identical copy of the Lotus menu tree (with Borland's additional menu commands inserted into the tree).

2. Key Reader files.

As the above explanation of macros suggests, interpretation of Lotus macros requires that the program treat the characters in the macro text as though they were keystrokes into a spreadsheet program using the Lotus menu tree (except for the characters in the macro text that are special commands in the Lotus macro language).

I find that, to implement the Key Reader (or at least that portion of the Key Reader that interprets characters from the Lotus menu tree), Borland began with the 123.MU file from the emulation interface. Borland then prepared a new file by reproducing the old 123.MU file but with only the first letter of each menu command name where the entire Lotus menu command name appears in the old 123.MU file. See Warfield Dep'n, IX:43. Put another way, the point is that to implement Key Reader Borland used a program file containing the same copy of the 1-2-3 menu tree structure and commands that Borland had used in its emulation interface, but with each menu command name stripped of everything after the first letter. Borland then appended this copy of the "stripped menu tree" to its quattro.mu file.

At various stages, Borland introduced other changes in how the menu structure is recorded in the stripped file, altering parentheses or indentation, etc. For example, I find that Borland may have altered the symbols used to record Lotus's menu structure, inserted the word "PICKLETTER" before the first letter of the menu command, or made other changes. Compare Exhibit 13 with Exhibit 517; see Warfield Dep'n, IX:43 at 148-49. Some of these things may actually appear in the old 123.MU file — Exhibit 13 contains only portions of the old 123.MU file. See Warfield Dep'n, IX:43 at 107-109, 148-49. In any event, I have considered the file and possible changes. I find that none of these changes is material to the scope or nature of copying from the Lotus 1-2-3 program.

In short, I find that the Key Reader file contains a virtually identical copy of the Lotus menu tree structure, but represented in a different form and with first letters of menu command names in place of the full menu command names.

Borland contends that the command letters copied from Lotus 1-2-3 that are in Borland's Key Reader files are not in the same order as displayed on the screen in Lotus 1-2-3. That is, if one reads sequentially down the Key Reader file, one encounters the Lotus commands in a different order than when reading the menus from the display screen while running Lotus 1-2-3. This is true, however, only in the sense that the menu structure of Lotus 1-2-3 is represented in a different way in the Key Reader file than on the Lotus 1-2-3 display screens; in the file, the structure is detailed by differences in indentation (or other means) rather than through display on the screen. I find that the file (in evidence under seal, Exhibit 517) fully delineates a virtually identical copy of the menu structure of Lotus 1-2-3 including the first letter of each menu command in the corresponding location in the copy of the menu structure.

Because these menus are used in interpreting macros but are never fully displayed to the user, the parties have sometimes referred to these as "phantom menus."

In sum, to interpret macros, Borland's programs use a file with phantom menus consisting of a virtually identical copy of the Lotus menu tree that Borland used for its emulation interface, but with only the first letter of each menu command name where the complete menu command name previously appeared.

C. Copyrightability Issues.

1. Renewed and new arguments concerning definition of the idea.

Borland contends that copyright protection covering the structure of the 1-2-3 menu tree and the first letters of the commands in the 1-2-3 menu tree (i.e., Borland's phantom menus) would be equivalent to copyright protection for a "system" or "method" of communication between the user and the program. Thus, Borland argues that copying of the 1-2-3 menu tree structure and first letters of command names is a necessary part of any system for interpreting Lotus 1-2-3 macros. Citing the proposition that copyright law does not protect a "system", see 17 U.S.C. § 102(b), Borland argues that the Lotus copyright cannot extend to Borland's phantom menus.

Lotus responds that Borland has not proved that copying of any part of the menu tree is necessary for running or translating macros.

As a preliminary matter, I observe that the parties, witnesses (and the court, in some instances) have not used the terms "macro translation," "macro conversion," "macro execution," and "macro compatibility" with precision during the Phase II trial and earlier proceedings. In order to avoid possible future misunderstanding, I will explain the ambiguity in use of these terms before proceeding farther.

Macro "conversion" refers to translating a macro that was written using Lotus 1-2-3 into a macro written in a form for use in another program. For example, the macro "/rfc " in Lotus may be translated, using the macro translation assistant in Excel 2.1, into an Excel 2.1 macro having the text:

= SET.NAME("Selection_Save",SELECTION())

= SET.NAME("Range3",SELECTION())

= DISPLAY(FALSE)

= SELECT(Range3)

= FORMAT.NUMBER

("$#,##0.00;($#,##0.00)"))

=RETURN()

This macro text is written in the Excel macro language and is executed by reference to the Excel menus. Thus, formatting a single cell to be displayed in monetary units with two decimal places (the result of the "/rfc " macro in Lotus) may be achieved in Excel 2.1 by selecting a single cell in an Excel spreadsheet followed by selection of the "Format" menu command, the "Number" command in the submenu of Format, then the "$#,##0.00;($#,##0.00)" (currency) leaf (compare with the second to last line of the Excel macro).

This facility for conversion of macros may also be referred to as a "one-time macro translator." The translator takes a Lotus macro and converts it into a macro written in a different macro language, for use with a different menu tree. Once the translation has been made, a user may run the translated macro as frequently as desired in the other program. Because the macro is written in a different macro language, the program need not refer to a copy of Lotus's menu tree to run the (translated) macro. Thus in Borland II, I observed that:

I need not and do not decide whether Borland is prohibited from reading and interpreting macros that have been created by users of 1-2-3. Had Borland created a program that read users' 1-2-3 macros and converted them to macros for use in the Quattro programs' native modes, so that they could be interpreted, executed, modified, debugged, etc. by resort to Borland's command hierarchy, that would have presented a different case from the one now before me.

799 F.Supp. at 214. In other words, I did not decide issues concerning one-time translation of macros into a different macro language, such that the macro could be executed, modified, and debugged without reference to copies of the Lotus menu tree.

Alternatively, consider a continuous macro "interpreter." This facility executes Lotus macros by referring to copies of the Lotus menu tree contained within the program. Macro interpretation may thus be viewed as continuous "translation" of macros as each macro is executed, or "on-the-fly" interpretation. Each time a macro is executed, modified, or debugged, the macro remains written in the Lotus macro language. Each time a macro is executed, modified or debugged, the program refers to the Lotus menu tree or structure.

Both one-time conversion and on-the-fly interpretation may be referred to as "macro translation," as providing an ability to "run" Lotus macros, and as providing "macro compatibility" with Lotus. For both, the user may begin with a Lotus macro and run the macro either by translating it first (one-time translation), or by parsing it with reference to the Lotus menu tree structure each time the user runs the macro (on-the-fly).

An example of the confusion in terms is demonstrated by testimony from Borland's Chief Executive Officer, Phillipe Kahn. Kahn testified that "macro translation was not a viable way to do things." I:13 at 100. From the context of this testimony, I understand the testimony to refer to one-time "macro translation" rather than what Borland now refers to as (on-the-fly) "macro translation" performed by Key Reader.

Borland's Key Reader does not perform one-time translation such as Excel 2.1 does. Rather, Key Reader interprets macros on-the-fly, by reference to "phantom" menus that contain a copy of the Lotus menu tree.

In clarifying this terminology, I do not decide whether copying of the Lotus menu structure for the purpose of one-time translation rather than on-the-fly interpretation should be accorded different treatment under copyright law. Also, I do not decide any issue concerning who (if anyone) owns the copyright in a macro written by a user in reliance on expression found in the Lotus 1-2-3 menu tree, or who (if anyone) owns the copyright in a translation into another language of a macro written in reliance on Lotus 1-2-3. These issues are not before the court. Rather, I make clear that I decide only those issues raised by Borland's Key Reader; i.e., only issues involved in on-the-fly interpretation using Borland's "phantom" menus.

Having clarified the terminology, I now reject Lotus's argument that on-the-fly macro interpretation does not require copying from the Lotus menu structure and first letters of the command names. To interpret a macro, the program must use the Lotus 1-2-3 menu structure. If a program did not have a representation of the 1-2-3 menu hierarchy somewhere within the program code (or in a file that is used by the code), then there is no way that the program could understand that "rfc" refers to a path through a menu tree to the specific executable operation that changes a cell or cells appearance to monetary units (i.e., a path through the range and format menus to the currency leaf). Whether the menu tree is copied into a file or directly into the code of a program does not make a difference. The scope of copying of the menu tree is the same whether done in one computer language, a different language, or in a file. Accordingly, I reject Lotus's contention that no part of the 1-2-3 menu tree need be copied to interpret 1-2-3 macros.

Nevertheless, I also reject Borland's contention that the menu tree structure and first letters of the menu commands constitute a "system" or "method," as those terms are used in copyright law.

Of course, it is possible to think of the Lotus 1-2-3 menu tree as a "system" for translating user keystrokes into executable operations (whether the keystrokes are typed into the keyboard or are taken from the text of a macro command). In the same way, a book may be thought of as a system for communicating various ideas and images to readers. Indeed, the only way of conveying each of the exact images of "Gone With the Wind" in the same order as in "Gone With the Wind" is to copy at least a great deal of the nonliteral expression in the book, if not the precise words of the book as well. Nevertheless, copyright protection extends both to the specific words of "Gone With the Wind" and to nonliteral elements of the novel. Accordingly, the ability to describe a work as a "system" is not decisive of whether the work is a "system," or instead is protected expression, under copyright law.

In calling the copying that is contained in the phantom menu tree a "system," one may attempt to distinguish the copying found in the phantom menus from copying of a book on the following grounds. A book communicates to the reader. The phantom menus, however, permit the user to communicate commands to the program. Thus, one may contend that the phantom menu trees constitute a method or system for the user to communicate executable commands rather than a system (such as a book) for communicating thoughts to the reader.

For the following reasons, I reject this basis for concluding that, in creating the phantom menus, Borland copied a system and not its expression. First, like Lotus's menu tree, the protected expression of a compilation may be viewed as a system for accessing information. The purpose of a compilation is to communicate facts. The specific facts communicated, however, are not copyrightable. Copyright protects only the selection, arrangement and manner of presentation of the facts (to the extent that those elements meet the other requirements for copyrightability). See Feist Publications, Inc. v. Rural Tel. Serv. Co., 499 U.S. 340, 111 S. Ct. 1282, 113 L. Ed. 2d 358 (1991). The selection, arrangement, and manner of presentation in a compilation may provide the user with a method or systematic manner of accessing the (uncopyrightable) facts. Thus, copyright law protects only that part of a compilation that the reader actually uses for selection of facts that the reader wants to know. Nevertheless, the expressive aspects of a compilation remain copyrightable.

Accordingly, I conclude that the fact that the copied menu structure and first letters of the menu commands may be used to specify executable operations does not bar a finding that these elements are copyrightable. For the reasons explained in detail in Sections II.A.1 and II.B.2.b of the Phase I Opinion, the structure of the menu tree including its designated keys for invoking commands (i.e. what Borland copied into the phantom menus) may also be viewed, in a light favorable to Borland, as a type of selection and arrangement of the executable operations in Lotus 1-2-3. The fact that the phantom menus may be used by a "reader" (whether directly or through the text of a macro) to access Lotus 1-2-3's executable operations does not compel a conclusion that this constitutes a system. See also Paperback, 740 F.Supp. at 72-73 (rejecting argument that the macro language is a non-copyrightable element of the program).

Similarly, a program's computer code may be described as a system. Computer code consists of a series of commands that the user issues to the computer by running the program. The commands are written in such a way that the computer code as a whole is a system for communicating the program's functionality to the computer. Nevertheless, Borland cannot and does not dispute that computer code is copyrightable.

Borland's contention that the menu tree structure is a system, or is strictly utilitarian in nature, raises again the same problem of defining the "idea," "system," "process," "procedure," or "method" of Lotus 1-2-3 that I have addressed since the beginning of this case. Borland wishes the court to define the "idea," "system," "process," "procedure," or "method" of Lotus 1-2-3 as including the ability to interpret macros written for use with Lotus 1-2-3. I rejected this contention in deciding the parties' cross motions for summary judgment, see 799 F.Supp. at 212-14, 216-17, and I reject this argument for the same reasons here. The fact that users of Lotus 1-2-3 have created macros in reliance on expressive aspects of Lotus 1-2-3 does not convert that expression into a part of the "system." That Borland wishes to copy protected expression contained in Lotus's menu tree for what Borland contends is a utilitarian purpose also does not turn that expression into a "system" under copyright law.

See Id. at 213-14. See also Mazer v. Stein, 347 U.S. 201 [,74 S. Ct. 460, 98 L. Ed. 630] (1954) (use of statue as lamp does not bar copyright protection on expression in statue); 1 Nimmer on Copyright § 2.18[D] at 2-207 ("If, however, there is a copying of the copyrightable expression, then an infringement should be found, even if the defendant employs the material for use rather than explanation.").

Borland nevertheless contends that according copyright protection to the menu structure and first letter of the command names would impermissibly protect a "discretionary pattern of events or processes." Section 102(b) provides:

In no case does copyright protection for an original work of authorship extend to any idea, procedure, process, system, method of operation, concept, principle, or discovery, regardless of the form in which it is described, explained, illustrated, or embodied in such work.

17 U.S.C. § 102(b). Borland quotes a proposal by the Information Industry Association to include the following language in Section 102(b):

However, copyright protection may exist in a collection of ideas or abstractions arbitrarily selected from a plurality of alternative ideas or abstractions or in a discretionary pattern of events or processes.

(Docket No. 345 at 8 (quoting Copyright Law Revision: Hearings Before the Subcomm. on Courts, Civil Liberties, and the Admin. of Justice of the House Comm. on the Judiciary, 94th Cong., 1st Sess. 334 (1975))). Because Congress did not adopt this "exception," Borland contends that Congress manifested an intent that a "discretionary pattern of events or processes" is not protected under copyright law and should be determined to be a "system" under section 102(b).

Nothing Borland presents to the court, however, provides any explanation of why Congress did not include this language in the statute. Failure to adopt this language may manifest a Congressional belief that the language was unnecessary or irrelevant. Indeed, Congress did not adopt any statutory language denying copyright protection for "a collection of ideas or abstractions arbitrarily selected from a plurality of alternative ideas or abstractions or in a discretionary pattern of events or processes."

In any event, the explanatory language accompanying the proposal indicates that the proposal was intended to assure that copyright protection is accorded to nonliteral aspects of computer program code. Thus, Borland's argument may be interpreted as a contention that nonliteral aspects of computer code are not copyrightable, under section 102(b). If so, Borland's argument has been consistently rejected by the courts, including this one.

See Paperback, 740 F.Supp. at 54; Arthur R. Miller, Copyright Protection for Computer Programs, Databases, and Computer Generated Works: Is Anything New Since CONTU?, 106 Harv.L.Rev. 978, 994-96 nn. 78-88 (March 1993) (collecting cases). See also Computer Assocs. Int'l, Inc. v. Altai, Inc., 982 F.2d 693, 702 (2d Cir.1992) ("We have no reservation in joining the company of those courts that have already ascribed to this logic [that non-literal structures of computer programs are protected by copyright].").

I again reject the argument that copyright cannot extend to nonliteral aspects of a computer program. Moreover, Borland is wrong when it argues that, by failing to adopt the proposed statutory language, Congress manifested any intent concerning the definition of "system" in section 102(b).

Borland next argues that its phantom menus must constitute a "system," or be found "utilitarian" in nature, because the phantom menus do not appear on the screen and are not communicated to the user.

This argument is readily dismissed. A user may never see computer code, but copyright protection is accorded to the code. Borland proposes a distinction on the ground that computer code may still be printed and read by someone. This distinction is vacuous for three reasons. First, the phantom menus may also be printed out; exhibit 517 is one copy. If one accepts the proposition that nonliteral aspects of computer code are copyrightable, the fact that the printed form of what Borland copied is not identical to any Lotus code or is not actually displayed to the user is not material to a finding that the Lotus menu structure contains copyrightable expression. Second, the fact that the phantom menus are not displayed does not mean that the user does not know they are there. Finally, copyright protection has been accorded to forms of computer code that are not generally intelligible to humans. See Apple Computer, Inc. v. Franklin Computer Corp., 714 F.2d 1240, 1249 (3d Cir.1983) (object code), cert. dismissed, 464 U.S. 1033, 104 S. Ct. 690, 79 L. Ed. 2d 158 (1984).

Last, Borland argues that it has removed anything expressive in the Lotus menu tree from its phantom menus, leaving only the first letters of the command names as "markers" of the program's functionality. See Docket No. 311 at 25-26. This is not the case. The letters serve as "markers" of the Lotus menu tree structure. Claiming that the "markers" are part of the functionality again incorrectly assumes that the "idea" or "function" of Lotus 1-2-3 includes menu structure and first letters of the command names. Moreover, for the reasons explained in the Phase I Opinion, I conclude that the menu tree structure is original and was not dictated or even substantially limited by functional considerations at the time of its development. Accordingly, I also conclude that the menu structure and organization (including the first letter of the commands, used to mark the structure) are part of the protectable expression found in the Lotus 1-2-3 program.

In sum, I conclude that the Lotus menu structure, organization, and first letters of the command names are not within the definition of the "idea," "system," "process," "procedure," or "method" of the Lotus 1-2-3 program and constitute part of the protectable expression found in the program.

2. Borland's arguments concerning earlier "holdings" of this court.

In arguing that the copying found in Borland's phantom menus is permissible, Borland places considerable reliance on what it characterizes as earlier "holdings of this court that expressly authorize a macro translator such as the Key Reader." See Docket No. 345 at 1-3. As a preliminary matter, before the Key Reader complaint in this case, no party before this court had ever pressed any actual dispute or controversy between two parties over whether a specific macro "translation" facility, standing alone, would infringe Lotus's copyrights. Article III courts decide only cases and controversies actually before the court. U.S. Const. Art. III, § 2. Accordingly, I could not possibly have "held" in any earlier decision that macro translation as performed by the Key Reader is permissible under copyright law.

After examining Borland's specific citations to my earlier opinions, I also observe that in making this argument Borland has done a bit of interpretative twisting of the language of my earlier opinions. In earlier opinions, I have rejected a defendant's arguments that were based on the incorrect premise that the defendant was somehow required to copy specific elements of the Lotus 1-2-3 program.

See Paperback, 740 F.Supp. at 78 (no showing that copying of entire interface is necessary for macro translation); Borland II, 799 F.Supp. at 218 (distinguishing Crume v. Pacific Mut. Life Ins. Co., 140 F.2d 182, 184-85 (7th Cir.), cert. denied, 322 U.S. 755[, 64 S. Ct. 1265, 88 L. Ed. 1584] (1944), as involving a system requiring use of only descriptive words, while in this case, varying full-word menu command names is not the only alternative for creating a different expression of the menu tree idea).

Contrary to Borland's arguments, I do not interpret the language in any of my earlier decisions rejecting these arguments as even remotely "authoriz[ing]" Borland to create its Key Reader. Explaining that a defendant's argument is overbroad by use of an example is hardly equivalent to "holding" that the example is legally permissible. Moreover, in explaining my earlier decisions, I have twice observed that copying of expressive aspects of Lotus 1-2-3 may not be permissible under copyright law, even if that is the only way to achieve macro compatibility. See Paperback, 740 F.Supp. at 69; Borland II, 799 F.Supp. at 214. In Borland II, I stated that "I need not and do not decide whether Borland is prohibited from reading and interpreting macros that have been created by users of 1-2-3." 799 F.Supp. at 214. In short, I reject Borland's attempt, by selective reading and interpretation of language from earlier opinions, to twist discussions contained in those opinions into "holdings" of this court.

Finally, much of Borland's argument rests on statements concerning whether a "macro translator" such as in Excel 2.1 infringes. Borland attempts to equate Key Reader with Excel 2.1 by labeling the Key Reader as a "translator." As explained above, however, Borland has expanded the term "translator" from the one-time translation done in Excel 2.1 to include on-the-fly interpretation as done in Borland's programs. In Borland II, I expressly did not decide issues concerning one-time translation, 799 F.Supp. at 214 (quoted supra), let alone issues concerning an expanded definition of macro "translator" — a definition including on-the-fly interpretation of macros.

D. Substantial Similarity.

For the following reasons, I find that what Borland copied into the Key Reader phantom menus is substantially similar to Lotus 1-2-3.

Contained in the phantom menus is a virtually identical copy of the menu structure and organization of Lotus 1-2-3, using the first letter of command names and other symbols to delineate that structure. Although Borland's copy may use a different way of representing the menu structure than is contained within the Lotus code or displayed to the user while running Lotus 1-2-3, I find that what was copied by Borland (details of expression of the menu structure) is virtually identical to details of expression of the Lotus 1-2-3 program's menu structure.

I also conclude that differences in the method Borland uses to represent the menu tree structure in its phantom menus file does not negate a finding that the copied expression of the menu tree structure is substantially similar to the Lotus 1-2-3 program. First, copyright law protects nonliteral aspects of a copyrighted program. Thus, one need not copy the specific code of a program to infringe copyrights in the program. Second, Borland's copying is analogous to a translation. No identity of words may exist in a translation into French of a book written in English. Nevertheless, the translated copy infringes by making a virtually identical copy of the book, but using a different method for representing the words and grammar structure. See 17 U.S.C. § 101 ("derivative work" includes translation); 17 U.S.C. 106(2) (copyright owner has exclusive right to prepare derivative works). Here, Borland created a virtually identical copy of the Lotus menu structure, but translated (nearly verbatim) the menu structure into a different language for representing menu structures.

Borland next contends that the fact that the phantom menus are not displayed on the screen prevents a finding of substantial similarity. I reject this contention for the same reason that I rejected Borland's argument that Borland copied only unprotected expression because the phantom menus are not displayed. See Section II.C.1, supra. That is, copyright law does not require that a program display its source or object code for copied elements of the code (literal or nonliteral) to be substantially similar.

In addition, I find that a user would understand that Borland was using a copy of the Lotus menu structure when executing a macro. Consider, for example, the "/{?}" macro described above. With this macro, the user can traverse the Lotus menu structure precisely as though typing keys into the Lotus program. Similarly, Key Reader executes macros by sequentially parsing the (Lotus) macro text. This is demonstrated most clearly when one steps through macros in the Borland macro debugger. In addition, Borland's experts contend that a user may not even look to the full command names when using Lotus menus or macros. E.g. Liddle Dec'n, VI:11, ¶ 53. I accept this point and reject Borland's premise that the Borland programs do not demonstrate to the user that Borland copied Lotus's menu structure.

Finally, I find that the Lotus menu structure, including the first letters of the command names that mark that structure, constitutes a substantial part of the Lotus expression. What Borland copied into Key Reader is that portion of the Lotus program that determines precisely how the user may select from among the executable operations in the program. Qualitatively, Borland's phantom menus copy a substantial part of what a user would think of as constituting the Lotus program: the menu structure and the sequences of keystrokes for invoking each of Lotus's executable operations.

III. Affirmative Defenses.

Borland raises four affirmative defenses: waiver, laches, estoppel, and fair use. Each is considered below.

A. Waiver.

The parties agree that in order to succeed in its waiver defense, Borland must prove that Lotus voluntarily and intentionally relinquished a known right. See Docket No. 311 at 26; Docket No. 338 at 20. That is, Borland must prove (1) voluntary and intentional relinquishment (2) of a right that Lotus was aware that it had.

Borland points to six statements that it contends demonstrate an intention to relinquish any right to assert claims against Key Reader. The first three statements were made before the Key Reader had been introduced into any Borland product. For these statements, Lotus clearly could not have intended to waive claims specifically against Key Reader; Lotus was unaware of Key Reader. To overcome this obstacle, Borland contends that these statements reflect the intentional relinquishment of a known right to claim that any kind of macro "translator" infringes.

The three statements made before Key Reader was released were made by the president of and counsel for Lotus during proceedings in the Paperback case. See Manzi Dep'n, IX:41; Lemberg Dep'n, IX:24; Trial Transcript, VIII:B.16. Each of the statements concerns whether Lotus intended to assert a claim of infringement against macro translation as performed by Excel.

Borland first cites a statement by Jim Manzi, President of Lotus, made during a deposition in the Paperback case. The statement ends with the conclusion that "as far as I know, we have no issue of that [Excel] product." Entirely missing from this statement is any evidence (1) that Manzi was aware of a right to prevent copying found in Excel (even this assumes, without support, that (a) there was copying, and (b) Manzi was aware of that copying), or (2) that Manzi intended to waive a claim against products other than Excel, with respect to any type of macro translation. This statement does not reflect an intention to relinquish any known rights.

Borland next cites statements by Lotus's General Counsel, Thomas Lemberg. The Lemberg statements, in evidence under seal, were not made in a context associated with waiver of rights. Accordingly, I cannot find a manifested intention to relinquish known rights based on these statements. In addition, having examined the Lemberg testimony, I also find that Mr. Lemberg was referring to one-time translation of macros into a different macro language, rather than macro translation in general, and more specifically, rather than referring to any program that executes macros by reference to copies of Lotus's menus. Whether or not the distinction between one-time translation and direct execution of macros makes a material difference under copyright law is not significant; a party may waive rights without following the specific contours of copyright law. In any event, I find that the Lemberg statements do not demonstrate an intent to relinquish either a specific right or more generally a right to assert claims against all forms of macro translation or execution.

Finally, Borland cites the Paperback trial transcript at a point where Lotus's counsel, Henry Gutman, responded to a defendant's contention that the defendant "had to" copy the entire Lotus user interface into its own spreadsheet product. Gutman argued that the premise of this argument is wrong because Excel had made a commercially successful product that did not copy the full interface, and in fact, included the ability to "translate[] and run in Excel" Lotus macros. VIII.B.16 at 45. Based on the materials before me, I find that (1) this statement was intended to discredit a defense argument and does not demonstrate that Lotus intended to waive any right, and (2) this does not demonstrate an intent to waive claims against all types of macro translation as opposed to Lotus's understanding of Excel's one-time translation.

Moreover, each of the three statements cited above was made in the context of an infringement suit against companies that had copied the entirety of Lotus's user interface. Up to the time of the three statements cited by Borland, Lotus had never been faced with issues raised by a program that did not fully copy the Lotus 1-2-3 interface but executed Lotus macros on-the-fly. Accordingly, for each of the statements I find that Borland has not proved (1) that, at the time of the statement, Lotus was aware of a right to bar copying of its menus when the copied menus were used only to execute macros on-the-fly, or (2) that Lotus intended to relinquish its right to assert claims against a program that directly executes Lotus macros by reference to copies of the Lotus menus, rather than by one-time translation of the macros into the product's own macro language.

Borland next cites three statements made by Lotus after Key Reader had been introduced into Borland's products. The first is a response to a Borland request for admissions. According to the response, Lotus admitted that

it does not contend that the ... ability to execute "macros" originally written using Lotus 1-2-3 by means of a conversion or translation program, standing alone, would infringe ..., but qualifies its admission to state that Lotus does contend that the 1-2-3 User Interface of Quattro and Quattro Pro, including, inter alia, its use of the 1-2-3 menu structure to provide the ability to execute macros originally written using Lotus 1-2-3, impermissibly copies protected expression contained in Lotus 1-2-3.

See VII:B.1. Later in the same document containing Lotus's response to a request for admission, Lotus objected to a Borland request for an admission that the ability to execute Lotus macros while in Quattro Pro's native mode does not infringe. Lotus's objection was based on the ground that, as far as Lotus knew, Quattro Pro had no such ability. See VII:A.7.

This admission does not constitute a waiver of a right to assert infringement claims against Key Reader. Lotus explicitly stated that it does contend that use of the Lotus menu structure to provide the ability to execute macros is impermissible, as done in Borland's emulation interface. For the reasons explained in Section II.B above, I find that the Key Reader executes macros by using copies of the Lotus menu structure in a way very similar to the way that the 1-2-3 emulation interface executed macros. The qualification to the admission demonstrates an intent to pursue claims against a program doing precisely what Key Reader does.

Borland contends, however, that the reservation should be interpreted as objecting to a facility such as Key Reader only when it is a part of an emulation interface, and not when it is incorporated into Borland's native menu interface. Considering the circumstances of the admission, however, I find that such an interpretation is unreasonable. First, under Borland's proposed interpretation, the qualification to the admission does not qualify the scope of the admission. The admission without the qualification was already limited to macro translation "standing alone." Second, when specifically asked about running Lotus macros while using the native menu interface, Lotus's answer demonstrated that Lotus was not then aware of Borland's Key Reader feature. It is, therefore, more reasonable to interpret Lotus's response as (1) a statement that Lotus was not contending in this suit that one-time translation or conversion infringes (a point very distinct from execution of Lotus macros by reference to "phantom" menus), or (2) a statement that Lotus was not contending that translation infringes because there was no need to make that claim in this case — Borland's emulation interface infringed and the scope of that infringement was sufficient for claims against the products then at issue.

If Borland wished later to be in a position to make its present assertion of waiver, it should have made full disclosure up front about Key Reader and obtained an unambiguous response. Borland's present claim of waiver is an attempt, wholly without merit, to escape the consequences of its own litigation strategy. Lotus was entirely free to respond as it did without waiving any right. I find that Lotus's response to the request for admission does not demonstrate an intent to relinquish a known right to assert claims against Key Reader, or a feature like Key Reader.

Borland next points to a statement by Lotus's counsel at a conference in June 1991. See VIII:B.17. In making the statement, Lotus's counsel advised the court that if Borland "include[d] 1-2-3 menus and alternate user interface" in a product Lotus believed was about to be released, Lotus would seek a preliminary injunction. Borland's contention that this constitutes a waiver of claims against any program that does not "display" the menus approaches, if not crosses, the line into frivolousness.

Finally, Borland points to a footnote in one of Lotus's briefs. See VIII:B.6. Here, Lotus was responding to Borland's contention that it had to copy and display the entire menu tree to achieve macro compatibility. In the footnote, Lotus argues that Borland was ignoring this court's distinction in Paperback between display of menus and executing macros by "interpretation, translation or conversion (as then existed in Excel or the foreign language versions of Lotus 1-2-3)." The foreign language versions of Lotus 1-2-3 perform a one-time translation or conversion of macros from English releases of 1-2-3 into a macro using the foreign language version of 1-2-3. See Morgan Dec'n, VI:12. This does not constitute waiver for several independent reasons.

First, the language focuses on the court's distinction, not Lotus's.

Second, Lotus sought to rebut Borland's argument by pointing out that macro compatibility might be achieved without display of the menus and cited examples of one-time macro conversion but not on-the-fly macro interpretation. In the circumstances here, I do not find that impeachment of a defendant's argument by example demonstrates an intent to relinquish any rights.

Third, at the time the argument was made, Borland had not released a product containing Key Reader but without the full emulation interface. Thus, Lotus was not faced with any decision over whether to assert claims against a program that copied Lotus's menus, but only for on-the-fly interpretation. I find that this statement does not demonstrate an intention to relinquish a known right to pursue infringement claims against a program containing Key Reader.

In sum, considering the statements proffered by Borland both separately and as a whole, I find that Borland has not proved that Lotus has waived a right to pursue its claims against Key Reader.

B. Laches.

To succeed in its laches defense, Borland must prove that (1) Lotus inexcusably or unreasonably delayed in raising claims based on Key Reader, and (2) Borland was prejudiced by this delay.

1. Delay.

Lotus first raised claims of infringement based exclusively on Key Reader in its motion for leave to file supplemental complaint, filed December 7, 1992. (Docket No. 250.) Borland contends that this is more than two years after Key Reader was introduced. As explained above, however, Key Reader was introduced into products that also contained the emulation interface (Quattro Pro 2.0, 3.0, and 4.0).

I begin by examining whether Lotus's delay was unreasonable or inexcusable during the time period when Borland's products included both the emulation interface and Key Reader. I then examine the delay in filing suit after Borland removed the emulation interface and marketed a product containing only Key Reader, i.e., after Quattro Pro 4.01 was announced in August 1992.

For the following reasons, I find that the delay in filing suit before Borland introduced Quattro Pro 4.01 into the market was both reasonable and excusable.

First, even assuming Lotus was aware or should have been aware of Key Reader in Quattro Pro 2.0, 3.0, and 4.0, a fact disputed by Lotus, there is little reason that Lotus should have known (and no evidence that Lotus did know) that Key Reader was anything other than a link to the macro execution facility that is contained in the 1-2-3 emulation interface. In these circumstances, it would have been reasonable for Lotus to believe that if the emulation interface were removed Borland's Key Reader would not function. Indeed, Borland's Chief Executive Officer stated at a deposition in May 1991 that Quattro Pro would not be macro compatible with Lotus 1-2-3 if the 1-2-3 compatible menu tree were removed. See I:13 at 52. Thus, claims against the emulation interface might then have appeared to protect Lotus fully, without the added cost of asserting separate claims against Key Reader.

Second, before Quattro Pro 4.01 was released, Lotus was pursuing its strongest claims against all of Borland's existing spreadsheet products, i.e., claims based on the emulation interface. In the circumstances of this case, I cannot say that Lotus was required to assert claims against each feature that Borland added to its (already) infringing products or be faced with the prospect of losing the right ever to assert claims against a program containing that feature. Until the emulation interface was removed, Lotus was not faced with a product that would not be found infringing without a determination that Key Reader infringes. I conclude that it was reasonable to wait to assert claims against Key Reader until resolution of this dispute was necessary and could be raised explicitly as a live issue.

Third, to the extent Lotus was expressly pursuing claims against macro execution as performed by Borland's emulation interface, i.e., on-the-fly macro interpretation by reference to Lotus's menu structure (see VII:B.1, quoted supra), Lotus was pursuing claims against something very similar to Key Reader.

Considering these factors, I find that Lotus's failure to bring an action specifically directed at Key Reader for the time period from the incorporation of Key Reader in Quattro Pro 2.0 until release of Quattro Pro 4.01 was both reasonable and excusable because of Lotus's pursuit of infringement claims against the emulation interface in each of Borland's then existing products.

Next, I consider whether Lotus's delay in filing suit after Quattro Pro 4.01 was released was unreasonable or inexcusable. Quattro Pro 4.01 was released after the Borland II decision was issued on July 31, 1992. Lotus filed its motion for leave to file supplemental complaint approximately four months after Quattro Pro 4.01 was made public. A few months before Quattro Pro 4.01 was released, Lotus gave notice of an intent to preserve claims against Key Reader (in April 1992, see VIII:A.5). Borland acknowledged this notice. (See VIII:A.2.) I also note the propriety of taking some time to investigate how Key Reader works before filing a complaint. In light of the brevity of the time period, the nature of investigation of Key Reader that was reasonably required, and Lotus's earlier notice of its intent to preserve claims against Key Reader, I find that Lotus did not unreasonably or inexcusably delay in bringing an action specifically directed at Key Reader.

Further, I reject Borland's contention that the motion to supplement the complaint was filed so late in the proceedings on the original complaint that Lotus's delay was unreasonable. It was the late (and secretive) timing of the release of Quattro Pro 4.01 that resulted in the late timing of Lotus's claims. Moreover, Lotus agreed to a short time schedule for preparing and presenting its claims for both of the first two Phases of the trial. Accordingly, I find that Lotus's delay in filing claims against Key Reader was reasonable and excusable, despite the advanced stage of proceedings under the original complaint.

2. Prejudice.

As an example of alleged prejudice caused by Lotus's delay in bringing suit, Borland contends that an appeal of copyrightability issues to the First Circuit has been delayed. To make this claim, Borland contends that it removed the emulation interface (but not the Key Reader) in order to expedite an appeal to the First Circuit. The record is barren of evidence to support what counsel contends was Borland's motive for removing the emulation interface.

In addition, even assuming arguendo that this unsupported assertion is true, I find that Borland has not proved prejudice. For the reasons explained on the record at the September 23, 1992 conference, I denied Borland's motion for interlocutory appeal. This was before Lotus moved for leave to include claims against Key Reader in this case. Thus, before Lotus filed its motion for leave to supplement, I had already concluded that an interlocutory appeal was not appropriate. Borland has not demonstrated that it could have secured an interlocutory appeal of the summary judgment decision, even if Lotus never asserted claims against Key Reader.

To demonstrate prejudice, Borland also points to costs in developing and advertising Key Reader. Even assuming these costs were appreciable, a finding that Borland provides little evidence to support, I find that these costs were not incurred as a result of any delay by Lotus. Of course, Lotus had not delayed at all in bringing suit before Key Reader was introduced into a Borland product. In any event, as to Quattro Pro 2.0, 3.0, and 4.0, these products have been found to infringe whether or not Key Reader was present. Borland points to no costs with respect to versions 2.0, 3.0, and 4.0 that might have been avoided had Lotus asserted infringement claims directed at Key Reader earlier. Moreover, Borland did not remove the emulation interface from Quattro Pro 2.0, 3.0, or 4.0, all released after Lotus had filed the complaint in this action. I find that Borland would have included Key Reader along with the emulation interface in its products whether or not Lotus immediately asserted that Key Reader infringes.

With respect to Quattro Pro 4.01 and later releases, Borland released these programs months after Lotus had sent a message (that Borland had acknowledged) that Lotus was seeking to preserve claims against programs containing Key Reader. (See discussion in preceding section.) I conclude that any prejudice suffered by Borland's inclusion of Key Reader in Quattro Pro 4.01 and later releases was not caused by delay on Lotus's part.

C. Estoppel.

As was true with respect to the estoppel claims in Phase I, the parties apparently agree that to establish a defense of estoppel in relation to Phase II issues, Borland must prove that Lotus engaged in (1) conduct that induced Borland to change its position in good faith, or (2) conduct on which a reasonable person would rely. As I did in the Phase I Opinion, again without endorsing this specific formulation of the standard for deciding a claim of estoppel, I proceed, to Borland's advantage, to apply the standard stated by the parties.

In determining whether Borland has proved reasonable reliance on any conduct by Lotus, I consider first Borland's inclusion of Key Reader in Quattro Pro versions 2.0, 3.0, and 4.0, then turn to inclusion of Key Reader in Quattro Pro 4.01 and later releases.

Versions 2.0, 3.0, and 4.0 were released after Lotus filed suit claiming that Quattro and Quattro Pro infringe. Nevertheless, Borland included the emulation interface in each of these products. Accordingly I find that, even if Lotus had clearly and unequivocally stated an intention to assert claims against something like Key Reader, Borland would have included Key Reader in these products anyway. Borland did not rely on any statement by Lotus in developing Key Reader.

For the following reasons, I also find that Borland has not proved that a reasonable person would have relied on any conduct by Lotus in developing or advertising Key Reader in versions 2.0, 3.0, and 4.0.

Borland contends first that it relied on Lotus's original complaint, ¶¶ 17-19, to conclude that Lotus would never assert claims against a program that copied Lotus's menu structure within the computer code but did not display the Lotus menu structure on the screen. This contention is without merit. The complaint alleged claims against products that did not have a Key Reader. The complaint focused on the emulation "user interface" because that is precisely the portion of the programs (in existence at the time the complaint was drafted), both as displayed on the screen and as implemented by the computer code, that infringes. In any event, without Borland's computer code, there is no Borland emulation interface. The complaint cannot be read in any way other than as asserting claims for infringement based on Borland's computer code. Finally, the premise to Borland's argument, that Lotus knew or should have known enough about the computer coding of Quattro and Quattro Pro to make specific allegations in the complaint about the computer code is without support in the record. Borland's claim that it reasonably relied on the original complaint as demonstrating an intention by Lotus to pursue infringement claims based only on Borland's display of the interface and not on Borland's code is baseless.

Borland next cites three statements, made after Key Reader was first released in Quattro Pro 2.0, by Lotus executives or counsel. These three statements are the same statements that Borland cited in its waiver argument, i.e., (1) the admission, (2) the statement at the June 1991 conference, and (3) a footnote in one of Lotus's briefs. For the reasons explained in Section III.A, supra, I conclude that Borland could not reasonably rely on any of these statements as demonstrating an intent not to pursue claims against Key Reader. Moreover, to the extent that the statements and the definition of macro "translation" are ambiguous, reliance on those statements would be unreasonable. A reasonable person or company in Borland's position would have sought clarification before relying on the statements as a position adopted by Lotus.

In addition, each of these statements was made after Key Reader was introduced into Quattro Pro 2.0. Borland, when originally developing and introducing Key Reader, could not have relied on statements made later, after Key Reader had been developed. Nevertheless, Borland contends that it relied on these statements in retaining Key Reader in Quattro Pro 4.01 and later releases. As explained above, however, in April 1992, Lotus clearly stated (and Borland acknowledged) that Lotus wished to preserve claims against Key Reader. In light of this, I find that for Quattro Pro 4.01 and later releases, Borland could not have reasonably relied on the cited statements as demonstrating an intent by Lotus not to assert claims against Key Reader.

Finally, Borland's General Counsel avers that, when recommending to keep Key Reader in the program, he relied "most directly" on the court's language in the Borland II summary judgment opinion. See VI:9, ¶¶ 13-14. First, for the reasons explained in Section II.C.2, I find that Borland's selective reading of the opinion and twisted interpretation of the court's language is unreasonable; reliance on this language, therefore, also would be unreasonable. Second, I am not aware of any precedent for basing an estoppel defense not on conduct of the party alleged to be estopped, but on conduct of the court. Borland offers no authority to support this proposition. Instead, Borland contends that the court's language reflects Lotus's arguments. I reject this contention. To support such a contention, Borland would have to place in evidence Lotus's arguments and conduct, rather than simply pointing to the court's decision. I have examined the language Borland points to in Lotus's earlier briefs and argument and reject Borland's contention that Borland reasonably relied on Lotus's statements or conduct.

In any event, to the extent Borland relied on the court's language in deciding to include Key Reader in Quattro Pro 4.01, Borland was not relying on Lotus's conduct.

Having considered the several instances of conduct cited by Borland both individually and as a whole, including any delay in filing suit, I find that Borland has not proved its estoppel defense.

D. Fair Use.

Borland contends that copying of the Lotus menu structure and first letters of the menu commands is a fair use of Lotus's copyrighted programs. The fair use doctrine is an "equitable rule of reason." Sony Corp. of Am. v. Universal City Studios, Inc., 464 U.S. 417, 448, 104 S. Ct. 774, 792, 78 L. Ed. 2d 574 (1984) (quoting legislative history). The doctrine

permits courts to avoid rigid application of the copyright statute when, on occasion, it would stifle the very creativity which that law is designed to foster.

Stewart v. Abend, 495 U.S. 207, 236, 110 S. Ct. 1750, 1768, 109 L. Ed. 2d 184 (1990) (quoting Iowa State University Research Found., Inc. v. American Broadcasting Cos., 621 F.2d 57, 60 (2d Cir.1980)).

Congress set forth four statutory factors to guide consideration of what constitutes a fair use. Section 107 of the Copyright Act provides that:

the fair use of a copyrighted work ... for purposes such as criticism, comment, news reporting, teaching ..., scholarship, or research, is not an infringement of copyright. In determining whether the use made of a work in any particular case is a fair use the factors to be considered shall include —

(1) the purpose and character of the use, including whether such use is of a commercial nature or is for nonprofit educational purposes;

(2) the nature of the copyrighted work;

(3) the amount and substantiality of the portion used in relation to the copyrighted work as a whole; and

(4) the effect of the use upon the potential market for or value of the copyrighted work.

17 U.S.C. § 107. These factors are not exclusive. Each case is to be decided on its own facts. See Harper & Row, Publishers, Inc. v. Nation Enters., 471 U.S. 539, 560, 105 S. Ct. 2218, 2230, 85 L. Ed. 2d 588 (1985).

1. "[P]urpose and character of the use."

The first statutory factor focuses primarily on whether the copied materials are used to secure profit.

The crux of the profit/nonprofit distinction is not whether the sole motive of the use is monetary gain but whether the user stands to profit from exploitation of the copyrighted material without paying the customary price.

Harper & Row, 471 U.S. at 562, 105 S.Ct. at 2231. Section 107(1) contrasts a use that is "of a commercial nature" with a use that is for "nonprofit educational purposes." According to the preamble in section 107, copying for "criticism, comment, news reporting, teaching ..., scholarship, or research" may be closer to being a "nonprofit educational use" than a commercial use.

In the instant case, there can be little dispute that Borland copied from Lotus for "commercial" purposes. Borland sells its spreadsheet products for profit. The Key Reader is included to make the program more attractive to potential customers that have Lotus 1-2-3 macros. Borland has copied Lotus's menu structure in order to enhance profits from sales of its spreadsheet products, without having secured a license to do so.

Borland tries to minimize the impact of having a profit motive on its fair use defense by contending that Key Reader is actually used by consumers and only for interpreting the macros that the consumers have written. (Docket 345 at 19.) The consumer's use of the part of Quattro Pro that Borland copied from Lotus, however, does not change the character of Borland's use of the copied materials — to please consumers and increase sales. To contend that copying is closer to a fair use because customers want the copied materials is entirely without merit. "It is fundamentally at odds with the scheme of copyright to accord lesser rights in those works that are of the greatest importance to the public." Harper & Row, 471 U.S. at 559, 105 S.Ct. at 2230.

Borland nevertheless contends that the present case is "almost identical" to Lewis Galoob Toys, Inc. v. Nintendo of Am., Inc., 964 F.2d 965 (9th Cir.1992), cert. denied, ___ U.S. ___, 113 S. Ct. 1582, 123 L. Ed. 2d 149 (1993). In Galoob, the alleged infringer sold a product (the "Game Genie") that allowed private users of Nintendo's copyrighted games to use Nintendo's games in an enhanced fashion. Nintendo did not argue that the Game Genie directly infringes Nintendo's copyright. Rather, Nintendo argued that use of the Game Genie with a Nintendo game creates a derivative work of the copyrighted Nintendo game. See id. at 970. Thus, Nintendo's infringement claims concerned only whether Galoob contributed to a consumer's direct infringement of Nintendo's copyright when the consumer used the Game Genie with a Nintendo game at home. For this reason, the opinion concerning fair use explicitly restricted its focus to whether a consumer's private use of the Game Genie was a fair use (and not on Galoob's use of the Game Genie — sale to the consumer for profit). Id. Private use by a consumer is a nonprofit use rather than a commercial use. See id. See also Sony Corp., 464 U.S. at 449, 104 S.Ct. at 792.

The present case is readily distinguished from Galoob. Lotus contends and I have found that Borland copied and that the Quattro Pro products, including Key Reader, directly infringe Lotus's copyright. The fair use issues in this case properly focus on Borland's use (and not the consumer's use) of the infringing products. Otherwise, a book store could copy and sell "Gone With the Wind" without permission. The book store would rely on the consumer's private use of the copied material to claim that its copying is a fair use.

Borland cites Sega Enters. Ltd. v. Accolade, Inc., 977 F.2d 1510, 1522 (9th Cir.1992) for the proposition that "the commercial nature of a use is a matter of degree, not an absolute." In finding that the commercial nature of the defendant's use in Sega was of a lesser degree, the Ninth Circuit relied on the fact that the copied materials were not included in defendant's final product. Id. Here, however, what Borland copied from Lotus is included in the product it sells to the public.

Borland also relies on Sega to argue that Borland has performed its own creative work in developing Quattro Pro, and therefore, Key Reader merely "supplements" Borland's own creative work. Assuming this to be true does not change the character of Borland's commercial use of the copied material. Most of Borland's own creative work, including its own menu structure, exists in Borland's programs independently of whether or not Borland includes a Key Reader in its product. Borland used the copied materials to please customers and increase sales, independently of the creative work it did. In addition, the Sega case is readily distinguished. Sega involved "intermediate" copying; the defendant did not include copied materials in the final product. 977 F.2d at 1522. Here, Borland "supplemented" the product it sells to consumers with a facility including the impermissibly copied materials.

In sum, I find that the "purpose and character" of Borland's use of Key Reader is entirely commercial. This conclusion concerns just a single factor among a number of factors a court weighs in deciding a fair use defense. Nevertheless, when a defendant's use of copied materials is determined to be commercial, that use is "presumptively an unfair exploitation of the monopoly privilege that belongs to the owner of the copyright." Abend, 495 U.S. at 237, 110 S.Ct. at 1768 (quoting Sony Corp., 464 U.S. at 451, 104 S.Ct. at 793). See also Harper & Row, 471 U.S. at 562, 105 S.Ct. at 2231.

2. "[T]he nature of the copyrighted work."

This statutory factor focuses on locating a work, according to its nature, on the spectrum from factual works to fiction or fantasy. "The law generally recognizes a greater need to disseminate factual works than works of fiction or fantasy." Harper & Row, 471 U.S. at 563, 105 S.Ct. at 2232. Similarly, a work largely dictated by functional considerations is closer to the "factual works" end of the spectrum than the fiction end. See Sega, 977 F.2d at 1524.

Also, even for factual works,

there are gradations as to the relative proportion of fact and fantasy. One may move from sparsely embellished maps and directories to elegantly written biography. The extent to which one must permit expressive language to be copied, in order to assure dissemination of the underlying facts, will thus vary from case to case.

Harper & Row, 471 U.S. at 563, 105 S.Ct. at 2232 (quoting Gorman, Fact or Fancy? The Implications for Copyright, 29 J. Copyright Soc. 560, 561 (1982)). Thus, weighing this factor requires a determination of how much freedom of expression the author had in formulating the copyrighted expression. If there was little freedom, the expression is like a bare map. With greater expression found in the work, the scope of copyright protection is greater and a finding of fair use less likely.

For the reasons explained in the Phase I Opinion, I concluded that Lotus had substantial freedom of expression in forming its menu tree. The degree of freedom of expression in creating a menu structure using only first letters of command names is no less than the degree of freedom in designing Lotus's menu tree using full command names. Nevertheless, the menu tree is based on the set of executable operations selected for Lotus 1-2-3. Accordingly, I find that the copyrighted work in this case is similar to a "factual work," but that copying from the substantial expression found in the menu tree is not remotely necessary for disseminating the underlying executable operations (or "facts"). I find that this factor does not weigh significantly in either party's favor.

Borland contends that the "utilitarian nature" of the menu tree weighs in favor of a finding of fair use. Lotus's copyright does not, however, extend to aspects of the program that are utilitarian or functional and not expressive. Moreover, Borland's reliance on Sega is misplaced. The Sega court determined that copying of protected expression was necessary in order to gain access to unprotected aspects of the program. For this reason, the Sega court determined that copyright protection for the code in Sega was entitled to a lower degree of protection than other literary works (i.e., less protection against the "intermediate" copying done by the defendant in that case). 977 F.2d at 1526. Here, Borland's copying was not necessary to examine unprotected aspects of Lotus 1-2-3.

3. "[A]mount and substantiality of the portion used in relation to the copyrighted work as a whole."

Borland created a virtually identical copy of the menu structure and first letters of command names from Lotus 1-2-3's menu tree. This necessarily includes copying of the keystroke sequences used by Lotus to access executable commands and Lotus's macro language. For the reasons explained in Section II.D, supra, I find that this is a substantial part of the copyrighted expression in Lotus 1-2-3.

Borland argues that "it is difficult to see how Borland could use even less of 1-2-3." Docket No. 345 at 21-22. The answer to this is simple. Borland could have copied none of Lotus's expression, or (though I do not comment on the permissibility of doing so) less than the complete 1-2-3 menu structure and first letters of command names.

The fact that Borland uses the menu tree structure and first letters of the command names only for macro translation is not significant in evaluating this statutory factor. "[A] taking may not be excused merely because it is insubstantial with respect to the infringing work." Harper & Row, 471 U.S. at 565, 105 S.Ct. at 2233 (original emphasis).

I find that this statutory factor weighs in favor of Lotus.

4. "[T]he effect of the use upon the potential market for or value of the copyrighted work."

The fourth statutory factor focuses on whether "some meaningful likelihood of future harm exists." Sony Corp., 464 U.S. at 451, 104 S.Ct. at 793 (original emphasis). To negate a claim of fair use, a copyright holder may show either "that the particular use is harmful, or that if it should become widespread, it would adversely affect the potential market for the copyrighted work." Id. (holding that, for a noncommercial use, copyright holder must make this showing). "This inquiry must take account not only of harm to the original but also of harm to the market for derivative works." Harper & Row, 471 U.S. at 568, 105 S.Ct. at 2234.

As noted in Section III.D.1, supra, a commercial use of the copied material is presumptively unfair. Thus, "[i]f the intended use is for commercial gain, [the] likelihood [of future harm] may be presumed." Sony Corp., 464 U.S. at 451, 104 S.Ct. at 793.

In the present case, I find that there is a meaningful likelihood that Borland's copying negatively affects the market for and value of Lotus's copyright. Quattro Pro's functionality is largely equivalent to Lotus 1-2-3's functionality. The operations the programs perform on spreadsheets are similar in nature. From this, I infer that many users will not go to the expense of purchasing, maintaining, and updating both the Quattro Pro and Lotus lines of spreadsheet products.

Borland's inclusion of Key Reader caters to users who already own Lotus 1-2-3; i.e., users that have developed macros for use with Lotus 1-2-3. This may directly affect sales of Lotus 1-2-3 programs. For example, a company using Lotus 1-2-3 may decide to shift to use of Quattro Pro rather than purchasing additional copies of Lotus 1-2-3 for new employees. Inclusion of Key Reader may also have an impact on sales of updates to or new releases of Lotus 1-2-3. For example, Key Reader increases the likelihood that a user will shift to Quattro Pro rather than purchase an update to Lotus 1-2-3.

For these reasons, I infer that there is a meaningful likelihood of harm to Lotus (by a negative impact on the market and a decrease in value of Lotus's copyright) stemming from Borland's use of Key Reader.

Borland seeks to rebut this inference with evidence that Lotus's share of the spreadsheet market has remained steady from the time before Borland introduced Key Reader to the present. I reject this argument for the following reasons.

First, this statutory factor includes an examination of what would happen "if [the use] should become widespread." Sony Corp., 464 U.S. at 451, 104 S.Ct. at 793. This is a necessary consideration. Otherwise, a local bookstore would be free under the fair use doctrine to copy and sell a popular book (without license) because the impact on the national market is negligible. Here, if consumers widely purchase Quattro Pro intending to use Key Reader, I find that the market for Lotus 1-2-3 products and value of the Lotus copyright would be diminished.

Second, Borland provides no evidence that maintaining market share is equivalent to having a copyright of undiminished value. A number of factors other than a complete lack of impact on the market for Lotus 1-2-3 may explain a constant market share. For example, pricing of both 1-2-3 and competing products (including cut prices or lack of increase in prices of 1-2-3) may maintain a constant market share. Also, advertising might be increased to maintain market share. The evidence presented by Borland falls far short of supporting an inference that Lotus's market has not been adversely affected.

Third, even if Lotus can maintain a constant market share without increased costs associated with lower prices or higher expenses, this does not demonstrate that the copying found in Key Reader has not diminished Lotus's market share from what it would be if Borland had not copied. Without Borland's copying, Lotus's market share may have increased.

In short, I find that Borland's limited evidence concerning market share is entirely insufficient to demonstrate that Lotus has not been harmed or to rebut the presumption that Borland's commercial use of Key Reader presents a meaningful likelihood that Lotus will be harmed. This statutory factor weighs in favor of Lotus.

5. Other factors.

The statutory list of factors a court may consider in deciding the merits of a fair use defense is not exclusive. As an additional factor, Borland contends that public policy dictates that Borland's use of Key Reader be considered a fair use. Borland argues that permitting Borland to market an "improved" spreadsheet product while maintaining macro compatibility for users of Lotus 1-2-3 stimulates (Borland's) artistic creativity. In essence, Borland contends that, when forming new artistic expressions, Borland should be permitted to tap into the market for existing expression by copying not just the idea but by copying from the expression of the idea. I reject Borland's arguments for the following reasons.

First, this "new" factor is just another argument concerning the "purpose and character" of Borland's use of the copied expression. Thus, I reject Borland's argument for the same reasons that I concluded that Borland's use of the copied materials is commercial. Borland is not entitled to rely on the consumer's private use of the program for execution of macros to claim fair use.

Second, even when barred from copying expression, Borland was and is free to create new expressions of the ideas contained in Lotus 1-2-3. Borland presents no evidence that providing users with macro compatibility, or the ability to execute macros by reference to copies of Lotus's menus, is necessary to permit copying of the ideas found in Lotus 1-2-3. Compare with Sega, discussed supra. Borland has not demonstrated that allowing it to copy Lotus's expression would stimulate creativity more than the general scheme of providing copyright protection for an author's expression.

6. Summary.

Each of the factors to be weighed in deciding whether Borland's copying constitutes a fair use either weighs against a finding of fair use, or is entitled to little or no weight. Considering all factors, I find that Borland's copying is not a fair use of Lotus's copyrighted expression.

IV. Summary.

For the reasons explained above, I find that Borland's Key Reader infringes Lotus's copyrights. Further, I find that (1) Lotus has not waived claims against Key Reader, (2) Lotus is not barred by laches or estoppel from asserting claims against Key Reader, and (3) including expression copied from Lotus 1-2-3 in Borland's Key Reader facility is not a fair use of the protected expression.

Permanent Injunction

For the reasons stated in the July 31, 1992 Memorandum and Order, and for the reasons stated and on the Findings and Conclusions recited in the Opinion of June 30, 1993, as amended August 19, 1993 (the "Phase I Opinion"), and the Opinion of August 12, 1993, as amended August 19, 1993 (the "Phase II Opinion"), it is ORDERED, ADJUDGED, AND DECREED:

1. Defendant Borland International, Incorporated ("Borland") has infringed plaintiff's copyrights in the computer software program "Lotus 1-2-3" by its development, manufacture and sale of: (1) Quattro and Quattro Pro version 1.0, by Borland's inclusion of its "1-2-3 emulation" interface; (2) Quattro Pro versions 2.0, 3.0, and 4.0, by Borland's inclusion of its "1-2-3 emulation" interface and its "Key Reader" facility; and (3) Quattro Pro SE, 4.01 and Quattro Pro for Windows by Borland's inclusion of its "Key Reader" facility.

2. Acting under 17 U.S.C. § 502(a), the court orders that Borland, its officers, agents, servants, employees and attorneys, and all persons in active concert or participation with them, are hereby permanently enjoined from manufacturing, selling, distributing, licensing, or continuing to license for manufacture, sale, distribution or sub-licensing

(i) Quattro, Quattro Pro versions 1.0, 2.0, 3.0, 4.0, SE, 4.01, and all versions of Quattro Pro for Windows that have been or are on the market on this date (August 19, 1993) ("Quattro Pro for Windows"), and

(ii) any work that contains in any portion, component or module thereof, a copy of the Lotus 1-2-3 menu commands and/or menu structure, in any form. Borland may at any time, however, apply to this court for modification of this clause upon a showing of good cause for determining that Borland has developed or proposes to develop a product that is within this clause but for special reasons

(a) the product is not infringing, or

(b) an alternative form of remedy allowing marketing on specified conditions, including payment of royalties, is more appropriate than an injunction.

3. In addition, upon entry of this Permanent Injunction, Borland shall forthwith take all necessary steps to terminate any existing licenses, distribution agreements or other arrangements pursuant to which it has manufactured, sold distributed or licensed any of Quattro, Quattro Pro version 1.0, 2.0, 3.0, 4.0, SE, 4.01 or Quattro Pro for Windows and it shall, at its own expense, on or before August 27, 1993, notify each and every other party to any such license, distribution agreement or other arrangement of the existence and terms of this Permanent Injunction. Borland shall take all reasonable measures necessary to ensure, so far as it can control, that all such manufacturers, distributors and resellers comply with the terms hereof, including reasonable measures to prevent the selling of infringing products, which may include, but does not require, repurchase of products, and which does not include a general recall.