IP Library Granted Patent US 7,821,666
Granted Patent B2
US 7,821,666 · App. 10/326,220 · Granted Oct 26, 2010

Alternative to pre-printed special forms

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,821,666
App. No.
10/326,220
Granted
Oct 26, 2010
Kind
B2
Abstract

A system and method allowing pre-printed forms to print onto plain paper and also for converting a pre-printed form type system into a plain paper system. The pre-printed form is recreated as an electronic template file in PCL (printer control language) including the contents of the pre-printed form (e.g., the pre-printed text, lines, boxes, logos, etc.), combined with a data file from an application and printed to a plain paper printer. Alternatively, the system may migrate the combined file to a database or web server to allow for easy access and searching by multiple-users at remote locations.

Claims (74)

1. A method of printing a pre-printed form on a plain paper printer, comprising:

obtaining, by a computer, a data code file generated by a legacy application, said data code file representing an output of the legacy application in text and blank spaces, wherein the legacy application generates the data code file configured for printing directly onto a preprinted paper form, the data code file comprising a predefined format associated with the legacy application;

identifying, by the computer, a selected one of a plurality of form code files associated with the data code file based on the output of the legacy application represented in the data code file, each one of the plurality of form code files specifying a corresponding one of plural types of forms, each of the plural types of forms comprising at least one of preprinted text, lines, boxes and logos;

merging, by the computer, the data code file generated by the legacy application with the identified form code file to form a merged file, and

sending the merged file for printing using a plain paper printer,

wherein each of said data code file and said identified form code file comprise instructions in a page description language and wherein said merging is implemented by a printer backend program in the computer to create the merged file.

2. The method of claim 1 , wherein the data code file includes an indicator associated with one of a predetermined set of the plurality of form code files.

3. The method of claim 1 , wherein the data code file includes PCL code containing instructions for printing the data on a pre-printed form.

4. The method of claim 1 , further comprising:

transferring the merged file to at least one of another computer, a web server and a database.

5. The method of claim 1 , further comprising:

converting the merged file to a predetermined format.

6. The method of claim 5 , wherein the predetermined format is one of PCL, .tif, .pdf and Postscript.

7. A method of converting a pre-printed form system into a system capable of printing a pre-printed form on a plain paper printer, comprising:

creating a plurality of form code files, each one of the plurality of form code files specifying a corresponding one of plural types of forms, each of the types of forms comprising at least one of preprinted text, lines, boxes and logos; and

creating a script executable on a computer to:

obtain a data code file generated by a legacy application, said data code file representing an output of the legacy application in text and blank spaces, wherein the legacy application is adapted to generate the data code file configured for printing directly onto a pre-printed paper form, the data code file comprising a predefined format associated with the legacy application; and

identify a selected one of a plurality of form code files associated with the data code file based on the output of the legacy application represented in the data code file;

merge the data code file generated by the legacy application with the identified form code file,

wherein each of said data code file and said form code file comprise instructions in a page description language, and wherein said merging is implemented by a printer backend program executable in the computer to create a merged file.

8. The method of claim 7 , wherein the script is executable to transfer the merged file to at least one of another computer, a web server and a database.

9. The method of claim 7 , wherein the data code file includes PCL code containing instructions for printing the data on a pre-printed form.

10. The method of claim 7 , wherein the script is executable to convert the merged file to a predetermined format.

11. The method of claim 10 , wherein the predetermined format is one of PCL, .tif, .pdf and Postscript.

12. A system for printing on a plain paper printer an output of a legacy application programmed to print onto a pre-printed form, comprising:

a computing system comprising a processor and a memory;

a plain paper printer coupled to the computing system;

wherein the memory contains machine programmable code to be executed by the central processing unit, the machine programmable code including instructions to:

obtain a data code file generated by the legacy application, said data code file representing the output of the legacy application in text and blank spaces, wherein the legacy application is adapted to generate the data code file configured for printing directly onto a pre-printed paper form, the data code file comprising a predefined format associated with the legacy application;

identify a selected one of a plurality of form code files associated with the data code file based on the output of the legacy application represented in the data code file, each one of the plurality of form code files specifying a corresponding one of plural types of forms, each of the plural types of forms comprising at least one of preprinted text, lines, boxes and logos;

merge the data code file generated by the legacy application with the identified form code file to form a merged file; and

send the merged file for printing using a plain paper printer;

wherein each of said data code file and said identified form code file comprise instructions in a page description language, and wherein said merging is implemented by an printer backend program in the computing system to create the merged file.

13. The system of claim 12 , wherein the data code file includes an indicator associated with one of a predetermined set of the plurality of form code files.

14. The system of claim 12 , wherein the data code file includes PCL code containing instructions for printing the data on a pre-printed form.

15. The system of claim 12 , wherein the machine programmable code further comprises instructions to:

transfer the merged file to at least one of another computer, a web server and a database.

16. The system of claim 12 , wherein the machine programmable code further comprises instructions to:

convert the merged file to a predetermined format.

17. The system of claim 16 , wherein the predetermined format is one of PCL, .tif, .pdf and Postscript.

18. A method of transferring an output of a legacy application programmed to print to a pre-printed form to a plain paper printer, comprising:

obtaining, by a computer, a data code file generated by the legacy application, said data code file representing the output of the legacy application in text and blank spaces, wherein the legacy application generates the data code file configured for printing directly onto a pre-printed paper form, the data code file comprising a predefined format associated with the legacy application;

identifying, by the computer, a selected one of a plurality of form code files associated with the data code file based on the output of the legacy application represented in the data code file, each one of the plurality of form code files specifying a corresponding one of plural types of forms, each of the types of forms comprising at least one of preprinted text, lines, boxes and logos;

merging, by the computer, the data code file generated by the legacy application with the form code file;

wherein each of said data code file and said form code file comprise instructions in a page description language, and wherein said merging is implemented by a printer backend program to create a merged file, and

transferring the merged file to at least one of another computer, a web server and a database.

19. The method of claim 18 , wherein the data code file includes an indicator associated with one of a predetermined set of the plurality of form code files.

20. The method of claim 18 , wherein the data code file includes PCL containing instructions for printing the data on a pre-printed form.

21. The method of claim 18 , further comprising:

converting the merged file to a predetermined format.

22. The method of claim 21 , wherein the predetermined format is one of PCL, .tif, .pdf and Postscript.

23. The method of claim 18 , further comprising:

printing the merged file using a plain paper printer.

24. A computer readable storage medium having computer readable program code embodied therein, the computer readable program code causing a computer to:

obtain a data code file generated by a legacy application, said data code file representing an output of the legacy application in text and blank spaces, wherein the legacy application is adapted to generate the data code file configured for printing directly onto a pre-printed paper form, the data code file comprising a predefined format associated with the legacy application;

identify a selected one of a plurality of form code files associated with the data code file based on the output of the legacy application represented in the data code file, each one of the plurality of form code files specifying a corresponding one of plural types of forms, each of the plural types of forms comprising at least one of preprinted text, lines, boxes and logos;

merge the data code file generated by the legacy application with the identified form code file to form a merged file; and

send the merged file for printing using a plain paper printer,

wherein each of said data code file and said identified form code file comprise instructions in a page description language, and wherein said merging is implemented by a printer backend program in the computer to create a merged file.

25. The computer readable storage medium of claim 24 , wherein the computer readable program code further causes the computer to:

transfer the merged file to at least one of another computer, a web server and a database.

26. The computer readable storage medium of claim 24 , wherein the computer readable program code further causes the computer to:

convert the merged file to a predetermined format.

27. The computer readable storage medium of claim 26 , wherein the predetermined format is one of PCL, .tif, .pdf and Postscript.

28. The method of claim 1 , wherein identifying the selected one of the plurality of form code files associated with the data code file is based on a layout of the output of the legacy application represented in the data code file.

29. The method of claim 7 , wherein to identify the selected one of the plurality of form code files associated with the data code file is based on a layout of the output of the legacy application represented in the data code file.

30. The system of claim 12 , wherein to identify the selected one of the plurality of form code files associated with the data code file is based on a layout of the output of the legacy application represented in the data code file.

31. The system of claim 18 , wherein identifying the selected one of the plurality of form code files associated with the data code file is based on a layout of the output of the legacy application represented in the data code file.

32. The computer readable storage medium of claim 24 , wherein to identify the selected one of the plurality of form code files associated with the data code file is based on a layout of the output of the legacy application represented in the data code file.

33. The method of claim 1 , wherein merging the data code file generated by the legacy application with the identified form code file comprises merging the data code file generated by the legacy application without redaction of content of the data code file with the identified form code file to form the merged file.

34. The method of claim 7 , wherein merging the data code file generated by the legacy application with the identified form code file comprises merging the data code file generated by the legacy application without redaction of content of the data code file with the identified form code file to form the merged file.

35. The system of claim 12 , wherein merging the data code file generated by the legacy application with the identified form code file comprises merging the data code file generated by the legacy application without redaction of content of the data code file with the identified form code file to form the merged file.

36. The method of claim 18 , wherein merging the data code file generated by the legacy application with the identified form code file comprises merging the data code file generated by the legacy application without redaction of content of the data code file with the identified form code file to form the merged file.

37. The computer readable storage medium of claim 24 , wherein merging the data code file generated by the legacy application with the identified form code file comprises merging the data code file generated by the legacy application without redaction of content of the data code file with the identified form code file to form the merged file.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 25, 2009
From: ELECTRONIC DATA SYSTEMS, LLC
To: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
Reel/Frame 022449/0267 →
CHANGE OF NAME Recorded Mar 24, 2009
From: ELECTRONIC DATA SYSTEMS CORPORATION
To: ELECTRONIC DATA SYSTEMS, LLC
Reel/Frame 022460/0948 →