JP3072770B2 - Information processing device - Google Patents

Description

Description: BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information processing apparatus for sharing character font data via a network.

2. Description of the Related Art In offices, various office tools such as personal computers, office computers, facsimile machines, and word processors are introduced. By linking these devices with personal workstations, information is compounded in a vertical and horizontal structure, and an integrated office system is realized. Its role as an open and transparent communication device is realized.
A network OS is required as a LAN and responding to such needs. This is for realizing distributed processing based on a PC network for the purpose of exchanging information with a host system or a UNIX workstation. Each of the workstations and servers is implemented. In addition, a common protocol is installed for each model, and sharing of data files, connection between different models, and sharing of peripheral devices are easily realized.

[Problems to be Solved by the Invention] However, in the above-described conventional example, since data contents cannot be managed, especially when character data is downloaded,
There were the following disadvantages.

That is, if the desired character data does not exist on its own work station, the user issues a command each time to another work station or server (printer), and The user has to select the most appropriate character data and download the character data to his / her own workstation.

According to the present invention, in an information processing apparatus connectable to a plurality of printing apparatuses, a developing means for developing typeface information to generate characters of the typeface and printing the information Specifying means for specifying typeface information to be output; first determining means for determining whether or not the typeface information of the specified typeface is stored in each connected printing apparatus or its own apparatus; When the determining unit determines that the designated typeface information is not stored in any of the printing apparatus and the printing apparatus, the specified typeface information is stored in another connected information processing apparatus. Second determining means for determining whether there is a device storing the information, developing means for each device determined to store the typeface information designated by the second determining means, With the deployment means of the printing device Third determining means for determining whether or not there is a combination having the same format.
If there is a corresponding combination as a result of the discrimination by the discriminating means, selecting means for selecting one set of the information processing apparatus and the printing apparatus from the combination, By providing control means for controlling the information to be loaded into the selected printing apparatus, it is possible to automatically download appropriate character data.

Embodiment FIG. 1 is a diagram showing an example of a system configuration of the present invention.

In the figure, 1 is a LAN cable connecting a workstation and a printer, 2 to 11 are workstations A to J, respectively, and 12 to 17 are printers A to D, respectively.

Here, the workstations A to D have font managers A to D for developing outline fonts into bitmap fonts, respectively.

Each of the workstations EG has a font manager A for developing an outline font into a bitmap font, and the workstation E has a detailed description which is developed into a bitmap font by the font manager A. Workstation F with outline font data of morning and Gothic fonts
Has outline font data of the Mincho and Gothic fonts which are developed into a bitmap font by the font manager A, and the workstation G has the outline font of the Taiming font which is developed into the bitmap font by the font manager A. Have data.

On the other hand, the workstations H and I have a font manager B for developing an outline font into a bitmap font, and the workstation H is provided with a font that is developed by the font manager B into a bitmap font. The workstation I has Gothic outline font data, and the workstation I has Tai Mincho outline font data which is developed into a bitmap font by the font manager B.

The workstation J has therein a font manager C for developing an outline font into a bitmap font, and a Tai Mincho outline font data developed by the font manager C into a bitmap font.

Further, each of the printers A and B has a font manager A for developing an outline font into a bitmap font, and the printer A includes a Ming typeface and a Gothic font which are developed by the font manager A into a bitmap font. Printer B has outline font data of Mincho and textbooks which are developed into a bitmap font by font manager A, and 14 is developed into a bitmap font by font manager A. Contains outline font data of Taiming dynasty.

Further, the printers D and E have a font manager B for developing outline fonts into bitmap fonts inside. D is a Ming type font and a Gothic font developed by the font manager B into bitmap fonts. It has outline font data and E is
The font manager B has outline font data of Tai Mincho style developed into a bitmap font.

Further, the printer F has therein a font manager E for developing an outline font into a bitmap font and an outline font data of a Tai Mincho style developed by the font manager B into a bitmap font.

FIG. 2 is a block diagram showing a basic configuration of a workstation according to the present invention.

In FIG. 2, reference numeral 201 denotes a CPU, that is, a central processing unit, which controls the entire apparatus, performs arithmetic processing, and the like. Reference numeral 202 denotes a ROM, that is, a read-only memory, which is a storage area for a system startup program, character pattern data, a font manager program, and the like. Here, the character pattern data is stored in a data format suitable for the font manager program. In addition, part or all of such ROM is in the form of a cartridge,
Extensions and changes may be made easily. 203 is R
It is an AM, that is, a random access memory, which is a data storage area with no usage restriction, and is an area where each program and data are loaded and executed for each of various processes.
Reference numeral 204 denotes a KBC, that is, a keyboard control unit, which receives key input data from the KB of 205, that is, a keyboard, and transmits the key input data to the CPU 201. 206 is a CRTC or display control unit, and 207 is a CRT or display device. The CRT 207 receives data from the CRTC 206 and displays it. Reference numeral 209 denotes an external storage device such as an FD or a floppy disk device or an HD or a hard disk device, which stores programs and data, and refers to or loads the data into the RAM as needed when executed. Reference numeral 208 denotes a DKC, that is, a disk control unit, which controls data transmission and the like to the external storage device 209. Reference numeral 201 denotes a system bus, which should serve as a data transmission path between the above-described components.

FIG. 3 is a block diagram showing a basic configuration of the printer according to the present invention.

In FIG. 3, reference numeral 301 denotes a CPU, that is, a central processing unit, which controls the entire apparatus, performs arithmetic processing, and the like. Reference numeral 302 denotes a ROM, that is, a read-only memory, which is a storage area for a system startup program, character pattern data, a font manager program, and the like. At this time, the character pattern data is stored in a data format suitable for the font manager program. This ROM is
It may be built in the main body, or may be removable in the form of a cartridge or the like. 303 is RAM
In other words, it is a random access memory, a data storage area with no usage restrictions, and an area where each program and data are loaded and executed for each of various processes. 30
Reference numeral 5 denotes a PRT, that is, a printer device, and 304, a PRTC, that is, a printer control unit, which controls the PRT 305. A system bus 306 is to be a data transmission path between the above-described components.

In this embodiment, when a certain workstation tries to use certain font data and the font data does not exist on the workstation, the font data is downloaded from another workstation according to a certain rule. .

In the system having the configuration shown in FIG. 1, for example, when the workstation A attempts to display using the Mincho font, the workstation A does not have the font data of the Mincho font. The font data of the Mincho font is loaded from the workstation E, and developed into a bitmap at the workstation A for use.

At this time, if the workstation E is disconnected from the LAN because the power switch is turned off or the like, the Ming type font data is loaded from the workstation F, and the workstation A develops the font data into a bitmap. Used.

Also, when performing display using the square typeface on the workstation A, since the square typeface does not exist in the workstation E but exists only in the workstation F, the font data of the square typeface is loaded from the workstation F. , And is developed into a bitmap at the workstation A and used.

When performing display using both the Mincho and Gothic fonts on workstation A, workstation E
As long as it is connected to N, the font data is loaded from the workstation E and the workstation A develops it into a bitmap and uses it.

In order to perform the above operation, in the present embodiment, LA
Each workstation on N is a workstation connected to or likely to be connected to the LAN,
In addition, information on font data of all printers is stored as a table. As an example, FIG. 4 shows a table of the workstation A in the configuration of FIG. In addition, data relating to oneself may be separately or together possessed in the same format and referred to.

In FIG. 4, the FM type represents the type of the font manager, and the device type is the workstation (WS).
Or a printer (PR).

FIG. 5 is a flowchart when the table shown in FIG. 4 is created. After turning on the power of each workstation and printer, first, in step S501, the search table shown in FIG.
Initialize the cable. Next, in step S502, a file storing all address information of each of the workstations and printers connected to the LAN is loaded from the FD or the like to the memory. In step S503, the process proceeds to step S508 if the following steps S504 to S507 have been completed for all the address information in the file, and to step S504 if there is unprocessed address information. In step S504, one piece of address information is obtained, and the address destination word is obtained.
If the station or the printer is connectable (the system is up), the process proceeds to step S505. Otherwise, the process for this address is terminated, and the process proceeds to step S503 again. In step S505, the information of the own device type, the information of the typeface provided, and the like are transmitted to the device of the address. Then, the process proceeds to step S506 to acquire information on the device type, information on the typeface held by the connection destination, and registers the information in the search table in step S507. Then, the process proceeds to step S503 again. In step S508, another word
Station and waits for a command from the printer. In step S509, if a system end command has been received, go to step S512; otherwise, go to step S512.
Proceed to S510. In step S512, the command transmission source data is deleted from the search table, and the process proceeds to step S508 again. On the other hand, when a command other than the system termination is received in step S509, first, in step S510, the typeface and device information of the other party are registered in the search table. Next, the process proceeds to step S511, where the own device information and typeface information are transmitted to the other party, and the process again proceeds to step S508 to wait for a command.

If there is a possibility that the typeface etc. of the device may change due to the replacement of the cartridge or card, etc., the information on itself shall be updated after the power is turned on and prior to communication with other devices. .

FIG. 6 is a flowchart showing an example of the operation of the present embodiment.

When font data is required at a certain workstation that does not have font data, first, at step S601, it is determined whether there is a workstation having a required type of font by using a search table shown in FIG. Is determined using If there is at least one workstation having the required font data, the process proceeds to step S602. If there is no workstation having the required font data, step S609 is performed.
Proceed to.

In step S602, it is determined whether there is a workstation having a font manager that matches the user among the workstations having the required font data by using the search table in FIG. Steps
In S602, if there is at least one workstation having a matching font manager, the process proceeds to step S603. If there is no workstation having a matching font manager, the process proceeds to step S604.

In step S603, one workstation is selected from one or more workstations having the required font data and the same font manager type, and the flow advances to step S619. The selection method may be that which first appears in the search table of FIG. 4, or that the work with the lowest load in the state of the corresponding workstation is performed.

In step S602, if there is no workstation having a matching font manager among the workstations having the same font type, the process proceeds to step S604.
Here, it is determined whether there is a workstation having font data that can be converted into the data format of its own font manager by checking the font manager type in the search table in FIG. 4 and the conversion between the data formats in FIG. The determination is made using a table indicating the degree. Step S604
If there is one or more workstations having font data whose data format can be converted, the process proceeds to step S605; otherwise, the process proceeds to step S607.

In step S605, one workstation is selected from the one or more workstations obtained in step S604. Subsequently, in step S606, the font data is converted into the data format of the font manager of the workstation requiring the data in the workstation selected in step S605, and the process proceeds to step S619.

On the other hand, if there is no workstation having font data that can be converted into the data format of the desired font manager in step S604, one workstation is selected from one or more workstations whose font data matches in step S607. In step S608, the font data is developed into a bitmap on the workstation selected in step S607, and then step S608 is performed.
Proceed to S618.

If there is no workstation having the required font data in step S601, it is determined in step S609 whether a workstation having a matching font manager exists using the search table in FIG. to decide. In step S609, if there is at least one workstation having a matching font manager, the process proceeds to step S610. If there is no workstation having a matching font manager, the process proceeds to step S612.

In step S610, one or more workstations having font data close to desired data are selected from the workstations having the same font manager. The selection method will be described later with reference to FIGS. 13 to 15. Then, in step S611, one workstation is selected from the workstations selected in step S610.

If there is no workstation having a matching font manager in step S609, step S612
, One or more workstations having font data of a type close to the desired font data are selected. The selection method will be described later with reference to FIGS. 13 to 15. In step S613, it is determined whether there is a workstation having font data that can be converted into the data format of the font manager in the font selected in step S612, by checking the font manager type in the search table in FIG. The determination is made using the table of FIG. 11 which indicates the degree of difficulty in conversion between font data. In step S613, if there is one or more workstations having font data whose data format can be converted, the process proceeds to step S614; otherwise, the process proceeds to step S616.

In step S614, one workstation is selected from the one or more workstations obtained in step S613. In step S615, the font data of the workstation selected in step S614 is converted into a desired font manager data format, and the flow advances to step S619.

In step S613, if there is no workstation having font data that can be converted to the desired font manager data format, in step S616, step S612
One workstation is selected from the one or more workstations selected in. Then, step S617
Then, the font data is developed into a bit map on the workstation selected in step S616.

Next, in step S618, the data that has been bit-mapped in steps S618 and S617 is downloaded to the workstation that has requested the font.

In step S619, the font data selected in step S603 or step S611, or the font data whose data format has been converted in step S606 or step S615, is downloaded to the workstation that has requested the font development. Then, in step S620, the font data downloaded in step S619 is bit-developed on the workstation requesting the data. In step S621, the bitmap data downloaded in step S618 or the data expanded in bitmap in step S620 is displayed, and the process ends.

Here, the operation of the flowchart of FIG. 6 will be described more specifically with reference to the search table of FIG. 4, with the workstation requesting the font in the configuration of FIG.

As an example, consider a case where there is a request to expand the Mincho font from the workstation A (font manager A, no font data).

First, in step S601 in FIG. 6, a workstation having font data of the Mincho font is selected.
Here, the workstation E, the workstation F, and the workstation H are selected. Then, since one or more workstations exist, step S6
Proceed to 02.

In step S602, a workstation whose font manager matches the workstation A is selected from the above workstations. Here, the workstation E and the workstation F are selected.
Subsequently, in step S603, one workstation is selected from the workstations selected in step S602. Here, assuming that the selection method first appears in the search table of FIG.

Then, in step S619, the font data of the Mincho font of the workstation E is downloaded to the workstation A. Next, in step S620, the downloaded font data is bitmap-developed by the font manager A on the workstation A.
In S621, the bitmap-deployed data is displayed, and the process ends.

FIG. 7 is a flowchart showing another example of the operation of the present embodiment. In the example shown in FIG. 6, if there is no font type that matches, the font manager gives priority to the matching type (steps S609 to S610).
This example is different from the example of FIG. 6 in that the priority is given to fonts having similar types.

In the example of FIG. 7, when font data is required at a certain workstation having no font data, first, at step S701, it is determined whether a workstation having the required font type exists. 4th
The determination is made using the search table shown in FIG. If there is at least one workstation having the required font data, the process proceeds to step S702. If there is no workstation having the required font data, the process proceeds to step S702.
Proceed to step S709.

Steps S702 to S708 (processing when there is one or more workstations having the required font data) are exactly the same as steps S602 to S608, and will not be described.

In step S701, if there is no workstation having the required font data, first, in step S709, a workstation having data close to the desired font data is selected. The selection method is
This will be described later with reference to FIGS. 13 and 15. Then, in step S710, it is determined from the workstations obtained in step S709 whether or not a workstation having a matching font manager exists using the search table in FIG. In step S710, if there is at least one workstation having a matching font manager, the process proceeds to step S711. If there is no workstation having a matching font manager, the process proceeds to step S712.

Then, in step S711, one workstation is selected from the workstations selected in step S710, and the process proceeds to step S718.

On the other hand, in step S712, since there is no workstation having the matching font manager, it is determined whether there is a workstation having font data that can be converted into the font format of the font manager of the workstation requiring the font. The determination is made using the font manager type in the search table shown in FIG. 11 and the table shown in FIG. In step S712, if there is one or more workstations having font data whose data format can be converted, the process proceeds to step S713; otherwise, the process proceeds to step S715.

In step S713, one workstation is selected from the one or more workstations obtained in step S712, and in step S714, the font data of the workstation selected in step S713 is converted into a desired font manager data format. Convert and step
Proceed to S718.

In step S715, one workstation is selected from the one or more workstations selected in step S709. Then, in step S716, the font data is developed into a bitmap on the workstation selected in step S715, and the process proceeds to step S717.

Steps S717 to S720 (the process of downloading bit-mapped data or displaying the downloaded data in bit-mapped form) are exactly the same as steps S618 to S621, and will not be described.

Next, another embodiment will be described with reference to the flowchart of FIG.

In this example, when a font is required at a certain workstation, first, in step S810, a check is made to see if there is a workstation whose font manager matches the workstation requesting the font. Perform using a table. If there is at least one matching workstation, the process proceeds to step S802. If there is no matching workstation, the process proceeds to step S805.

In step S802, a check is made using the search table shown in FIG. 4 to determine whether a workstation having font data matching the desired font data exists among the workstations having the desired font manager in step S801. . If there is at least one or more matching workstations, step S803
The process proceeds to step S804 if no matching workstation exists.

Step S803 is a case where there is one or more workstations having a desired font manager and font data, and one of these workstations is selected. The method of selecting from the plurality of workstations may be the one that appears first in the search table of FIG. 4 or the one that is performing the work with the least load in the state of the workstation at that time. good. After finishing step S803, control proceeds to step S815.

Step S804 is a case where there is a workstation with a matching font manager, but none of the workstations with the desired font data exists. The workstation having the closest font data is selected, and the process proceeds to step S815.
This selection method will be described later with reference to FIGS. 13 to 15.

Step S805 is processing in the case where there is no workstation whose font manager matches in step S801, and determines whether there is a workstation having font data in a data format that can be converted to the data format of the desired font manager. , Using the search table of FIG. If there is at least one workstation having font data in a data format that can be converted to the data format of the desired font manager, the process proceeds to step S806. If there is no such workstation, the process proceeds to step S810. move on.

Step S806 is a case where there is no corresponding workstation of the font manager, but there is at least one or more workstations having font data that can be converted into the data format of the desired font manager. It is checked whether any of these workstations has the desired font data. If there is at least one workstation having the desired font data, the process proceeds to step S807, where the desired font data is If does not exist, the process proceeds to step S808.

In step S807, one workstation is selected from at least one or more workstations obtained in step S806. The method of selecting from the plurality of workstations may be the one that appears first in the search table of FIG. 4 or the one that is performing the work with the least load in the state of the workstation at that time. good.

Also, in step S808, there is no workstation whose font manager matches, and there is no workstation having the desired font data, but at least one of the workstations requesting the font This is a case where the data can be converted into the data format of the font manager, and a workstation having a similar type of font data is selected. The selection method will be described later with reference to FIGS. 13 to 15. In step S809, the font data of the workstation selected in step S807 or S808 is converted into a desired font manager data format. Step S810 is a case where there is no workstation matching the font manager, and there is no font data that can be converted into the font manager data format.
In this step, it is checked whether a workstation having the desired font data exists in the fifth step.
The search is performed using the search table shown in the figure. If there is at least one or more workstations having the desired font data, the process proceeds to step S811. If not, the process proceeds to step S812.

In step S811, one workstation is selected from a plurality of workstations having desired font data. The method of selecting from the plurality of workstations may be the one that appears first in the search table of FIG. 4 or the one that is performing the work with the least load in the state of the workstation at that time. good.

Also, step S812 is to convert the data format to the font manager of the workstation that is requesting the font, because there is no workstation with the matching font manager, and there is no workstation with the desired font data. It is not possible. In this step, one of the plurality of workstations having a similar type of font data instead of the desired font data is selected. The selection method will be described later with reference to FIGS. 13 to 15.

In step S813, bitmap development is performed on the workstation selected in step S811 or S812. In step S814, step S8
Download the bitmap-expanded data to the workstation that requested the font in step 13.

On the other hand, in step S815, the font data selected in step S803 or step S804 or the data whose data format has been converted in step S809 is downloaded to the workstation that has requested the font. Then, in step S816, the font data downloaded in step S815 is developed into a bitmap by a desired font manager.

In step S817, the bitmap data downloaded in step S814 or the bitmap expanded data in step S816 is displayed, and the process ends.

Here, the operation of the above-mentioned flowchart of FIG. 8 will be described more specifically with reference to the search table of FIG. 4, with the workstation requesting the font in the configuration of FIG.

As an example, let us consider a case where there is a request to expand the Tai Mincho style from workstation A (font manager A, no font data).

First, in step S801 in FIG. 8, a workstation that matches the font manager of the workstation A is selected. At this time, workstation E,
Workstation F and workstation G are selected. Then, since at least one or more workstations have been selected, the process proceeds to step S802. Step S802
Then, it is checked whether or not the font data requested by the workstation A exists in the workstations. Here, the workstation G is selected. Then, in step S803, one of the workstations selected in step S802 is selected. At this time, since only the workstation G is selected, the workstation G is determined.

Then, in step S815, the workstation G
Is downloaded to the workstation A. Then, in step S816, the font data downloaded on the workstation A is subjected to bit development by the font manager A, and in step S817, the bit-developed data is displayed, and the process ends.

Next, another embodiment will be described with reference to the flowchart of FIG.

In the example shown in FIG. 8, if there is no workstation whose font manager matches, the one that can be converted into a data format that can be handled by the font manager of the workstation requesting the font is given priority (step S8).
01, S805), however, in this example, the difference is that a font having the same font type is prioritized.

In step S901 in FIG. 9, a check is first made as to whether or not there is a workstation having a font manager that matches the font manager of the workstation requesting the font, using the search table in FIG. And if at least one or more workstations and the font manager match, step
The process advances to step S902, and if there is no matching font manager, the process advances to step S905.

Steps S902 to S904 (processing when there is one or more workstations with the same font manager)
Are exactly the same as steps S802 to S804, and will not be described.

Step S905 is a process in the case where there is no workstation matching the font manager in step S901. Checking whether there is a workstation having the requested font data is performed by using the search table in FIG. Do it. If there is at least one workstation having the desired font data, the process proceeds to step S906. If there is no workstation having the desired font data, the process proceeds to step S911.

In step S906, it is determined whether the desired font data of the workstation selected in step S905 includes font data that can be converted to the data format of the font manager of the workstation requesting the font data. This is performed using the search table shown in FIG. If there is at least one font data whose data format can be converted, the process proceeds to step S907. If there is no convertible font data, the process proceeds to step S909.

In step S907, one workstation is selected from the plurality of workstations selected as having the font data whose data format can be converted in step S906. The method of selecting from the plurality of workstations may be the one that appears first in the search table of FIG. 4 or the one that is performing the work with the least load in the state of the workstation at that time. good. Then, in step S908,
In step S907, the selected font data is converted into a desired font manager data format.

On the other hand, in step S909, since it was found that none of the fonts of the same type could be converted into the data format of the desired font manager in step S906, a plurality of workstations having the font data selected in step S905 were found. One workstation is selected from. The method of selecting from the plurality of workstations may be the one that appears first in the search table of FIG. 4 or the one that is performing the work with the least load in the state of the workstation at that time. good. Then, in step S910, bitmap development of the requested font data is performed on the workstation selected in step S909.

Step S911 is a case where there is no matching font manager and there is no workstation having the desired font data, and this is a step S of selecting at least one or more font data to be changed. The selection method will be described later with reference to FIGS. 13 to 15.

In step S912, it is determined whether or not there is font data that can be converted into a desired font manager data format from at least one or more font data selected in step S911. If there is at least one convertible font data, the process proceeds to step S913. If there is no such data, the process proceeds to step S915.

In step S913, one workstation is selected from a plurality of workstations having font data whose data format selected in step S912 can be converted. The selection method from the plurality of workstations may be the one that appears first in the search table in FIG. 4 or the one that is performing the work with the least load in the state of the workstation at that time. good. Then, in step S914, the selected font data is converted into a desired font manager data format.

On the other hand, step S915 is an example in the case where there is no data that can be converted in step S912.
One workstation is selected from a plurality of workstations having the font data selected in step 11. How to select from the multiple workstations,
It may be the one that appears first in the search table of FIG. 4 or the one that is performing the work with the lowest load in the state of the workstation at that time. Then, in step S916, bitmap development is performed on the workstation selected in step S915.

In step S917, the data subjected to the bitmap development in step S910 or step S916 is downloaded to the workstation that has requested the font.

In step S918, the font data selected in step S903 or step S904 and the data converted in data format in step S908 or step S914 are downloaded to the workstation requesting the font. Then, in step S919,
The font data downloaded in step S918 is developed into a bitmap by a desired font manager.

In step S920, the bitmap data downloaded in step S917 or the data expanded in bitmap in step S918 is displayed, and the process ends.

Here, the operation of the flowchart of FIG. 9 will be described more specifically with the workstation that has requested the font in the configuration of FIG.

When there is a request to expand the Mincho font from the workstation D, first, in step S901 in FIG. 9, a workstation whose font manager matches the workstation D is selected. Here, since there is no workstation having a font manager that matches the font manager of the workstation D, the process proceeds to step S905.

In step S905, it is checked whether there is a workstation having the font data of the Mincho font requested by the workstation D, and the corresponding workstation is selected. At this time, workstation E,
Workstation F and workstation H are selected. Since there is one or more matching font data, the process proceeds to step S906.

In step S906, a check is made as to whether there is font data that can be converted into the data format of the font manager of the workstation D, with reference to FIG. At this time, the work station H is selected because only the font manager B can be converted to the font manager D. Then, since there is a workstation having font data that can be converted, the process proceeds to step S907.

In step S907, one workstation is selected from the workstations selected in step S906. However, since only the workstation H is selected in step S906, the workstation H is determined. In step S908, the font data of the font manager B of the workstation H is converted into the data format of the font manager D.

Then, in step S918, the workstation D
Download the converted data to the workstation D and download the downloaded data in step S919.
In the font manager D, bitmap development is performed. Finally, in step S920, the bitmap-deployed data is displayed, and the process ends.

Next, an embodiment in the case of performing printing will be described with reference to the flowchart of FIG.

In step S1001 in FIG. 10, a check is first made to determine whether there is a printer having font data matching the desired font data, using a search table as shown in FIG. If there is at least one printer having the same font data, all the printers are selected, and the process advances to step S1002. If there is no printer matching the font data, the process advances to step S1005.

In step S1002, a check is made using the search table shown in FIG. 4 to determine whether any of the printers whose font data matches in step S1001 has a font manager matching the desired font manager. If there is at least one printer having a matching font manager, the printer having that font manager is selected, and the process advances to step S1004. If there is no printer matching the font manager, the process advances to step S1003.

In step S1003, there is one or more printers having the fonts to be selected up to step S1002, but none of them has a desired font manager. Here, for example, the printer that first appears in the search table of FIG. 4 is selected, and the process proceeds to step S1018.

In step S1004, when there is one or more printers having the fonts and font managers to be selected up to step S1002 and a plurality of printers are candidates, the search table shown in FIG. Is selected first, and the process proceeds to step S1018.

In step S1005, it is checked whether or not the desired font data exists in another workstation by using the search table shown in FIG. 4. If it exists, the process proceeds to step S1007, and if not, the process proceeds to step S1006.

In step S1006, a workstation having font data closest to the desired font data is selected using the search table shown in FIG. How to select the closest font data will be described later.

In step S1007, step S1005 or step S1
It is checked whether there is a printer having a font manager that matches the font manager of the workstation selected in 006. If there is at least one printer, the process proceeds to step S1008. If there is no printer, the process proceeds to step S1012.

In step S1008, steps S1005 and S1007
In a set of a workstation having a desired font selected in the above and a printer having the same font manager as that of the workstation, it is checked whether or not there is one having the same font manager as the print data. If there is the above, the workstation and the printer having the font manager are selected, and the process proceeds to step S1010. If none exists, the process proceeds to step S1009.

In step S1009, one of the selected workstations and printers is selected. The selection method may be the one that appears first in the search table of FIG. 4 or the one that is performing the work with the least load in the state of the workstation at that time. good. Then, the process proceeds to step S1011.

In step S1010, one of the workstations and printers to be selected is selected. The selection method is the one that appears first in the search table in FIG. Alternatively, in the state of the workstation at that time, the work with the lowest load may be performed. And step S101
Proceed to 1.

In step S1011, the font data existing in the selected workstation is downloaded to the printer via the LAN line.

In step S1012, it is checked whether a desired font manager exists in the printer by using the search table shown in FIG. 4. If there is at least one font manager, the printer having that font manager is searched for and the process proceeds to step S1014. The process proceeds to step S1013 if it does not exist.

In step S1013, a printer registered on the table is selected as a default. If this printer cannot be selected, a printer having the same font manager as this printer is selected, and the flow advances to step S1014.

In step S1014, if the font data of the workstation on the search table can be converted into the font data format of the font manager of the desired printer, the process proceeds to step S1015; otherwise, the process proceeds to step S1016.
Proceed to.

In step S1015, the font data on the selected workstation is converted into the data format of the font manager of the printer that performs printing.

In step S1016, the font data is converted into bitmap data on the selected workstation.

In step S1017, the font data converted in step S1015 or the data developed in bitmap in step S1016 is downloaded to the printer.

In step S1018, the print data is printed using the font data incorporated in the printer, the downloaded font data, and the downloaded bitmap, and the process ends.

In the above-described embodiment, one printer is selected from the printers on the network. If you want to use a font that is not available on this printer when is fixed, the font format of this printer's font manager is used in the same way as when displaying with a font that is not on your workstation as described above. It is assumed that another device is selected and font data is downloaded from the selected device to this printer.

FIG. 11 is a diagram showing the ease of conversion of the font data format.

In the drawing, the cubic Bezier is font data represented by a cubic Bezier curve + straight line, the straight line is font data represented by only a straight line, and the tertiary B spline is font data represented by a cubic B spline curve + straight line. , Secondary Bezier is secondary Bezier + font data represented by a straight line, and arc is arc +
The font data represented by straight lines are respectively represented, and A to E
Is the type of the font manager corresponding to each data format.

This figure shows the ease of conversion from row-direction items to column-direction items, where ◎ indicates that conversion can be performed without losing the accuracy of the original data, and X indicates that data can be converted by approximation, and x indicates data that cannot be converted or cannot be easily converted due to a large load.

Next, a method of converting one font to another font will be described with an example. FIG. 12 shows an example of converting a Bezier curve into a straight line.

In FIG. 12, 1200 is a Bezier curve to be displayed, and 1201 is an end point which is the starting point of the curve, 1202, 12
03 is an intermediate point, and 1204 is an end point which is an end point of the curve.

Bezier curve 1200 has end point 1201, midpoint 1202, midpoint 120
3, using the end point 1204, is represented by the following equation. That is, assuming that the end point 1201 (X ₀ , Y ₀ ), the intermediate point 1202 (X ₁ , Y ₁ ), the intermediate point 1203 (X ₂ , Y ₂ ), and the end point 1204 (X ₃ , Y ₃ ), the Bezier curve 1900 becomes X ( ^{_{t) = X 0 t 3 +}} X 1 t 2 (1-t) + X 2 t (1-t) 2 + X 3 (1-t) 3 Y (t) = Y 0 t 3 + Y 1 t 2 (1-t ) + Y ₂ t (1-t) ² + Y ₃ (1-t) ³ t = 0 → 1

 Next, the Bezier curve represented by this equation is converted into a straight line.

In FIG. 12, 1205 is the midpoint between the end point 1201 and the intermediate point 1202,
06 is the midpoint between midpoints 1202 and 1203, 1207 is the midpoint
It is the middle point between 1203 and 1204. In addition, 1208 is 1205 and 12
The midpoint of 06, 1209, is the midpoint between 1206 and 1207. And
1210 is the midpoint between 1208 and 1209. When approximating a Bezier curve 1200 to a straight line, points 1201, 1205, 1208, 1209, and points
By drawing a straight line connecting 1207 and point 1204, it is possible to draw an approximate straight line. Point 1210 is on the line connecting point 1208 and point 1209. Point 120 when you want to further refine the approximation
A finer approximation is performed by approximating a Bezier curve with four points 1, 1, 1205, 1208, and 1210 and a Bezier curve with four points 1210, 1209, 1207, and 1204, respectively. be able to. Thus, the Bezier curve can be expressed recursively, and it is easy to approximate it to a straight line.

Using this conversion formula, font data represented by a straight line and a Bezier curve can be converted to font data represented only by a straight line.

Next, a method of selecting a font will be described with reference to the flowchart of FIG.

In step S1301 in FIG. 13, first, a selection is made as to whether the typeface selection method is automatic or performed by the user by himself / herself. If you select manual, step
The process advances to step S1302; otherwise, the process advances to step S1304.

In step S1302, all the font names existing in the search table shown in FIG. 4 are displayed, the user selects one of the fonts displayed in step S1303, and the process ends.

On the other hand, in step S1304, a file in which family information is registered is loaded into the memory. Referring to the family information loaded in step S1305,
If a family exists in the desired typeface, step S1306
If not, the process advances to step S1309.

In step S1306, a family search table as shown in FIG. 14 is created from the search table and family information shown in FIG.

In step S1307, if there is a device having the typeface in at least one typeface in the family search table, the process proceeds to step S1308; otherwise, the process proceeds to step S1309.

In step S1308, the typeface with the closest weight is selected using the family search table shown in FIG. that time,
The weight may be small or large.

In step S1309, a file in which friend information is registered is loaded. Subsequently, in step S1310, the loaded friend information is referred to, and if a friend exists in the desired typeface, the flow proceeds to step S1311; otherwise, the flow proceeds to step S1314.

In step S1311, a friend search table as shown in FIG. 15 is created from the search table in FIG. 4 and the loaded friend information. In step S1311, if at least one typeface is present in the friend search table, the process proceeds to step S1312; otherwise, the process proceeds to step S1314.

In step S1312, a typeface is selected using the friend search table shown in FIG. The selection method at this time may be the first typeface appearing in the friend search table in FIG. 15, or the work station performing the work with the least load in the state of the work station at that time. −
It may be an alternative typeface.

In step S1314, a check is performed to determine whether or not font data exists in the user's own work station using the search table shown in FIG. If at least one typeface exists in the user, step S131
Proceed to 5; otherwise, proceed to step S1316.

In step S1315, a font is selected using the search table shown in FIG. The selection method at that time may be a typeface in the user who first appears in the search table of FIG. 4 or a typeface in the user who appears last.

In step S1316, a typeface is selected from the entire system using the search table shown in FIG. The selection method at this time may be the first typeface appearing in the search table in FIG. 4, or the work station performing the work with the least load in the state of the work station at that time. It may be an alternative typeface.

 This completes the font selection process.

[Effects of the Invention] As described above, according to the present invention, when information is output, if the own device does not have a desired typeface, an optimum typeface is automatically selected from the typefaces of other devices in the network. It is possible to select and load and select and output.

[Brief description of the drawings]

FIG. 1 is a diagram showing a system configuration example of the present invention, FIG. 2 is a block configuration diagram of a workstation of the embodiment, FIG. 3 is a block configuration diagram of a printer of the embodiment, FIG. FIG. 5 is a flowchart showing an example of a table, FIG. 5 is a flowchart of a process for creating a retrieval table, and FIGS. 6 to 10 are flowcharts of an output process when there is no desired font. FIG. 11 is a diagram showing the ease of conversion between fonts, FIG. 12 is a diagram illustrating a method of converting a Bezier curve into a straight line, and FIG. 13 is a flowchart showing a font type selection procedure. FIG. 14 is a diagram showing an example of a family table, and FIG. 15 is a diagram showing an example of a friend table. 1 LAN cable 2-11 Workstation 12-17 Printer 201, 301 CPU 202, 302 ROM 203, 303 RAM 204 KBC 205 KB 206 CRTC 207 CRT 208 DCK 209 External storage 210, 306 Bus 304 PRTC 305 PRT

Claims (4)

(57) [Claims] 1. An information processing apparatus connectable to a plurality of printing apparatuses, comprising: a developing means for developing typeface information to generate characters of the typeface; and a specification for designating typeface information for printing out the information. Means, first determining means for determining whether or not the typeface information of the specified typeface is stored in each connected printing apparatus or its own apparatus; and the typeface specified by the first determining means. When it is determined that the information is not stored in either the own device or each of the printing devices, is there a device that stores the specified typeface information among other connected information processing devices? And a developing unit of each device determined to store the typeface information designated by the second determining unit, and a developing unit of each printing device. Determine if there is a matching combination A third discriminating means for performing, if a result of the discrimination by the third discriminating means, a corresponding combination exists, a selecting means for selecting one information processing apparatus and a printing apparatus from the combination; A control unit for controlling the font information of the information processing apparatus selected by the selection unit to be loaded into the selected printing apparatus. 2. An information processing apparatus according to claim 1, wherein said first determining means includes means for storing typeface information stored in each connected printing apparatus. 3. The information processing apparatus according to claim 1, wherein said second discriminating means includes means for storing typeface information stored in each of the connected information processing apparatuses. 4. The apparatus according to claim 1, wherein said third determining means includes means for storing a format of a developing means provided in each connected information processing apparatus and printing apparatus.
Item.