Printer
Through the technology of obtaining and generating adaptive font data in the printer, the problem of users needing to prepare different font data according to the type of printed data is solved, and a simple correspondence between the type of printed data and the form of font data is achieved, which improves the convenience of use.
Patent Information
- Application Number
- CN202410562590.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-09
- Filing Date
- 2024-05-08
- Publication Date
- 2024-11-12
AI Technical Summary
Users need to prepare corresponding font data according to different types of printing data and store it in the printer, which is inconvenient to use.
A printer is designed with a memory and a controller that can acquire different types of printing data and generate adaptive font data based on stored font data, so as to print with the same font data under different printing data.
It realizes a simple correspondence between the types of printed data and the forms of font data. Users do not need to consider the forms of font data and the types of printed data, so that font data is convenient to use.
Smart Images

Figure CN118939206A_ABST
Abstract
Description
Technical Field
[0001] The technical field disclosed in this specification relates to a printer capable of printing based on print data described in a page description language. Background Art
[0002] Conventionally, as disclosed in Patent Document 1, for example, there is a configuration in which font information is stored in a printer capable of printing based on print data described in a page description language.
[0003] Prior art literature
[0004] Patent Literature
[0005] Patent Document 1: Japanese Patent Application Publication No. 2014-56583
[0006] Technical problem to be solved by the invention
[0007] The format of font data sometimes differs depending on the type of print data. Therefore, the user needs to prepare font data that matches the type of print data and store the font data in the printer. However, if the type of print data must be considered in order to prepare font data, it is inconvenient to use. Summary of the invention
[0008] Technical means for solving technical problems
[0009] A printer for the purpose of solving the technical problem comprises a memory, a printing engine and a controller, wherein the memory can store font data of a first form corresponding to a first type of printing data, and the controller is configured to perform the following processes: an acquisition process, in which the printing data is acquired; a generation process, in which, when the printing data acquired in the acquisition process is a second type of printing data, font data of a second form corresponding to the second type of printing data is generated based on the font data of the first form stored in the memory; and a drawing process, in which the text specified by the printing data is drawn using the font data of the second form generated in the generation process.
[0010] The printer disclosed in this specification obtains the second type of printing data, and generates and draws the second type of font data corresponding to the second type of printing data based on the first type of font data corresponding to the first type of printing data stored in the memory. That is, even for the second type of printing data, the printer can print text based on the first type of font data. Therefore, if the user stores the first type of font data in the printer, the font can also be used by the printer in printing based on the second type of printing data. As a result, there is no need to consider the form of the font data and the type of printing data, and fonts can be easily used.
[0011] A printing system including the above-mentioned printer, a control method for realizing the functions of the printer, a computer program, and a storage medium readable by a computer storing the program are also novel and useful.
[0012] Effects of the Invention
[0013] According to the technology disclosed in this specification, a technology capable of easily coping with combinations of the types of print data and the formats of font data is realized in a printer. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] Figure 1 This is a block diagram showing the schematic structure of a printer.
[0015] Figure 2 This is a flowchart showing the steps of print job processing.
[0016] Figure 3 This is an explanatory diagram showing a schematic structure of font information of the first format.
[0017] Figure 4 This is an explanatory diagram showing a schematic structure of the second format font information.
[0018] Figure 5 : is a flowchart showing the steps of font registration processing.
[0019] Figure 6 This is a flowchart showing the steps of character intermediate data generation processing.
[0020] Figure 7 This is a flowchart showing the steps of print job processing.
[0021] Figure 8 : is a flowchart showing the steps of font registration processing.
[0022] Explanation of symbols
[0023] 1 Printer
[0024] 11CPU
[0025] 12 Memory
[0026] 15 Printing Engine. DETAILED DESCRIPTION
[0027] Hereinafter, a printer according to a first embodiment will be described in detail with reference to the drawings. This embodiment discloses a printer capable of printing based on print data described in a page description language.
[0028] like Figure 1 As shown, the printer 1 includes a control unit 10 including a CPU 11 and a memory 12. In addition, the printer 1 includes a user interface (hereinafter referred to as "user IF") 13, a communication interface (hereinafter referred to as "communication IF") 14, and a printing engine 15. The CPU 11 is an example of a controller. The user IF 13, the communication IF 14, and the printing engine 15 are all electrically connected to the control unit 10. In addition, Figure 1 The control unit 10 in the text is a general term for hardware and software used to control the printer 1 , and is not limited to referring to a single piece of hardware actually present in the printer 1 .
[0029] The CPU 11 executes various processes according to the program read from the memory 12 or based on the user's operation. Various programs and various data are stored in the memory 12. The memory 12 is also used as a work area when executing various processes. The memory 12 may also include a buffer provided by the CPU 11.
[0030] In addition, an example of the memory 12 is not limited to the ROM, RAM, HDD, etc. built into the printer 1, and any storage medium that can be read and written by the CPU 11 can be used. For example, an external memory such as a USB memory or HDD connected to the printer 1 via the communication IF 14; a memory or HDD included in a device connected to the printer 1 via the communication IF 14 is also an example of the memory 12.
[0031] For example, Figure 1 As shown, the memory 12 stores a print control program 21, first font information 22, second font information 23, and a generation program 24. The first font information 22 and the second font information 23 may or may not be stored in the memory 12 when the printer 1 is shipped. Details of each program and data will be described later.
[0032] The user IF 13 includes hardware for displaying a screen for notifying the user of information and hardware for accepting user operations. The user IF 13 may include a touch panel or a combination of a display unit and operation buttons.
[0033] The communication IF 14 includes hardware for communicating with an external device. The communication standard of the communication IF 14 is Ethernet (registered trademark), Wi-Fi (registered trademark), USB, etc. The printer 1 may include a plurality of communication IFs 14 corresponding to a plurality of communication standards.
[0034] The print engine 15 includes, for example, a device capable of printing based on image data by electronic photography or inkjet printing. The print engine 15 may include coloring materials of multiple colors to perform color printing, or may include coloring materials of only one color to perform monochrome printing.
[0035] In addition, for example, Figure 1 As shown, the printer 1 can communicate with the server 100 via the communication IF 14. The server 100 may be an external device storing font information. The printer 1 can receive a file containing font information from the server 100 based on a user's instruction and store it in the memory 12. In addition, the user can connect a USB memory storing font information to the printer 1, so that the printer 1 can use the font information stored in the USB memory.
[0036] Next, the operation of the printer 1 of the first embodiment is described. In addition, the following processing basically represents the processing of the CPU 11 according to the command recorded in the program. The processing of the CPU 11 also includes the hardware control via the API of the operating system (hereinafter referred to as "OS"). In this specification, the operation of each program is sometimes described by omitting the record of the OS. In addition, "acquisition" is used as a concept including the case of acquisition upon request and the case of acquisition without request. Moreover, data with the same essential content but different formats are treated as the same data.
[0037] The printer 1 can acquire a print job and execute printing based on the acquired print job. For the steps of the print job processing including the steps of printing based on the print job, refer to Figure 2 The print job process is executed by the CPU 11 of the printer 1 based on the print control program 21. The printer 1 can receive and acquire a print job from an external device via the communication IF 14, or can read and acquire a print job from a USB memory attached to the communication IF 14.
[0038] The print job is, for example, data representing an image of a print object, and includes PDL data described in a page description language and PJL data representing various parameters related to printing. The PDL data included in the print job includes multiple types, such as PCL5 provided by Hewlett-Packard (registered trademark) and PDF. PDL data in PCL5 format is an example of the second type of print data. PDL data in PDF format is an example of the first type of print data. The printer 1 can determine the type of PDL data based on the PJL data, for example.
[0039] Figure 2 The print job processing shown is a processing for executing a print job including PDL data in the PCL5 format when an execution instruction is received. In this specification, description of the processing of a print job including PDL data in a format other than the PCL5 format is omitted.
[0040] In the print job processing, the CPU 11 obtains a font ID for identifying a font (S101). The font ID is information associated with each font. The font ID is an example of first identification information. The font ID is, for example, a numerical value. The font ID may also be a character string.
[0041] Specifically, in S101, the CPU 11 obtains the font ID associated with the information of each font for all fonts included in the first font information 22 and the second font information 23 stored in the memory 12. In addition, when the font information is stored in the USB memory connected to the printer 1, the CPU 11 obtains the font ID associated with the font information stored in the USB memory.
[0042] The printer 1 can store the information of each font, for example, as a font file for each font. The first font information 22 and the second font information 23 may also include a plurality of font files. Each font file is not limited to being managed by a file system, and for one font, is information including a plurality of glyph data representing the shape of a character. Glyph data is an example of font data.
[0043] The font ID may be included in the font file or stored separately from the font file in association with the font file. Alternatively, when a font file is downloaded from an external device, for example, the printer 1 may generate a font ID and store the font ID in association with the font file downloaded from the external device.
[0044] The first font information 22 includes a font file storing font data of the first format corresponding to the PDF format PDL data. Examples of the font file containing the font data of the first format include TrueType fonts, OpenType fonts, and PostScript fonts. The font file included in the first font information 22 is an example of a first font file. In addition, in processing a print job containing PDL data in the PCL5 format, the printer 1 cannot directly use the font file included in the first font information 22 for printing.
[0045] The font file in the TrueType font format of the first font information 22 includes, for example, Figure 3 The font information 30 has the structure shown. The font information 30 includes a header table 31, a character table 32, a location table 33, and a glyph table 34. In addition, the font information 30 may include information indicating the printing position and information indicating the character width for each character.
[0046] The header table 31 is a table storing information including position information of the character table 32, position information of the location table 33, and position information of the glyph table 34. The character table 32 is a table associating the character code of each character with the glyph ID of the character. The character code is information for identifying each character. The location table 33 is a table associating the glyph ID with the position information of the glyph data corresponding to the glyph ID for each glyph ID. The glyph ID is identification information for identifying the glyph data of each character.
[0047] The font table 34 is a table storing a plurality of font data such as font data 341 and 342. Each font data is information indicating the outline of each character, and a unique font ID is assigned to each of them.
[0048] The second font information 23 includes a font file storing glyph data in a second format corresponding to PDL data in PCL5 format. The font file included in the second font information 23 is an example of a second font file. In processing a print job including PDL data in PCL5 format, the printer 1 can directly use the font file included in the second font information 23 for printing. Hereinafter, the font of the font file corresponding to the print data in PCL5 format is referred to as a "PCL font".
[0049] The font file of the PCL font included in the second font information 23 includes, for example, Figure 4 The font information 40 is structured as shown. The font information 40 includes a font header 41, segmentation information 42, and a plurality of glyph data 43, 44, and the like.
[0050] The font header 41 includes a font ID and is a header that stores information related to the entire font. The segmentation information 42 stores auxiliary information of the font information 40, which is a PCL font, for example. In addition, the font data of each character includes a font header and a font data body. The font header 431 is information related to the font data 43, including, for example, format information, size information, and a font ID. The font data body 432 is information indicating the outline of the character of the font data 43, which is equivalent to the font information 30 (see Figure 3 )’s font data 341, 342, etc.
[0051] That is, the glyph data (eg Figure 3 The font data 341 of the second font information 23 and the font data contained in the font file (for example Figure 4 The font data 43) is font data of different formats. Furthermore, the printer 1 uses font data of different formats to draw text according to the type of PDL data included in the print job.
[0052] return Figure 2 In S101, the CPU 11 can process the print job according to the font information 40 (refer to Figure 4 ) to obtain the font ID of the font included in the second font information 23. On the other hand, each font information 30 (refer to Figure 3 ) may not be associated with the font ID. When the font information stored in the memory 12 or the USB memory is not associated with the font ID, the CPU 11 may set the font ID in association with the font not associated with the font ID in S101.
[0053] Next, the CPU 11 obtains the print data included in the print job (S102). S102 is an example of an acquisition process. Then, based on the acquired print data, the CPU 11 determines whether a font ID selection instruction for specifying the font of the characters to be printed has been obtained (S111). The font ID selection instruction is an instruction that includes a font ID and specifies the font used in printing based on the font ID.
[0054] When determining that the acquired print data is a font ID selection command (S111: YES), the CPU 11 executes a font registration process (S112). The font ID included in the font ID selection command acquired in S111 is an example of the second identification information.
[0055] For the font registration process, refer to Figure 5In the font registration process, the CPU 11 retrieves the font ID that matches the font ID specified by the font ID selection command from the font IDs of each font file (S201). Specifically, the CPU 11 extracts the font ID that matches the font ID specified by the font ID selection command from the font IDs obtained in S101 of the print job process. Thus, the CPU 11 determines the font specified for the print data. S201 is an example of font determination processing.
[0056] Then, as the font determined in S201, the CPU 11 determines whether there is a PCL font (S202). For example, when a plurality of fonts are retrieved in S201, the CPU 11 determines whether there is a PCL font among the fonts retrieved in S202. When a font is retrieved in S201, the CPU 11 determines whether the font retrieved in S202 is a PCL font.
[0057] When it is determined that there is no PCL font (S202: No), the CPU 11 reads the font file of the font determined in S201 into the volatile area of the memory 12 (S203). In addition, when the font ID cannot be retrieved in S201 and the font file is not read in S203, the CPU 11 may set it as an error or replace it with another stored font.
[0058] Furthermore, the CPU 11 generates a font header of the PCL font based on the header information of the read font file (S204). Figure 4 The font header 41 included in the font information 40 shown is a font header of the same structure. The font header generated in S204 includes information for associating character codes with glyph data, but does not include glyph data for each character.
[0059] After S204, or when it is determined that there is a PCL font (S202: Yes), the CPU 11 registers the font header internally (S205). The CPU 11 registers the font header generated in S204 or the font header of the determined PCL font. After S205, the CPU 11 ends the font registration process and returns to the print job process.
[0060] return Figure 2 In the print job processing, after the font registration processing in S112, the CPU 11 proceeds to S102 to further acquire print data. Then, when it is determined that the acquired print data is not a font ID selection instruction (S111: No), the CPU 11 determines whether the acquired print data is a character code of a character designated to be printed (S121).
[0061] When it is determined that the acquired print data is a character code (S121: Yes), the CPU 11 executes character intermediate data generation processing for each character to be printed (S122). S121 of acquiring the character code of the character to be printed is an example of character acquisition processing.
[0062] For the steps of character intermediate data generation processing, refer to Figure 6 The CPU 11 determines whether the font file in which the font header is registered has font data of the character to be printed specified in the printing data registered (S301). The registration of the font header is performed in the above-mentioned font registration process (refer to Figure 5 ) is executed in S205.
[0063] Furthermore, when starting the character intermediate data generation process, if the font header is not registered, the CPU 11 may set it as an error, or may use another substitute font. For example, if a font file of a PCL font is stored in the memory 12 as a substitute font, the CPU 11 may read the font file of the PCL font stored in the memory 12 in S301 and register the font header.
[0064] When it is determined that font data of the characters to be printed are registered (S301: Yes), the CPU 11 acquires the registered font data as font data for rasterization (S302). The font data acquired in S302 is font data of a PCL font, which is font data in a format corresponding to the print data in the PCL5 format. S302 is an example of font data determination processing.
[0065] For example, if in the font registration process (refer to Figure 5 ) is a PCL font, the CPU 11 can obtain the glyph data of each character based on the font header registered in S205 of the font registration process. In addition, if it is a PCL font but there is no glyph data corresponding to the character code, the CPU 11 can generate intermediate data of a blank character, for example.
[0066] On the other hand, when the font retrieved in S201 of the font registration process is not a PCL font, even if the font header has been registered, the glyph data of each character may not necessarily be registered. When it is determined that the glyph data of the character to be printed is not registered (S301: No), the CPU 11 obtains the glyph ID corresponding to the character data based on the font file read in S203 of the font registration process (S311). The glyph ID is information for identifying each glyph data and is also information indicating the storage location of the glyph data of each character.
[0067] Furthermore, the CPU 11 acquires font data of a character corresponding to the acquired font ID from the read font file (S312). Since the determined font is not a PCL font, the font data acquired in S312 is not font data of a PCL font.
[0068] Then, the CPU 11 generates PCL font font data based on the font data acquired in S312 (S313). The CPU 11 generates PCL font font data by adding character format information, size information, font ID, etc. to the font data of the TrueType font acquired in S312. S313 is an example of the generation process.
[0069] Furthermore, the CPU 11 executes the process of S313 based on the generation program 24. The generation program 24 may be included in the print control program 21, or may be a program called from the print control program 21 and executed.
[0070] Furthermore, CPU11 registers the generated glyph data for one character in association with the already registered font header (S314). That is, CPU11 stores the glyph data obtained through S313 as glyph data corresponding to the character code of the character of the printing object. In S314, CPU11 may also generate association information that associates the character code of the printing object with the corresponding glyph ID (the glyph ID in the glyph data generated in S313). In addition, CPU11 may also generate a hash table and register the generated association information in the hash table. CPU11 may also store the hash table in association with the already registered font header in the memory 12. In the case where the hash table associated with the already registered font header is already stored in the memory 12, the hash table may not be re-created, but the association information generated in the hash table of the memory 12 may be stored. S314 is an example of character storage processing.
[0071] By registering the generated font data, the CPU 11 can obtain the registered font data in S302 of the next character intermediate data generation process. In addition, when the registered font data is obtained in S302, the CPU 11 does not register the obtained font data. That is, when the same character is printed multiple times through one printing job, the CPU 11 does not need to generate or register the same font data each time. Thus, the waste of processing can be reduced.
[0072] After S302 or S314, the CPU 11 generates intermediate data of the characters to be printed using the acquired font data (S321). Furthermore, the CPU 11 arranges the generated intermediate data at an appropriate position of the intermediate data of the page. After S321, the CPU 11 ends the character intermediate data generation process and returns to the print job process.
[0073] The font header registered in S205 of the font registration process and the font data registered in S314 of the character intermediate data generation process are stored in a volatile area of the memory 12. That is, these information are not stored in the memory 12 after the running print job is completed.
[0074] return Figure 2 In the print job processing, after the font registration processing in S112, the CPU 11 proceeds to S102 to further acquire print data. Then, when it is determined that the acquired print data is not a character code of a character that specifies a print object (S121: No), the CPU 11 determines whether the acquired print data represents a drawing object for printing other than a character (S131).
[0075] When it is determined that the drawing object is a drawing object indicating printing other than characters (S131: YES), the CPU 11 generates and arranges intermediate data other than characters (S132). The description of the process of generating intermediate data other than characters is omitted.
[0076] When it is determined that the acquired print data is not a drawing object indicating printing other than characters (S131: No), the CPU 11 determines whether the acquired print data is a page end command indicating the end of a page (S141). When it is determined that a page end command is acquired (S141: Yes), the CPU 11 generates raster data for one page based on the generated intermediate data (S142). S142 is an example of drawing processing.
[0077] The print engine 15 of the printer 1 can then print one page based on the generated raster data, thereby outputting a printed matter including text drawn in the font specified by the font ID selection command.
[0078] When it is determined that the acquired print data is not a page end command indicating the end of the page (S141: No), the CPU 11 determines whether the acquired print data is a job end command (S151). When it is determined that it is not a job end command (S151: No), the CPU 11 proceeds to S102 and acquires print data again. When it is determined that a job end command is acquired (S151: Yes), the CPU 11 ends the print job processing.
[0079] As described above in detail, when the printer 1 of the first embodiment performs printing based on the print data in the PCL5 format, it generates the font data of the PCL font based on the font data of the first font information 22 stored in the memory 12, thereby being able to draw text using the font. Therefore, as long as the font data in the TrueType font format is stored in the memory 12, the printer 1 can use the font data stored in the memory 12 regardless of whether the printing is based on the print data in the PDF format or the print data in the PCL5 format.
[0080] Thus, the user can use the downloaded font file for printing regardless of the type of print data simply by downloading a font file including font data in TrueType font format. The user does not need to prepare multiple font files for the same font or consider the type of print data.
[0081] Next, the printer involved in the second embodiment will be described in detail with reference to the accompanying drawings. This embodiment is different from the printer 1 of the first embodiment which only registers the font header in that, when a font other than the PCL font is specified in the print job, not only the font header but also the font information of the PCL font including the glyph data of each character is generated and registered. Hereinafter, the same components and steps as those of the printer 1 of the first embodiment are marked with the same symbols as those of the first embodiment and are briefly described.
[0082] For the steps of the print job processing executed by the printer 1 of the second embodiment, refer to Figure 7 When the CPU 11 of the printer 1 of the second embodiment determines that a font ID selection command for a designated font has been acquired (S111: Yes), the CPU 11 replaces Figure 5 The font registration process shown is executed Figure 8 The font registration process (S401) is shown.
[0083] For the steps of the font registration process executed by the printer 1 of the second embodiment, refer to Figure 8 In this font registration process, the CPU 11 searches for a font ID specified by a font ID selection command (S201). Then, the CPU 11 determines whether a PCL font has been found (S202).
[0084] When it is determined that there is no PCL font (S202: No), the CPU 11 reads out the font file of the determined font (S203). Then, the CPU 11 generates a font header of the PCL font based on the read font file (S204). After S204, or when it is determined that there is a PCL font (S202: Yes), the CPU 11 registers the font header internally (S205).
[0085] Then, the CPU 11 determines whether the font data of all characters are registered in association with the font header registered in S205 (S501). When the font determined in S201 is a PCL font, the font data of all characters are registered in association with the font header registered in S205. When it is determined that the font data is registered (S501: Yes), the CPU 11 ends the font registration process and returns to the Figure 7 Printing job processing.
[0086] On the other hand, when the determined font is not a PCL font, the CPU 11 registers only the font header in S205, and does not register the font data of each character. When it is determined that the font data is not registered (S501: No), the CPU 11 generates the font data of the PCL font based on the font data of each character included in the font file read out in S203.
[0087] Specifically, CPU11 obtains the glyph ID of a character that has not been registered (S502). Then, CPU11 obtains the glyph data of the character corresponding to the obtained glyph ID from the read font file (S503). Furthermore, CPU11 generates glyph data of a PCL font based on the glyph data obtained in S503 (S504). Then, CPU11 registers the generated glyph data (S505). Similar to S314, in S505, CPU11 may also generate association information that associates the character code of the printing object with the corresponding glyph ID (the glyph ID of the glyph data generated in S504). In addition, CPU11 may also register the association information in a hash table. S503 to S505 are related to the character intermediate data generation processing of the first method (refer to Figure 6 ) is processed in the same manner as S312 to S314.
[0088] After S505, the CPU 11 proceeds to S501 to determine whether registration of all font data included in the read font file has been completed. If there is any unregistered font data (S501: No), the CPU 11 repeats S502 to S505.
[0089] After all the font data are registered (S501: YES), the CPU 11 ends the font registration process and returns to the Figure 7In addition, the font header and each font data registered by the font registration process are stored in the volatile area of the memory 12. When a hash table is created in S505, the CPU 11 can also obtain the font data corresponding to the character code by referring to the hash table.
[0090] return Figure 7 After the font registration process in S401, the CPU 11 proceeds to S102 to further acquire print data. Then, when it is determined that the acquired print data is a character code (S121: Yes), the CPU 11 acquires the glyph data corresponding to the character code of the acquired print data from each glyph data registered in the font registration process (S411).
[0091] Furthermore, the CPU 11 generates intermediate data of the character using the acquired glyph data (S412). In addition, when the glyph data corresponding to the character code is not found, the CPU 11 may generate intermediate data of a blank character, for example.
[0092] When it is determined that the acquired print data is a drawing object other than characters ( S121 : Yes), the CPU 11 generates intermediate data based on the drawing object ( S132 ).
[0093] If it is determined that a page end command has been acquired (S141: YES), the CPU 11 generates raster data for one page based on the generated intermediate data (S142). The print engine 15 executes printing for one page based on the raster data.
[0094] When it is determined that the job end instruction has been obtained (S151: Yes), the CPU 11 saves the font header and each font data of the PCL font generated in the font registration process of S401 as a font file (S421). The CPU 11 stores the font file of the PCL font in a non-volatile area of the memory 12 or a USB memory connected to the printer 1. S421 is an example of the saving process. After S421, the CPU 11 ends the print job process.
[0095] In S421, the CPU 11 generates and stores a font ID different from the font files already stored in association with the font file. In addition, for example, the CPU 11 may store the font ID in association with the font file in the font registration process (see Figure 8 ), that is, the font file of the font that is not the PCL font stores the same font ID. Alternatively, the CPU 11 may store a font ID to which information indicating that the font is the same as the original font file but in a different format is added.
[0096] As described above in detail, the printer 1 of the second embodiment, like the printer 1 of the first embodiment, generates PCL font data based on the font data of the first font information 22. Therefore, the user can use downloaded font information, for example, without considering the type of print data.
[0097] Furthermore, the printer 1 of the second embodiment generates font data for all characters and saves them as a font file. Therefore, for example, when the same font is specified in a subsequent print job, the printer 1 can read out the saved font file from the memory 12 and use it. As a result, the time spent on generating font data in the processing of subsequent print jobs can be saved, and it can be expected that printing will be faster. In addition, by generating font data for all characters, the processing algorithm becomes simpler compared to the printer 1 of the first embodiment that generates font data only for the characters used in printing.
[0098] On the other hand, the printer 1 of the first embodiment does not save the generated font data in the memory 12. In the first embodiment, since the font data of all characters may not be generated, the printer 1 can suppress errors in subsequent printing jobs by not saving them as font files. In addition, in the first embodiment, the printer 1 generates only the font data of the characters required for printing, so the processing load required for generating the font data is reduced compared to the case of generating the font data of all characters. This step is particularly effective in the case of a font with many types of characters such as Japanese fonts.
[0099] In addition, the embodiments are merely illustrative and do not limit the present invention in any way. Therefore, the technology disclosed in this specification can of course be improved and modified in various ways within the scope of its main purpose. For example, the printer 1 is not limited to a single printing function, but can also be a multifunction machine, a copier, a fax machine, etc., as long as the device has a printing function, it can be applied.
[0100] In addition, the distinction between the first font information 22 and the second font information 23 is not essential. That is, the printer 1 only needs to store font files for each font. In addition, even in the first embodiment, when the glyph data of all characters are generated during the processing of the print job, the font file of the font for which the glyph data of all characters are generated may be saved.
[0101] In addition, in the first embodiment, the font data of the characters to be printed are registered in the job and reused in the same job, but it is not necessary to reuse them. Specifically, the character intermediate data generation process of the first embodiment (see Figure 6) S301 and S302. In this case, whenever the CPU 11 designates a character as a printing object, it reads out the font data of the designated character from the font information such as the TrueType font format. Furthermore, the CPU 11 may generate and use the font data of the PCL font based on the read font data.
[0102] In addition, the printer 1 of the second embodiment saves the generated PCL font file in the non-volatile area of the memory 12 after the print job processing is completed, but it is not necessary to save it. Specifically, the print job processing of the second embodiment (see Figure 7 ) S421. In addition, the printer 1 may be capable of accepting user settings on whether to save.
[0103] In addition, the printer 1 may be capable of executing either the process of the first embodiment or the process of the second embodiment. In this case, for example, when the number of characters included in the font file is greater than a prescribed number, the process of the first embodiment may be executed, and when the number of characters included in the font file is less than the prescribed number, the process of the second embodiment may be executed. In addition, the printer 1 may be capable of accepting a user setting regarding whether to execute either the process of the first embodiment or the process of the second embodiment.
[0104] In addition, the printer 1 can process not only the print data in the PCL5 format, but also the print data in the PDF format, for example. The printer 1 can directly use the font file of the first font information 22 to draw text when processing the print data in the PDF format. In addition, the printer 1 can also use the font file of the PCL font when processing the print data in the PDF format.
[0105] Furthermore, in any flowchart disclosed in the embodiment, the plurality of processes in any plurality of steps can be arbitrarily changed in execution order or can be executed in parallel within a range where no contradiction occurs in the process contents.
[0106] In addition, the processes disclosed in the embodiments may be executed by hardware such as a single CPU, multiple CPUs, ASIC, or a combination thereof. In addition, the processes disclosed in the embodiments may be implemented in various forms such as a recording medium or method that records a program for executing the processes.
Claims
1. A printer comprising: a memory, a printing engine and a controller, characterized in that: The memory can store font data of a first format corresponding to the first printing data, The controller is configured to execute the following processing: an acquisition process in which print data is acquired; a generating process in which, when the print data acquired in the acquiring process is the second type of print data, font data of a second format corresponding to the second type of print data is generated based on the font data of the first format stored in the memory; as well as A drawing process in which the text designated by the print data is drawn using the font data in the second format generated in the generating process.
2. The printer according to claim 1, characterized in that: the controller performs a font determination process in which, when the print data acquired in the acquisition process is the second type of print data, a font designated by the acquired print data is determined; The controller is also configured as follows: The generation process is executed when the font data in the first form is stored in the memory as the font data of the font determined in the font determination process.
3. The printer according to claim 2, characterized in that: The memory can store font data of a second format corresponding to the second printing data. The controller is configured as follows: When the second-form font data is stored in the memory as the font data of the font determined in the font determination process, the generation process is not performed even if the first-form font data is stored in the memory, and the second-form font data stored in the memory is used to draw the text specified by the printing data.
4. The printer according to claim 2, characterized in that: A first font file including a plurality of font data in the first form can be stored in the memory, The first identification information can be stored as identification information of the font in association with the first font file, The print data may include a command indicating the second identification information as a command for specifying a font. The controller is configured as follows: acquiring the first identification information associated with the first font file stored in the memory, The generation process is executed when the first font file associated with the first identification information that matches the second identification information indicated by the instruction is stored in the memory.
5. The printer according to claim 1, characterized in that: A generating program can be stored in the memory, the generating program being used to generate the font data in the second format based on the font data in the first format, The controller is configured as follows: In the generation process, the font data in the second format is generated based on the font data in the first format stored in the memory using the generation program.
6. The printer according to claim 1, characterized in that: The controller is configured as follows: In the generating process, the second-format font data is generated for the first-format font data corresponding to the characters used in the print data acquired in the acquiring process.
7. The printer according to claim 6, characterized in that: The controller is configured as follows: In the generating process, a character acquiring process is executed in which characters to be used are acquired character by character from the printing data acquired in the acquiring process. Further, in the generation process, for each character acquired in the character acquisition process, if there is no font data of the second form corresponding to the target character, a character storage process is performed in which the font data of the second form generated in the generation process corresponding to the target character is stored. If the font data of the second form corresponding to the object character exists, the character storing process is not performed.
8. The printer according to claim 6, characterized in that: The controller is configured as follows: After a job based on the print data acquired in the acquisition process is completed, the font data in the second format generated in the generation process is not stored in the memory.
9. The printer according to claim 1, characterized in that: A first font file including a plurality of font data in the first form can be stored in the memory, The controller is configured as follows: In the generation process, font data in the second format is generated for a plurality of font data in the first format stored in the first font file.
10. The printer according to claim 9, characterized in that: The controller is configured as follows: After a job based on the print data acquired in the acquisition process is completed, a storage process is executed in which the font data in the second format generated in the generation process is stored in the memory.
11. The printer according to claim 10, characterized in that: The controller is configured as follows: When the second-format font data is stored in the memory as font data required for printing the print data acquired in the acquisition process, the second-format font data is read from the memory without executing the generation process.
12. The printer according to claim 1, characterized in that: The controller is configured as follows: A first font file including a plurality of font data in the first format can be received from an external device and saved in the memory, When the print data acquired in the acquisition process is the first type of print data, the text specified by the print data can be drawn using a plurality of font data of the first format included in the first font file stored in the memory. When the print data acquired in the acquisition process is the second type of print data, the generation process and the drawing process can be executed.
13. The printer according to claim 12, characterized in that: A second font file including a plurality of font data in the second form can be stored in the memory, The controller is configured as follows: When the print data acquired in the acquisition process is the second type of print data, a font data determination process is executed in which font data required for printing the acquired print data is determined. In the drawing process, the text specified by the printing data is drawn using the font data determined in the font data determination process from among a plurality of font data of the second form contained in the second font file stored in the memory, or using the font data of the second form generated by the generation process based on the font data determined in the font data determination process from among a plurality of font data of the first form contained in the first font file stored in the memory.
14. The printer according to claim 13, characterized in that: The controller is configured as follows: In the font data determination process, font data corresponding to characters used in the acquired print data is determined as font data required for printing the acquired print data.
15. The printer according to claim 13 or 14, characterized in that: The controller is configured as follows: In the drawing process, when the font data determined in the font data determination process is not included in the second font file stored in the memory, the text specified by the printing data is drawn using the second font data of the second form generated by the generation process based on the font data determined in the font data determination process among a plurality of font data of the first form included in the first font file stored in the memory.
