JP3554150B2 - Font management apparatus, font management method, and storage medium - Google Patents

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a font management device, a font management method, and a storage medium, and more particularly, to a font management device and a font management method suitable for managing fonts in, for example, a graphic processing device, a Japanese word processor, an information processing system, and the like. And a storage medium.
[0002]
[Prior art]
For example, in a graphic processing device, a Japanese word processor, an information processing system, and the like, when updating and updating a normal corrected font, all users can refer to the updated version of the character. Therefore, even if the correction is made for a specific user, it can be referred to by other users.
[0003]
[Problems to be solved by the invention]
However, the above-described prior art has the following problems. That is, as described above, in normal update registration of a corrected font, all users can refer to the updated version of the character. For this reason, even if it is a correction for a specific user, since it can be referred to from other users, there is a problem that another user may not be able to obtain an appropriate font.
[0004]
SUMMARY OF THE INVENTION The present invention has been made in view of the above points, and uses a specific user character management table to update and register a corrected font so as to be valid only for a specific user in update registration of a corrected font. It is an object of the present invention to provide a font management device, a font management method, and a storage medium that can be used.
[0005]
[Means for Solving the Problems]
In order to achieve the above object, the invention of claim 1 is , Osamu Instructing means for instructing a specific user to make positive valid, and comparing the characters constituting the latest version of the font with the characters constituting the corrected font to be registered, Whether even one character has been updated Determining means for determining Registration processing means for performing a registration process of a corrected font to be registered when it is determined that at least one character has been updated by the determination means, wherein the registration processing means includes the corrected font to be registered Means for registering a record of a font in a font management table including a font ID and a version. A record of a character constituting a corrected font to be registered is stored in a user, a character, a character revision number, and a version valid for a specific user. Means for registering in a specific user character management table including a valid version indicating a valid version and an invalid version indicating a version that becomes invalid thereafter, and a record of characters constituting a corrected font to be registered, which is a character, a character revision number, and a font management The added version and the deleted version corresponding to the version of the table, and the specific product has been corrected. And means for registering the character history management table including a standard flag that indicates whether the regular modification date And characterized in that:
[0006]
In order to achieve the above object, the invention according to claim 2 is characterized in that the indicating means is , Indicate multiple specific users Ruko And features.
[0008]
Claims to achieve the above object 3 The invention of Executed by the CPU of the font management device A font management method, comprising: an instruction step of instructing a specific user to make a correction effective; comparing a character constituting a latest version of the font with a character constituting a corrected font to be registered; A determination step of determining whether at least one character has been updated; and a registration processing step of performing a registration process of a corrected font to be registered when the determination step determines that at least one character has been updated. The registration processing step includes a step of registering a corrected record of a font to be registered in a font management table including a font ID and a version; Registering in a specific user character management table including a character, a character revision number, a valid version indicating a version valid for a specific user, and an invalid version indicating a version invalid after that; The records of the characters that make up the font are stored in characters, character revision numbers, and the version of the font management table. Step of registering a character history management table including a standard flag indicating an additional version Remove the version corresponding or those identified product corresponding modifications, and whether those of normal corrective latest in And characterized in that:
[0009]
Claims to achieve the above object 4 In the invention, the instruction step is , Indicate multiple specific users Ruko And features.
[0011]
Claims to achieve the above object 5 The invention of On computer , An instruction step of instructing a specific user to make the correction effective, and comparing the characters constituting the latest version of the font with the characters constituting the corrected font to be registered, A determination step of determining whether at least one character has been updated; and a registration processing step of performing a registration process of a corrected font to be registered when the determination step determines that at least one character has been updated. A computer-readable storage medium storing a program to be executed, wherein the registration processing step registers a corrected record of a font to be registered in a font management table including a font ID and a version; A specific user including a record of characters constituting a corrected font to be registered, including a user, a character, a character revision number, an effective version indicating a version valid for a specific user, and an invalid version indicating a version invalid thereafter. Registering in the character management table and the phone to be registered Indicate whether the record of the character that constitutes is the added version, the deleted version corresponding to the version of the character, the character revision number, and the font management table, and the version that has been corrected for the specific product, and whether it is the latest version with the normal correction Registering in a character history management table including a standard flag It is characterized by the following.
[0012]
Claims to achieve the above object 6 In the invention, the instruction step is , Indicate multiple specific users Ruko And features.
[0014]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0015]
[1] First Embodiment
First, a basic configuration of the information processing system (font data management device) according to the first embodiment will be described with reference to FIG. The information processing system may be, for example, a Japanese word processor, or a system such as a workstation or a personal computer.
[0016]
The font data management device according to the first embodiment includes a CPU 1, a ROM 2, a RAM 3, a keyboard control unit (KBC) 4, a keyboard (KB) 5, a display control unit (CRTC) 6, a CRT display. The system includes a device (CRT) 7, a disk control unit (DKC) 8, an external storage device 9, a printer control unit (PRTC) 10, a printer device (PRT) 11, and a system bus 12. .
[0017]
More specifically, the CPU 1 is a central processing unit connected to the ROM 2 to the printer (PRT) 11 via the system bus 12 and controls the entire font data management device and performs arithmetic processing. The ROM 2 is a read-only memory, and stores a system startup program, character pattern data for character conversion, and the like. The RAM 3 is a random access memory, and temporarily stores data used for the operation of the CPU 1 and operation results of the CPU 1.
[0018]
The keyboard control unit (KBC) 4 receives key input data (character code or control code) input from the keyboard (KB) 5 and transmits it to the CPU 1. The keyboard (KB) 5 has various keys such as character keys and numeric keys. The display controller (CRTC) 6 reads the display information stored in the RAM 3, that is, the bitmap image converted from the character code, and transfers the read bitmap image to the CRT display device 7. The CRT display device (CRT) 7 receives the bitmap image from the display control unit (CRTC) 6 and displays it on a display screen. Note that the display method is not limited to the CRT, and another display method such as a liquid crystal display may be used.
[0019]
The disk control unit (DKC) 8 controls data transmission and the like of the external storage device 9. The external storage device 9 is configured as a floppy disk device (FD) 9a, a hard disk device (HD) 9b, a CD-ROM (Compact Disc ROM) 9c, or the like. The external storage device 9 stores programs and data, and the CPU 1 refers to the stored data or loads the data into the RAM 3 as necessary. The printer control unit (PRTC) 10 controls the operation of the printer device (PRT). The printer device (PRT) 11 performs a printing operation based on the control of the printer control unit (PRTC) 10. The system bus 12 performs data transfer between the above-described components.
[0020]
FIG. 2 is a diagram showing a memory configuration relating to the processing of the entire information processing system (font data management device) having the above configuration. The font data management device operates by executing an operating system such as a basic I / O program, a window system, and the like, and an application serving as a process of the present invention. The basic I / O program is stored in the ROM 2 of FIG. The operating system is stored in the hard disk device 9b of the external storage device 9 in FIG. When the power of the font data management device is turned on, the operating system is read from the hard disk device 9b into the RAM 3 by the IPL (Initialize Program Loading) function in the basic I / O program, and the operation is started.
[0021]
In FIG. 2, reference numeral 40 denotes a memory map of a basic I / O program, 41 denotes a memory map in which an operating system such as a window system is loaded into the RAM 3 and becomes executable, and 42 denotes a font data management program of the present invention in the RAM 3. A memory map 43 in a loaded and executable state, a memory map 43 in a state in which related data is loaded into the RAM 3 and an executable state, and a memory map 44 of a work memory used by each program.
[0022]
FIG. 3 is a diagram showing the content structure of a recording medium such as a floppy disk device 9a or a CD-ROM 9c in which the font data management program and related data are recorded. The recording medium 50 includes volume information 51, directory information 52, a font data management program execution file 53, and a font data management program related data file 54.
[0023]
FIG. 4 is a conceptual diagram showing that the font data management program and related data can be supplied from a recording medium to an information processing system. 61 denotes a personal computer as an information processing system, 62 denotes a floppy disk drive, and 63 denotes a floppy disk.
[0024]
In FIG. 1, the font data management program and related data are once installed in the hard disk device 9b from the floppy disk device 9a or the CD-ROM 9c, so that they can be loaded from the hard disk device 9b to the RAM 3 and executed. Alternatively, the program can be directly loaded from the floppy disk device 9a or the CD-ROM 9c to the RAM 3 without being installed in the hard disk device 9b and executed.
[0025]
FIG. 7 is a diagram illustrating an example of a registration table related to the font registration process. Reference numeral 71 denotes a "font history management table" for managing the history of each font, which is composed of a font ID and a version (version). Reference numeral 72 denotes a "character history management table" for managing additional information of characters, which is composed of characters, character revision numbers, added versions, deleted versions, and standard flags.
[0026]
The additional version is a number corresponding to the version in the font history management table 71. The deleted version is, in principle, the same number as the character data number relating to the change when the added character is changed, but the latest version is given "0" as the deleted version. The standard flag gives "0" if the character has been corrected for a specific product, "2" if the character is the latest one after normal correction, and "1" otherwise.
[0027]
Reference numeral 73 denotes a “specific user character management table” for managing character information corrected for a specific user, and includes a user, a character, a character revision number, a valid version, and an invalid version. The valid version and the invalid version are given as a version of a font that is valid for a specific user and, if invalid thereafter, the version is given as an invalid version.
[0028]
Next, in the font data management device according to the first embodiment configured as described above, a specific user-corresponding corrected font registration according to a specific example will be described with reference to FIGS. 5, 6, 8, and 9. FIG. I do. FIG. 5 is a flowchart showing a processing procedure executed in the CPU 1 of the font data management device, and FIG. 6 is a flowchart showing details of step S4 in FIG. FIGS. 8A and 8B are diagrams showing specific examples of the font history management table, and show images of characters constituting each font A version. The symbol “↑” shown in the figure means that the same character as in the previous version is retained. FIG. 9 is a diagram showing a specific example of the character history management table and the specific user character management table.
[0029]
In FIG. 5, first, a desired specific user for which the correction is effective is instructed (step S1). In this example, it is assumed that “user1” is designated as the specific user. Next, the characters constituting the latest version of the font are compared with the corrected characters constituting the font to be registered (step S2). As shown in the font history management table of FIG. 8A, in this example, it is assumed that “A”, “I”, “U”,... Of version 2 have been corrected and extracted, and only “A” has been corrected to “A”. I do.
[0030]
The characters to be compared are “A” and “A”, “I” and “I”, “U” and “U”, and so on. Next, it is determined whether at least one character has been updated (step S3). If it is determined that the information has been updated, a registration process described later is performed (step S4). On the other hand, if it is determined that the information has not been updated, the present process ends.
[0031]
The flow of the registration process in step S4 will be described with reference to the flowchart in FIG. In FIG. 6, first, each font is registered in a font history management table for managing the history of each font (step S41). In this example, it is registered as version 3. Next, it is determined whether registration for the updated number of characters has been completed (step S42). If it is determined that the registration has been completed, the registration processing ends. On the other hand, if it is determined that the registration has not been completed, registration in the specific user character management table shown in FIG. 9 (step S43) and registration in the character history management table shown in FIG. 9 (step S44) are performed.
[0032]
In this example, since only “A” has been corrected, the record of the character revision number 2 of “A” in the font history management table of FIG. 8 and the record of “user1 A” in the specific user character management table of FIG. 9 are registered. You. The character of the character “A” revision number 2 has been corrected for “user1”. Actually, characters configured as version 3 of font A are as shown in the font history management table of FIG.
[0033]
As described above, according to the first embodiment, the font data management device instructs a specific user to make correction effective, and specifies the characters constituting the latest version of the font and the corrected font to be registered. Comparing with the constituent characters, it is determined whether at least one character has been updated. If it is determined that the character has been updated, the CPU 1 for updating and registering the font, a font history management table for managing the history of each font, and addition of characters Since it has a character history management table for managing information, a specific user character management table for managing character information corrected for a specific user, and an external storage device 9 storing a font data management program, the specific user character management table is By using it, in the registration of updating the corrected font, the corrected font will be valid only for a specific user. It is possible to new registration.
[0034]
[2] Second embodiment
The font data management device according to the second embodiment includes a CPU 1, a ROM 2, a RAM 3, a keyboard control unit (KBC) 4, a keyboard (KB) 5, A display control unit (CRTC) 6, a CRT display device (CRT) 7, a disk control unit (DKC) 8, an external storage device 9, a printer control unit (PRTC) 10, a printer device (PRT) 11, The configuration includes a system bus 12 (see FIG. 1). These components have been described in detail in the first embodiment, and a description thereof will be omitted.
[0035]
In the second embodiment, the memory configuration (see FIG. 2 above) and the content configuration of a recording medium such as a floppy disk device 9a or a CD-ROM 9c that stores a font data management program and related data (see FIG. 3 above) The concept of supplying the font data management program and related data from the recording medium to the apparatus (see FIG. 4) is also the same as in the first embodiment, and a description thereof will be omitted.
[0036]
Next, in the font data management device according to the second embodiment configured as described above, specific user-specific correction registration when a correction other than the latest version of a font according to the specific example is extracted is shown in FIGS. This will be described with reference to FIGS. FIGS. 10A and 10B are diagrams showing specific examples of the font history management table, and show images of constituent characters of each font A version. The symbol “↑” shown in the figure means that the same character as in the previous version is retained. FIG. 11 is a diagram showing a specific example of the character history management table and the specific user character management table. In FIG. 5, first, a desired specific user for which the correction is effective is instructed (step S1). In this example, it is assumed that “user1” is designated as the specific user. Next, the characters constituting the latest version of the font are compared with the corrected characters constituting the font to be registered (step S2). As shown in the font history management table in FIG. 10A, in this example, “A”, “I”, “U”,... Of version 1 which is not the latest version are corrected and extracted, and only “A” is “A”. Suppose that it was corrected.
[0037]
Since the characters to be compared are the characters of the latest version, “A” and “A”, “I” and “I”, “U” and “U”... Next, it is determined whether at least one character has been updated (step S3). If it is determined that the information has been updated, a registration process described later is performed (step S4). On the other hand, if it is determined that the information has not been updated, the present process ends.
[0038]
The flow of the registration process in step S4 will be described with reference to the flowchart in FIG. In FIG. 6, first, each font is registered in a font history management table for managing the history of each font (step S41). Next, it is determined whether registration for the updated number of characters has been completed (step S42). If it is determined that the registration has been completed, the registration processing ends. On the other hand, if it is determined that the registration has not been completed, registration in the specific user character management table shown in FIG. 11 (step S43) and registration in the character history management table shown in FIG. 11 (step S44) are performed.
[0039]
In this example, since the characters “A” and “I” have been modified, the character history management table shown in FIG. 11 has a character revision number 2 record for “A”, a character revision number 3 record for “I”, and FIG. Two records of "user1 sub" and "user1 well" in the specific user character management table of "1" are registered. The character of the character "A" revision number 2 and the character of the character "I" revision number 3 have been corrected for "user1". In fact, the characters configured as version 3 of font A look like the font history management table in FIG.
[0040]
As described above, according to the second embodiment, the font data management device instructs a specific user to make correction effective, and specifies the characters constituting the latest version of the font and the corrected font to be registered. Comparing with the constituent characters, it is determined whether at least one character has been updated. If it is determined that the character has been updated, the CPU 1 for updating and registering the font, a font history management table for managing the history of each font, and addition of characters Since it has a character history management table for managing information, a specific user character management table for managing character information corrected for a specific user, and an external storage device 9 storing a font data management program, the specific user character management table is By using it, in the registration of updating the corrected font, the corrected font will be valid only for a specific user. It is possible to new registration.
[0041]
[3] Third Embodiment
The font data management device according to the third embodiment includes a CPU 1, a ROM 2, a RAM 3, a keyboard control unit (KBC) 4, a keyboard (KB) 5, A display control unit (CRTC) 6, a CRT display device (CRT) 7, a disk control unit (DKC) 8, an external storage device 9, a printer control unit (PRTC) 10, a printer device (PRT) 11, The configuration includes a system bus 12 (see FIG. 1). These components have been described in detail in the first embodiment, and a description thereof will be omitted.
[0042]
In the third embodiment, the memory configuration (see FIG. 2 above) and the content configuration of a recording medium such as a floppy disk device 9a or a CD-ROM 9c that stores a font data management program and related data (see FIG. 3 above) The concept of supplying the font data management program and related data from the recording medium to the apparatus (see FIG. 4) is also the same as in the first embodiment, and a description thereof will be omitted.
[0043]
Next, in the font data management device according to the third embodiment configured as described above, specific user correspondence correction registration when a plurality of specific users are specified based on a specific example is shown in FIGS. This will be described with reference to FIG. FIG. 12 is a flowchart showing a processing procedure executed in the CPU 1 of the font data management device. FIGS. 13A and 13B are diagrams showing specific examples of the font history management table, and show images of constituent characters of each font A version. The symbol “↑” shown in the figure means that the same character as in the previous version is retained. FIG. 14 is a diagram showing a specific example of the character history management table and the specific user character management table.
[0044]
In FIG. 12, first, a desired specific user for which correction is effective is instructed (step S121). Next, it is determined whether or not the specific user instruction has been completed (step S122). If it is determined that the specific user instruction has been completed, the process from step S123 is performed. If it is determined that the specific user instruction has not been completed, the process returns to step S121 to receive the specific user instruction. In this example, it is assumed that two users “user1” and “user3” are specified as specific users.
[0045]
If it is determined in step S122 that the specific user instruction has been completed, the characters constituting the latest version of the font and the characters constituting the corrected font to be registered are compared (step S123). As shown in the font history management table in FIG. 13A, in this example, the latest version “A”, “I”, “U”,. Suppose that it was corrected.
[0046]
The characters to be compared are “A” and “A”, “I” and “I”, “U” and “U”, and so on. Next, it is determined whether at least one character has been updated (step S124). If it is determined that the information has been updated, a registration process described later is performed (step S125). On the other hand, if it is determined that the information has not been updated, the present process ends.
[0047]
The flow of the registration process in step S125 will be described with reference to the flowchart in FIG. In FIG. 6, first, each font is registered in a font history management table for managing the history of each font (step S41). Next, it is determined whether registration for the updated number of characters has been completed (step S42). If it is determined that the registration has been completed, the registration processing ends. On the other hand, if it is determined that the registration has not been completed, registration in the specific user character management table shown in FIG. 14 (step S43) and registration in the character history management table shown in FIG. 14 (step S44) are performed.
[0048]
In this example, since only "A" was corrected, the record of the character revision number 2 of "A" in the character history management table of FIG. 14 and "user1 A" and "user3 A" of the specific user character management table of FIG. Are registered. The character of the character “A” revision number 2 has been corrected for “user1” and “user3”. In fact, the characters configured as version 3 of font A are as shown in the font history management table in FIG.
[0049]
As described above, according to the third embodiment, the font data management device instructs a specific user to make correction effective, and specifies the characters constituting the latest version of the font and the corrected font to be registered. Comparing with the constituent characters, it is determined whether at least one character has been updated. If it is determined that the character has been updated, the CPU 1 for updating and registering the font, a font history management table for managing the history of each font, and addition of characters A character history management table for managing information, a specific user character management table for managing character information corrected for a specific user, an external storage device 9 storing a font data management program, and a plurality of specific users can be designated. Therefore, by using the specific user character management table, it is The cement only to a specific user can be updated and registered as valid.
[0050]
The present invention may be applied to a system including a plurality of devices or to an apparatus including a single device. A storage medium storing software program codes for realizing the functions of the above-described embodiments is supplied to a system or an apparatus, and a computer (or CPU or MPU) of the system or apparatus executes the program code stored in the storage medium. Needless to say, this can also be achieved by executing reading.
[0051]
In this case, the program code itself read from the storage medium realizes the function of the above-described embodiment, and the storage medium storing the program code constitutes the present invention.
[0052]
As a storage medium for supplying the program code, for example, a floppy disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, a nonvolatile memory card, a ROM, and the like can be used.
[0053]
When the computer executes the readout program code, not only the functions of the above-described embodiments are realized, but also an OS or the like running on the computer executes actual processing based on the instruction of the program code. It goes without saying that a case where some or all of the operations are performed and the functions of the above-described embodiments are realized by the processing is also included.
[0054]
Further, after the program code read from the storage medium is written into a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. It goes without saying that the CPU or the like provided in the 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.
[0055]
【The invention's effect】
As described above, according to the first aspect of the present invention, Repair Instructing means for instructing a specific user to make positive valid, and comparing the characters constituting the latest version of the font with the characters constituting the corrected font to be registered, Whether even one character has been updated Determining means for determining Registration processing means for performing a registration process of a corrected font to be registered when it is determined that at least one character has been updated by the determination means, wherein the registration processing means includes the corrected font to be registered Means for registering a record of a font in a font management table including a font ID and a version. A record of a character constituting a corrected font to be registered is stored in a user, a character, a character revision number, and a version valid for a specific user. Means for registering in a specific user character management table including a valid version indicating a valid version and an invalid version indicating a version that becomes invalid thereafter, and a record of characters constituting a corrected font to be registered, which is a character, a character revision number, and a font management The added version and the deleted version corresponding to the version of the table, and the specific product has been corrected. And means for registering the character history management table including a standard flag that indicates whether the regular modification date Thus, in the update registration of the corrected font, the corrected font can be updated and registered so as to be effective only for a specific user.
[0056]
According to the invention of claim 2, the instruction means is , Indicate multiple specific users Ruta Therefore, the corrected font can be updated and registered so as to be effective only for a plurality of specific users.
[0058]
Claim 3 According to the invention of Executed by the CPU of the font management device A font management method, comprising: an instruction step of instructing a specific user to make a correction effective; comparing a character constituting a latest version of the font with a character constituting a corrected font to be registered; A determination step of determining whether at least one character has been updated; and a registration processing step of performing a registration process of a corrected font to be registered when the determination step determines that at least one character has been updated. The registration processing step includes a step of registering a corrected record of a font to be registered in a font management table including a font ID and a version; Registering in a specific user character management table including a character, a character revision number, a valid version indicating a version valid for a specific user, and an invalid version indicating a version invalid after that; The records of the characters that make up the font are stored in characters, character revision numbers, and the version of the font management table. Step of registering a character history management table including a standard flag indicating an additional version Remove the version corresponding or those identified product corresponding modifications, and whether those of normal corrective latest in Thus, in the update registration of the corrected font, the corrected font can be updated and registered so as to be effective only for a specific user.
[0059]
Claim 4 According to the invention, the instruction step is , Indicate multiple specific users Ruta Therefore, the corrected font can be updated and registered so as to be effective only for a plurality of specific users.
[0061]
Claim 5 According to the invention of On computer , An instruction step of instructing a specific user to make the correction effective, and comparing the characters constituting the latest version of the font with the characters constituting the corrected font to be registered, A determination step of determining whether at least one character has been updated; and a registration processing step of performing a registration process of a corrected font to be registered when the determination step determines that at least one character has been updated. A computer-readable storage medium storing a program to be executed, wherein the registration processing step registers a corrected record of a font to be registered in a font management table including a font ID and a version; A specific user including a record of characters constituting a corrected font to be registered, including a user, a character, a character revision number, an effective version indicating a version valid for a specific user, and an invalid version indicating a version invalid thereafter. Registering in the character management table and the phone to be registered Indicate whether the record of the character that constitutes is the added version, the deleted version corresponding to the version of the character, the character revision number, and the font management table, and the version that has been corrected for the specific product, and whether it is the latest version with the normal correction Registering in a character history management table including a standard flag Therefore, in the update registration of the corrected font, the corrected font can be updated and registered so as to be effective only for a specific user.
[0062]
Claim 6 According to the invention, the instruction step is , Indicate multiple specific users Ruta Therefore, the corrected font can be updated and registered so as to be effective only for a plurality of specific users.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a basic configuration of a font data management device according to first to third embodiments of the present invention.
FIG. 2 is an explanatory diagram showing a memory configuration according to first to third embodiments of the present invention.
FIG. 3 is an explanatory diagram showing a content configuration of a recording medium storing a font data management program and related data according to the first to third embodiments of the present invention.
FIG. 4 is an explanatory diagram showing a concept in which a font data management program and related data according to the first to third embodiments of the present invention are supplied to a system from a recording medium.
FIG. 5 is a flowchart showing an overall process of the font data management device according to the first and second embodiments of the present invention.
FIG. 6 is a flowchart showing details of registration processing in the overall processing of the font data management device according to the first to third embodiments of the present invention.
FIG. 7 is an explanatory diagram showing a configuration of a font history management table, a character history management table, and a specific user character management table according to the first to third embodiments of the present invention.
FIG. 8 is an explanatory diagram showing an example of a font history management table according to the first embodiment of the present invention, wherein (a) is an explanatory diagram before update registration and (b) is an explanatory diagram after update registration. is there.
FIG. 9 is an explanatory diagram showing an example of a character history management table and a specific user character management table according to the first embodiment of the present invention.
FIG. 10 is an explanatory diagram showing an example of a font history management table according to the second embodiment of the present invention, wherein (a) is an explanatory diagram before update registration and (b) is an explanatory diagram after update registration. is there.
FIG. 11 is an explanatory diagram showing an example of a character history management table and a specific user character management table according to the second embodiment of the present invention.
FIG. 12 is a flowchart illustrating an overall process of the font data management device according to the third embodiment of the present invention.
13A and 13B are explanatory diagrams illustrating an example of a font history management table according to a third embodiment of the present invention. FIG. 13A is an explanatory diagram before update registration, and FIG. 13B is an explanatory diagram after update registration. is there.
FIG. 14 is an explanatory diagram showing an example of a character history management table and a specific user character management table according to the third embodiment of the present invention.
[Explanation of symbols]
1 CPU
2 ROM
3 RAM
4 Keyboard control unit
5 Keyboard
6 Display control unit
7 CRT display device
8 Disk control unit
9 External storage device
9a floppy disk drive
9b Hard disk drive
9c CD-ROM
10 Printer control unit
11 Printer device

Claims (6)

And instruction means for instructing a particular user to enable the fix,
Determining means for comparing a character constituting the latest version of the font with a character constituting the corrected font to be registered, and determining whether at least one character has been updated ;
Registration processing means for performing registration processing of a corrected font to be registered when it is determined that at least one character has been updated by the determination means,
The registration processing means,
Means for registering a corrected record of a font to be registered in a font management table including a font ID and a version;
A specific user including a record of characters constituting a corrected font to be registered, including a user, a character, a character revision number, an effective version indicating a version valid for a specific user, and an invalid version indicating a version invalid thereafter. Means for registering in the character management table;
The records of the characters that make up the corrected font to be registered are added, deleted and corresponding to the specific version of the character, character revision number, and font management table. Means for registering in a character history management table that includes a standard flag indicating whether the font is a font management device. It said instructing means, font management apparatus according to claim 1, wherein the benzalkonium be more indicates a specific user. A font management method executed by a CPU of a font management device , comprising:
An instruction step of instructing a specific user to make the correction effective ;
A determination step of comparing the characters constituting the latest version of the font with the characters constituting the corrected font to be registered, and determining whether at least one character has been updated;
A registration processing step of performing a registration processing of a corrected font to be registered when it is determined that at least one character has been updated by the determination step,
The registration processing step includes:
Registering the corrected record of the font to be registered in a font management table including a font ID and a version;
A specific user including a record of characters constituting a corrected font to be registered, including a user, a character, a character revision number, an effective version indicating a version valid for a specific user, and an invalid version indicating a version invalid thereafter. Registering in the character management table;
The records of the characters that make up the corrected font to be registered are added, deleted and corresponding to the specific version of the character, character revision number, and font management table. Registering in a character history management table including a standard flag indicating whether the font is a font management method. The instruction step, font management method according to claim 3, wherein the benzalkonium be more indicates a specific user. On the computer,
An instruction step of instructing a specific user to make the correction effective ;
A determination step of comparing the characters constituting the latest version of the font with the characters constituting the corrected font to be registered, and determining whether at least one character has been updated;
If it is determined that at least one character has been updated in the determination step, the computer-readable storage medium stores a program for executing a registration processing step of performing a registration processing of a corrected font to be registered. hand,
The registration processing step includes:
Registering the corrected record of the font to be registered in a font management table including a font ID and a version;
A specific user including a record of characters constituting a corrected font to be registered, including a user, a character, a character revision number, an effective version indicating a version valid for a specific user, and an invalid version indicating a version invalid thereafter. Registering in the character management table;
The records of the characters that make up the corrected font to be registered are added, deleted and corresponding to the specific version of the character, character revision number, and font management table. Registering in a character history management table including a standard flag indicating whether the
Computer readable storage medium. The instruction step, the storage medium according to claim 5, wherein the benzalkonium be more indicates a specific user.

Images