JPH08202690A - Method and device for managing font data - Google Patents

Abstract

PURPOSE: To easily perform the history management of font data in every character or version by accepting the specification of information regarding a registered font, processing the information as additional information on font data, and managing the font data on the basis of the additional information. CONSTITUTION: This device consists of a CPU1, ROM2, a RAM3, a keyboard 5, a display device 7, an external storage device 9, etc. In this constitution, the specification of the information regarding the registered font is accepted and processed as the additional information on the font data, and on the basis of the additional information, the font data are managed. For example, when temporary deletion of the registered font data is specified, all registered font data are listed and displayed, the specified font data are temporarily deleted, and the history management of the temporarily deleted font data is performed, so that even a case wherein the temporary deletion specification is reset thereafter can easily be coped with.

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 method and apparatus for managing a history of a plurality of font data.

[0002]

2. Description of the Related Art Generally, there is not one type of product in which font data is installed, but there are many types, and it is necessary to change the font data for a specific product depending on the circumstances of the product.
In particular, when managing font data history, data deviating from such a series of history must be treated as completely different fonts, separated from the history management up to that point. When the font data that should be applied to all products is changed, all the generated font data must be changed.

Further, it is not possible to delete a specific character only from a certain version from the font data in a system that manages the history on a character-by-character basis, and it is realized only by registering it as another font. Can not.

[0004]

However, in the above-mentioned conventional example, it is a waste of the data area to manage as a different font because of a slight change, and the change of the font data which does not depend on the specific product is for the specific product. It had to be applied to multiple font data derived from, which made the management complicated, and mistakes were easy to occur. Also,
It is necessary to re-register the font data to delete and restore the characters, and the version will be unnecessarily increased. Therefore, it has been necessary to change or delete the font data without registering the font data.

The present invention has been made to solve the above problems, and an object of the present invention is to provide a font data management method and apparatus that can easily manage the history of font data in units of characters or versions.

[0006]

In order to achieve the above object, the font data management method of the present invention has the following steps.

A font data management method for managing a history of a plurality of font data, wherein a receiving step of receiving designation of information relating to registered fonts, and the information received in the receiving step is processed as additional information to the font data. It has a processing step and a management step of managing font data based on the additional information processed in the processing step.

To achieve the above object, the font data management device of the present invention has the following configuration.

A font data management device for managing a history of a plurality of font data, and accepting means for accepting designation of registered font-related information, and the information accepted by the accepting means is processed as additional information to the font data. A processing means and a management means for managing font data based on the additional information processed in the processing processing are provided.

[0010]

With this configuration, the designation of information relating to the registered font is accepted, the information is processed as additional information to the font data, and the font data is managed based on the additional information.

[0011]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A preferred embodiment of the present invention will be described in detail below with reference to the drawings.

FIG. 1 is a block diagram showing the basic configuration of the system in this embodiment. The system 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. 2 is a ROM (read-only memory)
And 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 without use restrictions, and is an area in which each program and data are loaded and executed for each various processing. A keyboard control unit (KBC) 4 receives key input data from the keyboard (KB) 5 or a pointing device such as a mouse 12
CP that receives menu instructions from the device (PD)
Transmit to U1.

A display control unit (CRTC) 6 controls the display on a display device described later. 7 is a display device (CR
T), which receives data from the CRTC 6 and displays it. Reference numeral 9 denotes an external storage device such as a floppy disk device (FD) 9a or a hard disk device (HD) 9b, which stores programs and data, and which is referred to or loaded into the RAM 3 at the time of execution as necessary. Reference numeral 8 is a disk control unit (DKC) for controlling data transmission and the like, and 10 is a printer control unit (PRTC).
Reference numeral 1 is a printer device (PRT). Reference numeral 13 denotes a system bus, which should serve as a data path between the above-mentioned components.

Next, a data management format in a font data management system for managing a change history of a plurality of font data in character string units will be described with reference to FIG.

As shown in FIG. 2 (a), the highest level concept of data management is called a font, and there are a plurality of versions underneath it, and character pattern data is under the version, which is a hierarchical structure. ing. However, different versions may be configured with the same characters as in the table of (b) version and the character numbers of constituent characters shown in FIG. 2, and the character pattern depends on the version, but the version and the character pattern are different. It does not have to be one-to-one.

Next, the data holding format in this system will be described with reference to FIG. In this system, the font data includes a table (a) shown in FIG. 3 (a font ID for identifying a font, a version for holding history information, a data number for knowing whether character data has been changed, a temporary Table for managing additional information of the character of (b) shown in FIG. 3), which is composed of a flag indicating whether or not deletion is designated, a flag indicating whether or not modification corresponding to a specific product has been made) , And the character pattern data table (c) shown in FIG.

In FIG. 3A, when the data other than the character pattern is changed, the data number does not change even if the version is different.

The additional number in (b) shown in FIG.
The corresponding data number of (a) shown in FIG. 3 is set.
The deletion number is set to the corresponding data number when the added character is added again. The character numbers are set in ascending order for the same font ID and character code. That is, when version 1 and data number 1, 0010
When 3021 is added, the data in which the character number is 1 and the additional number is 1 is DKC as shown in (b) of FIG.
8 to be stored in the HD 9. Next, in the case of version 3 and data number 2, if 00103021 is added again,
The data in which the corresponding deletion number of the character number 1 is changed to 2 is stored in the HD 9 via the DKC 8, and the data of the character number 2 and the additional number 2 is stored in the HD 9 via the DKC 8. In either case, the character pattern data is stored in the HD 9 via the DKC 8 in the format of (c) shown in FIG.

Further, in the format of (d) shown in FIG. 3, information about the change of the data for a specific product is sent to H through the DKC 8.
The data stored in the D9 and related to the temporary deletion of the specific character in the format of (e) shown in FIG. 3 is transferred to the HD9 via the DKC8.
Stored in. The information on the product is stored in advance in the HD 9 via the DKC 8 in the format of (f) shown in FIG. 3, and the information of the character type to be mounted on the product is stored in advance in the format of (g) shown in FIG. 3 for each product. It is stored in the HD 9.

<First Embodiment> A font data registration / reference method will be described with reference to the drawings, assuming a system in which data is held as described above. Less than,
As a first embodiment, a case where the additional information is temporarily deleted and the information addition target is a character will be described as an example.

First, the data structure of the font data shown in FIG. 4 will be described. 4A shows the number of records in the data management table shown in FIG. In FIG. 4B, the data management table shown in FIG. 3A is read from the HD 9 via the DKC 8 and read R
This is an area for holding on AM3. (C) shown in FIG. 4 belongs to the font_id [i] of (b) shown in FIG. 4 which is instructed as an output processing target, and HD is searched via the DKC 8 to search for referenceable character pattern data.
It is an area for reading from 9 and holding it on the RAM 3. FIG. 4D is an area for reading the character pattern data referred to as the processing target from the HD 9 via the DKC 8 and holding it in the RAM 3. (E) shown in FIG. 4 is the number of records in the table holding the information corresponding to the specific product shown in (d) of FIG. In (f) shown in FIG. 4, the table shown in (d) of FIG. 3 is read from the HD 9 via the DKC 8 and held in the RAM 3 or RA.
This is an area for writing data from the M3 to the HD 9 via the DKC8.

5A shows the number of records in the temporary deletion character table shown in FIG. 3E, and FIG. 5B shows the number of records in FIG. 3E via the DKC 8. Read from HD9 and hold on RAM3 or DKC from RAM3
It is an area for writing to the HD 9 via the memory 8. 5C shows the number of records in the product table shown in FIG. 3F, and FIG. 5D shows the product table shown in FIG. 3F from the HD 9 via the DKC 8. Read RA
It is an area for holding on M3. As shown in FIG.
Is an area for holding the number of records of the character type table installed for each product shown in (g) of FIG. 3 on the RAM 3, and (f) shown in FIG. 5 shows the character type table from the HD 9 via the DKC 8. This is an area to be read and held in the RAM 3. (G) shown in FIG. 5 is an area for holding the table index of (b) shown in FIG. 4 corresponding to the font and version selected as the processing target on the RAM 3.

In the above arrangement, the processing procedure for temporary deletion according to the first embodiment will be described below with reference to the flow charts shown in FIGS.

First, in step S101, the information of all the fonts registered in this system is read from the HD 9 via the DKC 8 and stored in (a) and (b) of FIG. 4 for either data reference or registration. The designation of whether or not to perform the process is received from the KB 5 or PD 12 via the KBC 4.
Next, in step S102, the received designation is determined, and if it is a data reference, the process proceeds to step S110 to perform a data reference process described later. However, if it is data registration, the process proceeds to step S103, the process type is accepted, and in step S104, it is determined whether or not the process type is completed. If it is completed, the process ends.

However, if it is not completed, step S105.
Then, it is determined whether the processing type is additional information addition, and if additional information is added, that is, if temporary deletion is designated, step S1.
Proceeding to 06, information regarding the temporarily deleted characters is first read into (a) and (b) shown in FIG. Next, referring to (b) shown in FIG. 4 from i = 0 to font_num−1, the following processing is performed.

Font_id [i], version
The character corresponding to [i] is read in the format of FIG. Then, (b) shown in FIG. 5 is searched up to j = 0 to del_num−1 using the code as a key, and font_i
d_i [, font_id [j] matching code,
If code [j] is present, temporary deletion is specified, and therefore temporary deletion has already been specified, so it is not displayed in the list as a non-process target. If there is no match, temporary deletion can be specified, so it is displayed in the list as a processing target.

On the other hand, if it is determined in step S105 that the designation is temporary deletion cancellation, step S10
7, the information regarding the temporarily deleted characters is read in the same manner as in step S106, and i = 0 to del_nu
List up to m-1 as a processing target. Next, in step S108, K is selected for the character to be processed.
It is accepted from the KB 5 or PD 12 via the BC 4, and information is added or changed in step S109. When information is added, that is, when temporary deletion is designated, the font ID of the selected character is added to font_id [del_num] of FIG. 5B, and version [del_num].
Select the version of the selected character in code [del_nu
m] is the character code of the selected character, char_no [de
Set the character numbers of the selected characters to [l_num],
Count up del_num. In case of changing information, that is, canceling temporary deletion, delete the corresponding record,
Count down del_num. Then, the updated data on the RAM 3 is written to the HD 9 via the DKC 8 and the process returns to step S103.

Next, the processing when referring to data will be described. First, in step S110, as shown in FIG.
The font stored in i = 0 to font_num
A list of unique font_id [i] (excluding those different only in version) from -1 is displayed and a selection is accepted. Next, in step S111, when it is determined that the end is instructed, the process returns to step S101. However, when the font is selected in step S111, the process proceeds to step S112, and (b) illustrated in FIG. 4 is searched from i = 0 to font_num−1, and the font_id [i] that matches the selected font_id [] is searched. ] [Version] [] of [] is displayed in a list and the selection is accepted.
Then, the index of the selected record is held in slctd_font of (g) shown in FIG.

Then, in step S113, the product name in which the character data is mounted for accepting the code of the extracted character is accepted. Figure 5 from the specified product name
(D) shown in is searched from i = 0 to prdct_num-1 to obtain prdct_id [i] in which prdct_name [i] matches the designated product name, and the corresponding character code group is passed from HD9 to DKC8. Figure 5
It is stored in the RAM 3 in the format (f) shown in FIG. Next, in step S114, codes [i], i = 0 to
The following processing is performed up to ncode-1.

In FIG. 5B, j = 0 to del_nu.
m-1 is searched, and font_id in FIG.
[J], version [j], code [j] are the selected font ID and version, respectively.
Font_id [slctd_fon of (b) shown in FIG.
t], version [slctd_font], and
If it matches with code [i], since temporary deletion is specified and it is not an output target, processing for the next character code is performed. When the temporary deletion is not designated, the additional registration information table of characters stored in the HD 9 in the format of (c) shown in FIG. 4 is sequentially referenced through the DKC 8 and shown in the RAM 3 as shown in FIG. ) Format. The font_id and code of (c) shown in FIG. 4 are f
ont_id [slctd_font], codes
Same as [i], add number add_no and delete number de
l_no, data number data_no [slctd_f
ont], the character pattern data is referred to.

Add_no≤data_no [slct
d_font] <del_no add_no ≦ data_no [slctd_font
t] and del_no are undefined. The search is repeated by referring to the additional character registration information until data matching any of the above conditions is found. Then, the referable data is sent to PRT11 via PRTC10.
To the CRT 7 via the CRTC 6 and to the HD 9 via the DKC 8 for presentation at step S110.
Return to

<Modification> In the above-described embodiment, the case where information is added in character units has been described as an example, but the present invention is not limited to this, and for example, information is added in version units and font units. Is also good.

Next, information addition and designation of a cancellation unit in the modified example will be described with reference to FIG. In the following description, one character, one version, and one font are designated as an example, but it goes without saying that the designation is not limited to one.

First, designation of information addition will be described.
In step S201, i = 0 to f in FIG.
search up to ont_num-1 and list all the version deletion flags del_flag [i] to which it belongs to as an object to be processed, and select the font and the presence / absence of the version designation through PD12 or KBC4.
Accept from B5. Next, in step S202, if it is determined that no version is specified, the process ends, but if it is determined that version is specified, step S20 is performed.
3 is searched, (b) of FIG. 4 is searched, and among the versions belonging to the selected font, the versions for which the deletion flag is not ON are displayed as a processing target, and the version selection and the presence / absence of character designation are performed via the PD 12 or the KBC 4. Te KB5
Accept from.

Next, in step S204, if it is determined that there is no character designation, the process ends, but if it is determined that there is a letter designation, the process proceeds to step S205, in which data is sequentially read from the HD 9 to (c) shown in FIG. 4 and selected. Font_id and code match the font and version
add_no ≤ selected font, data number corresponding to version <del_no add_no ≤ selected font, data number corresponding to version, del_no is one of the undefined relationship is true, record corresponding to (b) shown in FIG. If it does not exist, it is not temporarily deleted, and a list is displayed as the processing target and the selection is accepted.

Then, in step S109 shown in FIG. 6, if the processing target is a font, it is shown in FIG. 4 (b).
The deletion flag of all records having font_id [] matching the specified font of is turned ON. If the processing target is a version, font_id that matches the designated font and version of (b) shown in FIG.
The deletion flag of the record having [], version [] is turned ON.

Next, cancellation of additional information will be described.
In step S201, i = 0 to f in FIG.
Search up to ont_num-1 and process fonts for which at least one deletion flag del_flag [i] of the belonging version is ON, and fonts for which font_id [i] shown in FIG. A list is displayed as and the presence or absence of font selection and version designation is accepted from KB5 via PD12 or KBC4. In list view, all versions are temporarily deleted. Whether the partial version is temporarily deleted or the character is temporarily deleted is indicated by means such as displaying a character string and a predetermined symbol together with the font. Next, in step S202, if it is determined that no version is specified, the process ends, but if it is determined that version is specified, the process proceeds to step S203 to search (b) of FIG. 4 and delete the version belonging to the selected font. Version with flag ON and font
5B in FIG. 5 in which _id [i] and version [i] match is displayed as a processing target in a list, and the version selection and the presence / absence of character designation are PD
12 or from KB5 via KBC4. In the list display, whether all versions are temporarily deleted or characters are temporarily deleted is indicated by means such as displaying a character string or a predetermined symbol together with the version.

Next, in step S204, if it is determined that no character is specified, the process ends, but if it is determined that character is specified, the process proceeds to step S205, where i in FIG.
= 0 to del_num-1 is displayed as a processing target and a selection is accepted.

Then, in step S109 shown in FIG. 6, if the processing target is a font, it is shown in FIG. 4 (b).
The delete flag of all the records having the font_id [] matching the specified font is turned off. If the processing target is a version, font_id [] matching the specified font and version of (b) shown in FIG. 4,
Set the deletion flag of the record having version [] to O
Set to FF.

Next, the data reference will be described. Figure 7
In step S110 shown in FIG. 4, (b) shown in FIG. 4 is searched from i = 0 to num−1, and a list is displayed as a processing target except that the deletion flags del_flag [i] of all the versions to which they belong are ON. Select the font P
Accepted from KBC5 via D12 or KBC4. The font specification acceptance process ends.

Further, in step S112 shown in FIG. 7, (b) of FIG. 4 is searched, and among the versions belonging to the selected font, the versions for which the deletion flag is not ON are displayed as a processing target and the selection of the version is selected by the PD12.
Alternatively, it is accepted from KB5 via KBC4. The version specification acceptance process ends.

<Second Embodiment> In the first embodiment, the temporary deletion is described as an example of the additional information, but the present invention is not limited to this. For example, information that the correction is made corresponding to a specific product. It is also possible to apply when adding.

9 and 10 are flowcharts showing the processing procedure according to the second embodiment. First, step S
In 301, the target product name is accepted, and in step S302, the information of all fonts registered in the system is read from the HD 9 via the DKC 8,
(A) and (b) shown in FIG. Then, the designation of whether to perform data reference or registration is received from the KB 5 or PD 12 via the KBC 4. Next, in step S303, if the designation is data reference, the process proceeds to step S311 to perform data reference processing.

If the designation is registration, step S
The process proceeds to 304, the processing type is accepted, and step S305
It is determined whether or not to end. Here, if it is finished, the process is terminated, but if it is not finished, the process proceeds to step S306, and it is determined whether the designation is a correction designation corresponding to a specific product. As a result, if it is the correction designation for the specific product, the process proceeds to step S307. First, referring to (d) shown in FIG. 5 from the designated product name, the product ID is obtained, and the information on the characters corrected like this product ID is obtained. (E) shown in FIG.
Read in (f). Next, (b) i = 0 to f shown in FIG.
The following processes are performed with reference to ont_num-1.

Font_id [i], version
The character corresponding to [i] is read in the format of FIG. Then, (f) shown in FIG. 4 is searched from j = 0 to spec_num-1 using the code as a key, and font_
font_id matching id [i], code
If there is [j] or code [j], it is not displayed in the list as a non-process target because it has already been designated as a specific product correspondence. If there is no match, it is possible to specify a specific product correspondence and display it in the list as a processing target.

On the other hand, if it is determined in step S306 that the specific product correspondence is released, the process proceeds to step S308, and information regarding the characters corresponding to the specific product is displayed in step S3.
Read as in 07, i = 0 to spec_num-1
To list up to be processed. Next, step S
In 309, the selection of the character to be processed is KBC4.
Accept from KB5 or PD12 via
At 310, information is added or changed. In the case of the addition of information, that is, the modification designation corresponding to the specific product, the product ID is set in prdct_id [spec_num] of FIG. 4F, the font ID of the selected character is set in font_id [spec_num], and the version [spec_nu] is specified.
m] is the version of the selected character, code [spec_
num] with the character code of the selected character, char_no
Enter the character number of the selected character in [spec_num] inv
0 is set in each of alid [spec_num], and spce_num is counted up. Further, in the case of changing the information, that is, releasing the modification corresponding to the specific product, the version of the selected character is set in the invail [i] of the corresponding record. Then, the updated data on the RAM 3 is written to the HD 9 via the DKC 8 and the process returns to step S304.

Next, the processing when referring to data will be described. First, in step S311, the font held in FIG. 4B is set to i = 0 to font_num-1.
Among the above, unique font_id [i] (excluding those having different versions only) in which spec_flag [i] is 0 or one or more product IDs corresponding to the designated product name are displayed in a list, and the selection is accepted.

If it is determined in step S312 that the termination is instructed, the process returns to step S301. If a font is selected in step S312, i is displayed in step S313 in FIG.
= 0 to font_num-1 and selected f
matches ont_id [], and spec_flag
A list of versions [i] in which [i] is 0 or the same product ID as the designated product name is displayed, the selection is accepted, and the index of the selected record is held in slctd_font of (g) shown in FIG. .

Next, in step S314, the product I
A character code group corresponding to D is stored in the RAM 3 from the HD 9 through the DKC 8 in the format of (d) shown in FIG. 5, and the specific product correspondence correction table corresponding to the selected version is stored in FIG.
HD9 via DKC8 in the formats (e) and (f) shown in FIG.
It is held in the RAM 3 more. codes [i], i = 0
The following processes are performed up to ncode-1.

In (f) of FIG. 4, j = 0 to spec_n
um-1 is searched, and prdct_id in FIG.
If [i], font_id [i], code [j] are the same as the product code corresponding to the specified product name, f
ont_id [j], version [j], code
[J] is a product code corresponding to the specified product name,
Font_id [slctd_fon in FIG.
When t] and codes [i] are the same, the character number of the character to be output is obtained as follows.

Version [slctd_font]
Is the same as version [j], (f) c in FIG.
Reference the character pattern data corresponding to har_no [i]. In addition, version [slctd_fon
When t] is different from version [j], the data to be referred to by the relationship with the corresponding invalid version in FIG. 4 (f) invalid [j] are as follows.

Version_slctd_fon
When t] <version [j], fo in FIG.
nnt_id, code is font_id [slctd
_Font], codes [i], additional number a
dd_no, deletion number del_no, data number dat
When the relationship of a_no [slctd_font] is as follows, the character pattern data is referenced.

Add_no≤data_no [slct
d_font] <del_no or add_no ≦ data_no [slctd_fon
t] and del_no are undefined. version [slctd_font]> vers
version [j], version [slctd_fo
nt] <invalid [j] or invalid
If [j] is 0, the specific product modification support is valid, so the character pattern data corresponding to (f) char_no [j] in FIG. 4 is referred to.

If not, fon in FIG.
nt_id, code is font_id [slctd_
font], codes [i], additional number ad
d_no, deletion number del_no, data number data
When the relationship of _no [slctd_font] is as follows, the character pattern data is referenced.

Add_no≤data_no [slct
d_font] <del_no or add_no ≦ data_no [slctd_fon
t], del_no is undefined, and if there is no corresponding record in the specific product correspondence correction table, font_id, code in FIG. 4C is fo.
nt_id [slctd_font], codes
Same as [i], add number add_no and delete number de
l_no, data number data_no [slctd_f
ont], the character pattern data is referred to.

Add_no≤data_no [slct
d_font] <del_no or add_no ≦ data_no [slctd_fon
t], del_no is undefined. Referenceable data is PRT11 via PRTC10.
To the CRT7 via the CRTC6 and to the HD9 via the DKC8. Then, the process returns to step S311.

The present invention may be applied to either a system composed of a plurality of devices or an apparatus composed of a single device.

It goes without saying that the present invention can also be applied to the case where it is achieved by supplying a program to a system or an apparatus.

[0060]

As described above, according to the present invention,
It is possible to provide a font data management method and device that can easily manage the history of font data for each character or version.

[0061]

[Brief description of drawings]

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

FIG. 2 is a diagram showing a data relationship in an example.

FIG. 3 is a diagram showing a configuration of a character data management table in the embodiment.

FIG. 4 is a diagram showing a data structure related to font data in the embodiment.

FIG. 5 is a diagram showing a data structure related to font data in the embodiment.

FIG. 6 is a flowchart showing a processing procedure in the first embodiment.

FIG. 7 is a flowchart showing a processing procedure in the first embodiment.

FIG. 8 is a flowchart showing a processing procedure in a modified example.

FIG. 9 is a flowchart showing a processing procedure in the second embodiment.

FIG. 10 is a flowchart showing a processing procedure in the second embodiment.

[Explanation of symbols]

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

Claims (10)

[Claims] 1. A font data management method for managing a history of a plurality of font data, comprising a receiving step of receiving designation of information relating to registered fonts, and the information received in the receiving step as additional information to the font data. A font data management method comprising: a processing step of processing; and a management step of managing font data based on additional information processed in the processing step. 2. The font data management method according to claim 1, wherein the information is temporary deletion. 3. The font data management method according to claim 1, wherein the information is a correction for a specific product. 4. The font data management method according to claim 1, wherein the management step manages the font data in character units. 5. The font data management method according to claim 1, wherein the management step manages font data on a version-by-version basis. 6. A font data management device for managing a history of a plurality of font data, the receiving means receiving designation of information relating to registered fonts, and the information received by the receiving means as additional information to font data. A font data management device comprising: processing means for processing; and management means for managing font data based on the additional information processed in the processing. 7. The font data management device according to claim 6, wherein the information is temporary deletion. 8. The font data management device according to claim 6, wherein the information is a correction for a specific product. 9. The font data management device according to claim 6, wherein the management unit manages the font data on a character-by-character basis. 10. The font data management device according to claim 6, wherein the management unit manages the font data in version units.