JPH09288662A - Device and method for managing font data - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a device and a method for managing font data capable of easily changing key information added to the font data. SOLUTION: A CPU(central processing unit) 1 displays a product group list which is the key information for history managing the font data to a CRT (display device) 7. An operator specifies a product group to be updated, corrected, copied or deleted, etc., and a product code and a product name are retrieved from a table stored in an HD(hard disk device) 9b based on a product group ID instructed by the CPU 1 and displayed at the CRT 7. The operator confirms the list, operates a KB(keyboard) 5 and a PD(pointing device) 12 and instructs or inputs the product code and the product name to be updated, corrected, copied or deleted, etc., at needed. Then, an execution button is instructed and inputted by the PD 12 and the table stored in the HD 9b is updated corresponding to instruction contents.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a font data management device and method for history management of font data.

[0002]

2. Description of the Related Art Normally, font data as one unit is about 8000 characters in Japanese and 3 in Western characters.
It consists of about 00 characters. Then, in order to improve the management efficiency of the already created font data, there is a case in which key information is given to a certain group of font data.

[0003]

However, as the development cycle of the product incorporating the font data becomes shorter, the content of the font data is also changed, so that the content of the key information added in the past becomes meaningless. The current situation is that they will end up.

[0004]

SUMMARY OF THE INVENTION The present invention has been made for the purpose of solving the above-mentioned problems. For example, when the font data is changed in history management of the font data, the font is changed. It is an object of the present invention to provide a font data management device and method that can change the key information added to data and achieve the efficiency of data management. For example, the following configuration is provided as a means for achieving the object.

That is, the instruction means for designating the user who uses the key information for history management of the font data and the display means for displaying the key information for the font data held by the user designated by the instruction means are no longer necessary. And a deleting unit for specifying and deleting the key information.

Further, an instruction means for designating a user who uses the key information for history management of font data, a display means for displaying the key information for the font data held by the user designated by the instruction means, and the displayed key It is characterized by having a copying means for designating information and copying it as key information for a specific user.

Furthermore, an instruction means for designating a user who uses the key information for history management of font data, a display means for displaying the key information for the font data held by the user designated by the instruction means, and the instruction means. And changing means for changing the content of the key information for the font data held by the user specified in step 1.

Further, an instruction means for designating a user who uses the key information for history management of font data, a display means for displaying the key information for the font data held by the user designated by the instruction means, and other key information. On the other hand, it has a merging means for merging designated key information for font data held by the user designated by the instructing means.

[0009]

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, an example of an embodiment of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram showing the basic configuration of an example system according to an embodiment of the present invention. The system in the embodiments of the present invention described below may be a workstation or a computer system.

In FIG. 1, reference numeral 1 denotes a CPU (central processing unit), which controls the entire system and performs various arithmetic processes according to a control procedure stored in the ROM 2 or the RAM 3. Reference numeral 2 denotes a ROM (read-only memory), which is a storage area for the system startup program, character patterns, data, and the like. Reference numeral 3 denotes a RAM (random access memory), which is a data storage area with no usage restrictions,
This is an area where each program and data are loaded and executed for each of various processes.

Reference numeral 4 is a keyboard control unit (KBC),
Key input data from the keyboard (KB) 5 or menu instructions or the like from a pointing device (PD) 12 such as a mouse is received and transmitted to the CPU 1. A display control unit (CRTC) 6 controls display on a display device described later. 7 is a display device (CRT), which is a CRTC 6
Receive and display more data.

Reference numeral 9 is a floppy disk device (FD) 9a.
It is an external storage device composed of a hard disk device (HD) 9b, etc., and is also used to store programs and data and refer to or load them into the RAM 3 as needed at the time of execution. 8 is a disk control unit (DK
C), which controls the external storage device 9 and
It controls data transmission to and from the PU 1 and RAM 3.

A printer controller (PRTC) 10 controls the printer device (PRT) 11, and a printer device (PRT) 11 is provided. A system bus 13 serves as a data path between the above-mentioned components.

The system of the present embodiment having the above-mentioned configuration can manage the history of the font data to which the key information used in the printer (PRT) 11, etc. is added, and the font data can be managed when managing the history of the font data. The key information added to the font data can also be changed even when is changed, and the efficiency of data management can be improved.

A data holding format in the font data management system for managing the history of a plurality of font data of the present example having the above configuration will be described below with reference to FIG. In this system, it is managed by two tables shown in FIG. It is also possible to specify one product code for a plurality of font data.

That is, the first table is shown in FIG. 2A. The key information is the "product series ID" indicating the user ID when accessing the system, the "product code" serving as the key information, and the key. It is managed by the table shown in (a) of FIG. 2 which is composed of "product name" and "comment" corresponding to the font data added with.

The second table is shown in FIG.
A table composed of a "product series ID" indicating a user ID when accessing the system, a "product code" serving as key information, a "font ID" for identifying a font, and a "version" for retaining history information. It is managed by.

[Table Deletion Operation] Next, the font data management processing in this example having the above-mentioned tables will be described with reference to FIGS.

FIG. 3 is a flowchart showing a product code deletion process in the font data management process in this example.

The CPU 1 displays a list of product series on the CRT 7. Then, in the case of deleting the product code, first, in step S101, the operator uses the PD 12
By the operation of, the target product series is designated from the list of product series. Next, in step S102, C
The PU 1 retrieves the product code and the product name from the table shown in FIG. 2A stored in the HD 9b based on the instructed product series. Next, in step S103, the product code and product name retrieved in step S102 are displayed on the CRT 7 via the CRTC 6.

Then, in step S104, the operator confirms this display and instructs the product code to be deleted by operating the PD 12. Next, in step S105, the CPU 1 uses the designated product code as a key for H
The data is deleted from the tables shown in FIGS. 2A and 2B stored in D9b.

A specific example of the deleting operation according to the operation guidance screen for the CRT 7 in the above processing will be described with reference to FIG.

In step S105, the CPU 1 displays the product code deletion screen shown in FIG. 4 on the CRT 7 via the CRTC 6, and the product series list is displayed here. From this list, by specifying the product series ID "User 1" on the PD 12,
U1 retrieves the product code and the product name from the table shown in FIG. 2A stored in the HD 9b based on the instructed product series ID, and displays them on the CRT 7 via the CRTC 6.

The operator designates the product code and product name to be deleted from this list by operating the PD 12,
Furthermore, by instructing the execute button on PD12, CP
U1 deletes data from the tables shown in FIGS. 2A and 2B stored in the HD 9b using the designated product code as a key.

The state of the table in which data has been deleted from the tables of (a) and (b) shown in FIG. 2 is shown in FIG.
(B). As shown in (a) and (b) of FIG. 5, it indicates that the data of the product series ID “user 1” and the product code “a101” has been deleted from (a) and (b) of FIG. .

By controlling in this way, the product code and product name can be easily deleted from the table.

[Table Copy Operation] Next, the copy processing of the product code and the like in the font data management processing in this example will be described with reference to FIGS.

FIG. 6 is a flow chart showing an operation procedure in the copy processing of the product code and the like in the font data management processing in this example. In this case, the CPU 1
Displays a list of product series on the CRT 7. When copying the product code, the operation shown in FIG. 6 is performed.

First, in step S201, the operator operates the PD 12 to instruct the copy source product code from the list of product series. Subsequently, in step S202, the CPU 1 sets the HD 9 based on the instructed product series.
The product code and the product name are retrieved from the table shown in FIG.

Then, in step S203, the product code and product name retrieved in step S202 are set to C
It is displayed on the display screen of the CRT 7 via the RTC 6. Next, in step S204, the operator confirms this display and operates the PD 12 to instruct the copy source product code.

Then, in step S205, the operator operates the PD 12 to indicate the product code of the copy destination from the list of product series. Next, in step S206, the CPU 1 of FIG. 2A stored in the HD 9b or the like based on the product series instructed in step S205.
The product code and product name are searched from the table shown in. Next, in step S207, the CPU 1 sets the product code and product name retrieved in step S206 to C.
CRT7 is displayed via RTC6. It should be noted that the product code and the product name do not need to be specified here, since the copy source is directly copied.

Next, in step S208, the CPU 1
2 copies the data in the table shown in FIGS. 2A and 2B with the designated copy source product code as a key to the copy destination product series with the copy destination product code as a key. Then, it is added to the tables of FIGS. 2A and 2B and stored in the HD 9b.

A specific example of the above copying process will be described with reference to FIG. As the copy source list screen, the product series list shown at the left end of FIG. 7 is displayed on the CRT 7 via the CRTC 6. From this list, the operator uses the PD 12 to instruct the product series ID “user 1”, for example. As a result, the CPU 1 retrieves the product code and the product name from the table shown in FIG. 2A stored in the HD 9b based on the instructed product series ID, and displays them on the CRT 7 via the CTRC 6.

The operator designates the product code and the product name to be copied by operating the PD 12 from this list. On the copy destination list screen, the product series list is displayed on the CRT 7 via the CRTC 6. The operator designates a copy destination on the PD 12 from the copy destination list, for example, a product series ID "user 3", and the CPU 1 stores the product series ID in the HD 9b based on the instructed product series ID (a) in FIG. The product code and the product name are retrieved from the table shown in and displayed on the CRT 7 via the CRTC 6.

Further, when the execute button is designated on the PD 12, the CPU 1 uses the designated product code as a key and is stored in the HD 9b or the like (a) and (b) of FIG.
The data in the table shown in FIG. 2 is copied to the product series of the copy destination, the data having the product code of the copy destination as a key is copied, and is added to the tables of FIGS. 2A and 2B.
To be stored.

FIG. 8 shows a state in which data is copied from the table shown in FIG. 2 to "user 3" by the above-mentioned operation, and the data of product series ID "user 1" and product code "a102" is This indicates that the product series ID has been copied to “user 3”.

By controlling in this way, the product code and product name can be easily copied from the table.

[Table Correction Operation] Next, the operation of correcting the product code, product name, etc. of the table in the font data management process of this example will be described with reference to FIGS.

FIG. 9 is a flow chart showing an operation procedure for correcting the product code, the product name, etc. of the table in the font data management processing in this example. CPU1
Displays a list of product series on the CRT 7. Then, when the product code or the like is corrected, the operation shown in FIG. 9 is performed.

First, in step S301, the operator operates the PD 12 to instruct the target product series from the list of product series. Next, in step S302, the CPU 1 sets the HD 9b based on the instructed product series.
The product code and the product name are retrieved from the table shown in FIG. And step S3
In 03, the product code and product name retrieved in step S302 are displayed on the CRT 7 via the CRTC 6.

Next, in step S304, the operator operates the PD 12 to instruct the product code to be corrected. The CPU 1 brings the product code or product name instructed thereby into a state in which it can be corrected. Then, step S3
In 05, the operator corrects the product code or the product name for which the correction is designated by inputting from the KB 5.
In step S306, the CPU 1 executes the instruction in FIG.
The contents of the table shown in (b) are changed and stored in the HD 9b or the like.

A specific example of the above correction process will be described with reference to FIG. On the product code / name correction screen, the product series list shown at the left end of FIG. 10 is displayed on the CRT 7 via the CRTC 6.

From this list, the operator uses the PD 12 to instruct the product series ID "user 1", for example. As a result, the CPU 1 instructs the product series I
Based on D, the product code and the product name are retrieved from the table shown in FIG. 2A stored in the HD 9b.
Then, the search result is displayed on the CRT 7 via the CRTC 6.

The operator confirms this list and confirms the PD
The product code and product name to be corrected are designated by the operation of 12. Then, the product code or the product name is corrected in the correction area by the input from the KB 5. When the correction input is completed, the operator further designates the execute button on the PD 12 to confirm the correction content. CP
When the execute button is instructed to be input by U1, U1 of FIG.
The table of (b) is modified and stored in the HD 9b or the like.

FIG. 11 shows a state in which the data is corrected from the table of FIG. 2, in which the product series ID “user 1” and the product code “a102” data are the product code “a202” and the product name “LBP4”. , Comment “×
"X" indicates that each has been corrected.

By controlling in this way, the product code and product name can be easily corrected from the table.

[Table Merging Operation] The details of the merging process of the product code and the product name in the font data management process of this example will be described with reference to FIGS. 12 to 14.

FIG. 12 is a flow chart showing a merging process procedure of a product code and a product name in the font data management process of this example.

The CPU 1 displays a list of product series on the CRT 7. When merging product codes, first, in step S401, the operator uses the PD 12
By operating, the target product series is specified from the displayed list of product series.

Next, in step S402, the CPU 1
Searches for the product code and the product name from the table shown in FIG. 2A stored in the HD 9b or the like based on the instructed product series. Then, in step S403, the product code and product name retrieved in step S402 are displayed on the display screen of the CRT 7 via the CRTC 6.

Next, in step S404, the operator operates the PD 12 to instruct a plurality of product codes to be merged. The operator continues to step S40
In 5, the product code or product name after merging
Input from KB5.

Next, in step S406, the CPU 1
Merges the data into the tables shown in FIGS. 2A and 2B stored in the HD 9b or the like using the entered product code as a key.

A specific example of the above merge process will be described with reference to FIG. On the product code merge screen, see FIG.
The product series list shown at the left end of is CR via CRTC6.
It is displayed at T7. The operator uses the PD 12 from this list to instruct the product series ID “user 1”, for example.

The CPU 1 retrieves the product code and the product name from the table shown in FIG. 2A stored in the HD 9b based on the instructed product series ID, and then the CRTC.
Display on CRT 7 via 6.

The operator confirms this list and confirms the PD
12 is operated to specify a plurality of product codes and product names to be merged. Next, the merged product code, product name,
Input a comment from KB5. When the above input is completed, the operator instructs the execute button on the PD 12. C
When PU1 detects that the execution button has been input, the PU1 displays the merged contents that have been input by that time.
The tables stored in the HD 9b are stored in the tables of FIGS. 2A and 2B to update the tables stored in the HD 9b.

FIG. 14 shows a state in which data is corrected by merging from the table of FIG. In FIG. 14, the data of the product series ID “user 1”, the product codes “a101” and “a102” is merged with the product code “a103”, the product name “LBP3”, and the comment “xxxxx” and added. It represents what you have done.

By controlling in this way, the product code and the product name can be easily merged from the table.

[Other Embodiments] Incidentally, even when the present invention is applied to a system composed of a plurality of devices (for example, a host computer, an interface device, a reader, a printer, etc.), a device composed of one device ( For example, it may be applied to a copying machine, a facsimile machine, etc.).

An object of the present invention is to provide a storage medium storing a program code of software for realizing the functions of the above-described embodiments to a system or an apparatus, and to provide a computer (or CPU) of the system or apparatus.
And MPU) read and execute the program code stored in the storage medium.

In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiment, and the storage medium storing the program code constitutes the present invention.

As a storage medium for supplying the program code, for example, a floppy disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD
-R, a magnetic tape, a nonvolatile memory card, a ROM, or the like can be used.

When the computer executes the readout program code, not only the functions of the above-described embodiment are realized, but also the OS (Operating System) running on the computer based on the instruction of the program code. ) May perform some or all of the actual processing, and the processing may realize the functions of the above-described embodiments.

Further, after the program code read from the storage medium is written into a memory provided on a function expansion board inserted into the computer or a function expansion unit connected to the computer, based on the instructions of the program code, It goes without saying that the CPU included in the function expansion board or the function expansion unit performs part or all of the actual processing, and the processing realizes the functions of the above-described embodiments.

[0065]

As described above, according to the present invention, the key information added to the font data can be easily changed.

That is, the user who uses the key information is designated by a simple operation, the key information for the font data held by the designated user is displayed, and the unnecessary key information is designated and deleted. You can

It is also possible to specify a user who uses the key information, display the key information for the font data held by the specified user, and copy the key information for the specific user.

It is also possible to specify a user who uses the key information, display the key information for the font data held by the specified user, and change the contents of the specified key information.

Further, the user who uses the key information is designated, the key information for the font data held by the designated user is displayed, and the designated key information is merged with other key information. You can

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of a font data management system according to an example of an embodiment of the present invention.

FIG. 2 is a diagram showing a configuration of a table for managing a product code according to the embodiment of the present invention.

FIG. 3 is a flowchart showing a product code deletion process in the font data management process according to the embodiment of the present invention.

FIG. 4 is a diagram showing a product code deletion screen in font data management processing according to the embodiment of the present invention.

5 is a diagram showing a state of a table in which data is deleted from the table shown in FIG.

FIG. 6 is a flowchart showing a product code copying process in the font data management process according to the embodiment of the present invention.

FIG. 7 is a diagram showing a product code copy processing screen in font data management processing according to the embodiment of the present invention.

FIG. 8 is a diagram showing a state of a table in which data is copied from the table shown in FIG.

FIG. 9 is a flowchart showing a process of correcting a product code, a product name, etc. in the font data management process according to the embodiment of the present invention.

FIG. 10 is a diagram showing a correction screen for a product code, a product name, and the like in the font data management processing according to the embodiment of the present invention.

11 is a diagram showing a state of a table in which data is corrected from the table shown in FIG.

FIG. 12 is a flowchart showing a process of merging a product code and a product name in the font data management process according to the embodiment of the present invention.

FIG. 13 is a diagram showing a merge instruction screen for a product code, a product name, and the like in the font data management processing according to the embodiment of the present invention.

14 is a diagram showing a state of a table in which data is merged from the table shown in FIG.

[Explanation of symbols]

 1 CPU 2 ROM 3 RAM 4 keyboard control unit 5 keyboard 6 display control unit 7 display device 8 disk control unit 9 external storage device 10 printer control unit 11 printer device 12 pointing device

Continuation of the front page (51) Int.Cl. ⁶ Identification code Office reference number FI Technical display location G09G 5/24 640 G09G 5/24 640

Claims (8)

[Claims] 1. An instruction means for designating a user who uses key information for history management of font data, a display means for displaying key information for the font data held by the user designated by the instruction means, is no longer necessary. A font data management device comprising: a deleting unit that specifies and deletes key information. 2. An instruction means for designating a user who uses key information for history management of font data, a display means for displaying key information for the font data held by the user designated by the instruction means, and the displayed key. A font data management device comprising: a copying unit that specifies information and copies it as key information for a specific user. 3. An instruction means for designating a user who uses key information for history management of font data, a display means for displaying key information for font data held by the user designated by said instruction means, and said instruction means. A font data management device comprising: a changing unit for changing the content of key information for font data held by a designated user. 4. An instruction means for designating a user who uses key information for history management of font data, a display means for displaying key information for font data held by the user designated by the instruction means, and other key information. And a merging means for merging designated key information for font data held by the user designated by the instructing means. 5. An instruction step for designating a user who uses key information for history management of font data, and displaying key information for font data held by the user designated in the instruction step to display unnecessary key information. A font data management method, comprising: a deletion step of designating and deleting. 6. An instruction step of designating a user who uses key information for history management of font data, key information for the font data held by the user designated in the instruction step is displayed, and the displayed font data is further designated. And a copying step for copying as key information for a specified user. 7. An instructing step of designating a user who uses key information for history management of font data, displaying key information for font data held by the user designated in the instructing step, and displaying the designated user And a change step of changing the content of the key information for the font data held by the font data management method. 8. An instructing step of designating a user who uses key information for history management of font data, displaying key information for font data held by the user designated in the instructing step, and displaying other key information. And a merging step of merging designated key information for the font data held by the user designated in the instructing step.