printer

JP2024162182APending Publication Date: 2024-11-21BROTHER KOGYO KK
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023077487
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-09
Publication Date
2024-11-21

AI Technical Summary

Benefits of technology

【0008】 本明細書に開示される技術によれば、プリンタにおいて、印刷データの種類とフォントデータの形式との組み合わせに簡単に対応できる技術が実現される。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024162182000001_ABST
    Figure 2024162182000001_ABST
Patent Text Reader

Abstract

To provide a technology that is able to easily cope with a combination of the type of print data and the format of font data, in a printer.SOLUTION: A printer 1 stores a font file including glyph data corresponding to print data in a PDF format, for example, font information in a True Type font format, in a memory 12. When the printer 1 acquires print data in a PCL5 format, the printer generates a PCL font glyph data corresponding to the print data in the PCL5 format, based on glyph data included in the font file stored in the memory 12 and corresponding to the print data in the PDF format. Further, using the generated PCL font glyph data, the printer 1 can draw a text designated in the acquired print data.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

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 technology]

[0002] Conventionally, printers capable of printing based on print data written in a page technology language have a configuration in which font information is stored, as disclosed in, for example, Japanese Patent Laid-Open No. 2003-233996. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2014-56583 A Summary of the Invention [Problem to be solved by the invention]

[0004] The format of font data may differ depending on the type of print data. Therefore, the user must prepare font data that matches the type of print data and store that font data in the printer. However, it is inconvenient to have to consider the type of print data when preparing font data. [Means for solving the problem]

[0005] A printer made to solve this problem is a printer equipped with a memory, a print engine, and a controller, wherein the memory is capable of storing font data in a first format corresponding to a first type of print data, and the controller is configured to execute an acquisition process for acquiring print data, a generation process for generating font data in a second format corresponding to the second type of print data based on the font data in the first format stored in the memory if the print data acquired in the acquisition process is a second type of print data, and a drawing process for drawing text specified in the print data using the font data in the second format generated in the generation process.

[0006] The printer disclosed in this specification acquires the second type of print data, and generates and renders font data of a second format corresponding to the second type of print data based on font data of a first format corresponding to the first type of print data stored in memory. That is, the printer can print text based on font data of the first format even for the second type of print data. Therefore, if a user stores font data of the first format in the printer, the printer can use the font even when printing based on the second type of print data. This makes it easy to use fonts without having to consider the format of the font data or the type of print data.

[0007] A printing system including the printer, a control method for implementing the functions of the printer, a computer program, and a computer-readable storage medium storing the program are also novel and useful. Effect of the Invention

[0008] The technology disclosed in this specification realizes a technology that allows a printer to easily accommodate combinations of print data types and font data formats. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a block diagram showing a schematic configuration of a printer. [Diagram 2] 10 is a flowchart showing a procedure for print job processing. [Diagram 3] FIG. 2 is an explanatory diagram showing a schematic configuration of font information in a first format. [Figure 4] FIG. 11 is an explanatory diagram showing a schematic configuration of font information in a second format. [Diagram 5] 13 is a flowchart showing a procedure for font registration processing. [Figure 6] 13 is a flowchart showing a procedure for generating character intermediate data. [Figure 7] 10 is a flowchart showing a procedure for print job processing. [Figure 8] 13 is a flowchart showing a procedure for font registration processing. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] A printer according to a first embodiment will be described in detail below with reference to the accompanying drawings. This embodiment discloses a printer capable of printing based on print data described in a page description language.

[0011] As shown in Fig. 1, the printer 1 includes a control unit 10 including a CPU 11 and a memory 12. The printer 1 also includes a user interface (hereinafter referred to as "user IF") 13, a communication interface (hereinafter referred to as "communication IF") 14, and a print engine 15. The CPU 11 is an example of a controller. The user IF 13, the communication IF 14, and the print engine 15 are all electrically connected to the control unit 10. Note that the control unit 10 in Fig. 1 is a general term for hardware and software used to control the printer 1, and does not necessarily represent a single piece of hardware actually present in the printer 1.

[0012] The CPU 11 executes various processes according to a program read from the memory 12 or based on a user's operation. Various programs and various data are stored in the memory 12. The memory 12 is also used as a working area when various processes are executed. The memory 12 may include a buffer provided in the CPU 11.

[0013] Note that an example of the memory 12 is not limited to a ROM, RAM, HDD, etc. built into the printer 1, but may be a storage medium that is readable and writable by the CPU 11. For example, an external memory such as a USB memory or HDD connected to the printer 1 via the communication IF 14, or a memory or HDD provided in a device connected to the printer 1 via the communication IF 14 are also examples of the memory 12.

[0014] 1, the memory 12 stores a print control program 21, first font information 22, second font information 23, and a generation program 24. Note that 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 from the factory. Details of each program and data will be described later.

[0015] The user IF 13 includes hardware for displaying a screen for notifying the user of information and hardware for accepting operations by the user. The user IF 13 may include a touch panel, or may be a combination of a display unit and an operation button.

[0016] The communication IF 14 includes hardware for communicating with an external device. The communication standards of the communication IF 14 are Ethernet (registered trademark), Wi-Fi (registered trademark), USB, etc. The printer 1 may be provided with a plurality of communication IFs 14 compatible with a plurality of communication standards.

[0017] Print engine 15 includes a device capable of printing based on image data by, for example, an electrophotographic method or an inkjet method. Print engine 15 may be equipped with coloring materials of multiple colors and capable of color printing, or may be equipped with coloring materials of only one color and perform monochrome printing.

[0018] The printer 1 can communicate with a server 100 via the communication IF 14, for example, as shown in FIG. 1. The server 100 may be an external device that stores font information. The printer 1 can receive a file including font information from the server 100 and store the file in the memory 12 based on a user's instruction. In addition, the user can connect a USB memory that stores font information to the printer 1, for example, to cause the printer 1 to use the font information stored in the USB memory.

[0019] Next, the operation of the printer 1 of the first embodiment will be described. The following process basically indicates the processing of the CPU 11 according to the commands written in the program. The processing by the CPU 11 also includes hardware control via the API of the operating system (hereinafter referred to as "OS"). In this specification, the description of the OS may be omitted and the operation of each program may be described. Also, "acquisition" is used as a concept that includes acquisition by request and acquisition without request. Data that has the same substantial meaning but different formats will be treated as the same data.

[0020] The printer 1 can acquire a print job and execute printing based on the acquired print job. The procedure of print job processing, including the procedure of printing based on a print job, will be described with reference to the flowchart in Fig. 2. The print job processing is executed by the CPU 11 of the printer 1 based on the print control program 21. The printer 1 may receive and acquire the print job from an external device via the communication IF 14, or may read and acquire the print job from a USB memory attached to the communication IF 14.

[0021] A print job is data indicating an image to be printed, and includes, for example, PDL data described in a page description language, and PJL data indicating various parameters related to printing. There are multiple types of PDL data included in a print job, such as the PCL5 format provided by Hewlett-Packard (registered trademark) and the PDF format. PDL data in the PCL5 format is an example of a second type of print data. PDL data in the PDF format is an example of a first type of print data. The printer 1 can identify the type of PDL data based on, for example, the PJL data.

[0022] 2 is executed when an execution instruction is received for a print job including PDL data in PCL5 format. In this specification, a description of the processing of a print job including PDL data in a format other than PCL5 format will be omitted.

[0023] In the print job process, the CPU 11 acquires 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 be a character string.

[0024] Specifically, in S101, the CPU 11 acquires font IDs associated with the font information for all fonts included in the first font information 22 and the second font information 23 stored in the memory 12. Furthermore, when font information is stored in a USB memory connected to the printer 1, the CPU 11 acquires font IDs associated with the font information stored in the USB memory.

[0025] The printer 1 can store information about each font as, for example, a font file for each font. The first font information 22 and the second font information 23 may include multiple font files. Each font file is not limited to being managed by a file system, and is information that includes multiple pieces of glyph data indicating the shape of characters for one font. Glyph data is an example of font data.

[0026] The font ID may be included in the font file, or may be stored separately from the font file in association with the font file. In addition, when the printer 1 downloads a font file from an external device, the printer 1 may generate a font ID and store the font ID in association with the font file downloaded from the external device.

[0027] The first font information 22 includes font files in which glyph data in a first format corresponding to PDF format PDL data is stored. Examples of font files including glyph data in the first format include TrueType fonts, OpenType fonts, and PostScript fonts. The font files included in the first font information 22 are examples of first font files. Note that when processing a print job including PDL data in PCL5 format, the printer 1 cannot use the font files included in the first font information 22 for printing as is.

[0028] The font file in the TrueType font format of the first font information 22 includes, for example, font information 30 configured as shown in Fig. 3. The font information 30 includes a header table 31, a character table 32, a location table 33, and a glyph table 34. The font information 30 may further include information indicating the print position and information indicating the character width for each character.

[0029] Header table 31 is a table that stores information including position information of character table 32, position information of location table 33, and position information of glyph table 34. Character table 32 is a table that associates the character code of each character with the glyph ID of the character. The character code is information that identifies each character. Location table 33 is a table that associates, for each glyph ID, the glyph ID with the position information of the glyph data corresponding to that glyph ID. The glyph ID is identification information that identifies the glyph data of each character.

[0030] The glyph table 34 is a table that stores a plurality of glyph data such as glyph data 341, 342, etc. Each glyph data is information that indicates the outline of each character, and each glyph data is assigned a unique glyph ID.

[0031] The second font information 23 includes font files in which glyph data in a second format corresponding to PDL data in the PCL5 format is stored. The font files included in the second font information 23 are an example of second font files. When processing a print job including PDL data in the PCL5 format, the printer 1 can use the font files included in the second font information 23 for printing as is. In the following, the fonts in the font files corresponding to print data in the PCL5 format are referred to as "PCL fonts."

[0032] The font file of the PCL font included in the second font information 23 includes, for example, font information 40 configured as shown in Fig. 4. The font information 40 includes a font header 41, division information 42, and a plurality of glyph data 43, 44, and so on.

[0033] Font header 41 is a header that includes a font ID and stores information about the entire font. Division information 42 stores information corresponding to, for example, header table 31 of font information 30 (see FIG. 3). Furthermore, glyph data for each character includes a glyph header and a glyph data body. Glyph header 431 is information about glyph data 43, including, for example, format information, size information, and a glyph ID. Glyph data body 432 is information indicating the outline of a character in glyph data 43, and corresponds to glyph data 341, 342, etc., of font information 30 (see FIG. 3).

[0034] That is, the glyph data included in the font file of the first font information 22 (e.g., glyph data 341 in FIG. 3) and the glyph data included in the font file of the second font information 23 (e.g., glyph data 43 in FIG. 4) are in different formats. Then, printer 1 draws text using glyph data in different formats depending on the type of PDL data included in the print job.

[0035] Returning to the description of the print job processing in Fig. 2, in S101, the CPU 11 can obtain the font ID of the font included in the second font information 23 from the font header 41 of each piece of font information 40 (see Fig. 4). On the other hand, there is a possibility that a font ID is not associated with each piece of font information 30 (see Fig. 3) included in the first font information 22. When a font ID is not associated with the font information stored in the memory 12 or the USB memory, the CPU 11 may set a font ID in S101 in association with the font with no associated font ID.

[0036] Next, CPU 11 acquires print data included in the print job (S102). S1102 is an example of an acquisition process. Then, CPU 11 determines whether or not a font ID selection command that specifies the font of the characters to be printed has been acquired based on the acquired print data (S111). The font ID selection command includes a font ID, and is a command that specifies the font to be used for printing based on the font ID.

[0037] When it is determined 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 second identification information.

[0038] The procedure of the font registration process will be described with reference to the flowchart in Fig. 5. In the font registration process, CPU 11 searches for a font ID that matches the font ID specified in the font ID selection command from among the font IDs of each font file (S201). Specifically, CPU 11 extracts the font ID that matches the font ID specified in the font ID selection command from among the font IDs acquired in S101 of the print job process. In this way, CPU 11 identifies the font specified in the print data. S201 is an example of a font identification process.

[0039] Furthermore, CPU 11 determines whether or not the fonts identified in S201 are PCL fonts (S202). For example, if multiple fonts are searched for in S201, CPU 11 determines whether or not the searched fonts are PCL fonts in S202. If one font is searched for in S201, CPU 11 determines whether or not the searched font is a PCL font in S202.

[0040] If it is determined that the PCL font is not available (S202: NO), the CPU 11 reads the font file of the font identified in S201 into a volatile area of ​​the memory 12 (S203). If the CPU 11 is unable to search for the font ID in S201 or is unable to read the font file in S203, the CPU 11 may treat it as an error or may substitute another stored font.

[0041] Furthermore, CPU 11 generates a font header for the PCL font based on the header information of the read font file (S204). CPU 11 generates a font header having a similar structure to font header 41 included in font information 40 shown in Fig. 4, for example. The font header generated in S204 includes information for associating character codes with glyph data, but does not include glyph data for each character.

[0042] After S204, or if it is determined that a PCL font is present (S202: YES), CPU 11 internally registers the font header (S205). CPU 11 registers the font header generated in S204 or the font header of the identified PCL font. After S205, CPU 11 ends the font registration process and returns to print job processing.

[0043] Returning to the description of the print job processing in Fig. 2, in the print job processing, after the font registration processing in S112, CPU 11 proceeds to S102 and acquires further print data. Then, if CPU 11 determines that the acquired print data is not a font ID selection command (S111: NO), CPU 11 determines whether the acquired print data is a character code that specifies the characters to be printed (S121).

[0044] When it is determined that the acquired print data is character code (S121: YES), the CPU 11 executes character intermediate data generation processing for each character to be printed (S122). S121 for acquiring the character code of the character to be printed is an example of character acquisition processing.

[0045] The procedure of the character intermediate data generation process will be described with reference to the flowchart in Fig. 6. The CPU 11 determines whether or not glyph data of the character to be printed, specified by the print data, is registered in the font file in which the font header is registered (S301). The registration of the font header is performed in S205 of the font registration process described above (see Fig. 5).

[0046] If the font header is not registered at the start of the character intermediate data generation process, the CPU 11 may treat 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 out the font file of the PCL font stored in the memory 12 in S301 and register the font header.

[0047] When it is determined that glyph data of the character to be printed is registered (S301: YES), the CPU 11 acquires the registered glyph data as glyph data to be used for rasterization (S302). The glyph data acquired in S302 is glyph data of a PCL font, and is glyph data of a format corresponding to print data in the PCL5 format. S302 is an example of a font data specification process.

[0048] For example, if the font searched for in S201 of the font registration process (see FIG. 5) is a PCL font, the CPU 11 can obtain glyph data for each character based on the font header registered in S205 of the font registration process. If the font is a PCL font and there is no glyph data corresponding to the character code, the CPU 11 may generate intermediate data for a blank character, for example.

[0049] On the other hand, if the font searched for 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 is not necessarily registered. If it is determined that the glyph data of the character to be printed has not been registered (S301: NO), the CPU 11 acquires a 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 that identifies each glyph data, and is also information that indicates the storage location of the glyph data of each character.

[0050] Furthermore, CPU 11 acquires glyph data of a character corresponding to the acquired glyph ID from the read font file (S312). Since the specified font is not a PCL font, the glyph data acquired in S312 is not glyph data of a PCL font.

[0051] Therefore, CPU 11 generates glyph data of a PCL font based on the glyph data acquired in S312 (S313). CPU 11 generates glyph data of a PCL font configuration by adding character format information, size information, glyph ID, etc. to the glyph data of the font in the TrueType font format acquired in S312, for example. S313 is an example of the generation process.

[0052] 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 that is called from the print control program 21 and executed.

[0053] Furthermore, CPU 11 registers the generated glyph data for one character in association with the registered font header (S314). That is, CPU 11 stores the glyph data acquired in S313 as glyph data corresponding to the character code of the character to be printed. S314 is an example of a character storage process.

[0054] By registering the generated glyph data, CPU 11 can acquire the registered glyph data in S302 of the next character intermediate data generation process. Furthermore, if registered glyph data is acquired in S302, CPU 11 does not register the acquired glyph data. In other words, when the same character is printed multiple times in one print job, CPU 11 does not need to generate or register the same glyph data each time. This reduces unnecessary processing.

[0055] After S302 or S314, the CPU 11 uses the acquired glyph data to generate intermediate data for the characters to be printed (S321). Furthermore, the CPU 11 places the generated intermediate data at an appropriate position in the intermediate data for that page. After S321, the CPU 11 ends the character intermediate data generation process and returns to the print job process.

[0056] The font header registered in S205 of the font registration process and the glyph data registered in S314 of the character intermediate data generation process are stored in a volatile area of ​​the memory 12. In other words, this information is not saved in the memory 12 after the ongoing print job is completed.

[0057] Returning to the description of the print job processing in Fig. 2, in the print job processing, after the font registration processing in S112, the CPU 11 proceeds to S102 and acquires further print data. Then, if it is determined that the acquired print data is not a character code that specifies the characters to be printed (S121: NO), the CPU 11 determines whether the acquired print data is a drawing object that indicates printing of something other than characters (S131).

[0058] When it is determined that the drawing object indicates printing other than text (S131: YES), the CPU 11 generates intermediate data other than text and places it (S132). The process of generating intermediate data other than text will not be described.

[0059] If 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). 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). S142 is an example of a drawing process.

[0060] The print engine 15 of the printer 1 can then print one page based on the generated raster data, thereby outputting a printout including text drawn in the font specified by the font ID selection command.

[0061] If it is determined that the acquired print data is not a page end command indicating the end of a page (S141: NO), the CPU 11 determines whether the acquired print data is a job end command (S151). If it is determined that the acquired print data is not a job end command (S151: NO), the CPU 11 proceeds to S102 and acquires more print data. If it is determined that a job end command has been acquired (S151: YES), the CPU 11 ends the print job process.

[0062] As described above in detail, when the printer 1 of the first embodiment executes printing based on print data in PCL5 format, it can generate glyph data of a PCL font based on the glyph data of the first font information 22 stored in the memory 12, and use this font to render text. Therefore, if font data in TrueType font format is stored in the memory 12, for example, the printer 1 can use the font data stored in the memory 12 for printing based on print data in PDF format and for printing based on print data in PCL5 format.

[0063] This allows a user to simply download a font file containing font data in TrueType font format, for example, and use the downloaded font file for printing, regardless of the type of print data. The user does not need to prepare font files in multiple formats for the same font, nor does he need to consider the type of print data.

[0064] Next, a printer according to a second embodiment will be described in detail with reference to the attached drawings. This embodiment differs from the printer 1 of the first embodiment, which registers only the font header, in that when a font other than a PCL font is specified in a print job, font information of a PCL font including not only a font header but also glyph data of each character is generated and registered. In the following, the same configurations and procedures as those of the printer 1 of the first embodiment will be briefly described with the same reference numerals as those of the first embodiment.

[0065] The procedure of print job processing executed by the printer 1 of the second embodiment will be described with reference to the flowchart of Fig. 7. When the CPU 11 of the printer 1 of the second embodiment determines that a font ID selection command specifying a font has been acquired (S111: YES), the CPU 11 executes the font registration process shown in Fig. 8 (S401) instead of the font registration process shown in Fig. 5.

[0066] The procedure of the font registration process executed by the printer 1 of the second embodiment will be described with reference to the flowchart of Fig. 8. In this font registration process, the CPU 11 searches for a font ID designated by a font ID selection command (S201). Then, the CPU 11 determines whether a PCL font has been searched for (S202).

[0067] If it is determined that a PCL font is not present (S202: NO), CPU 11 reads the font file of the identified font (S203). Then, CPU 11 generates a font header of the PCL font based on the read font file (S204). After S204, or if it is determined that a PCL font is present (S202: YES), CPU 11 internally registers the font header (S205).

[0068] Then, CPU 11 determines whether glyph data of all characters has been registered in association with the font header registered in S205 (S501). If the font specified in S201 is a PCL font, glyph data of all characters has been registered in association with the font header registered in S205. If it is determined that glyph data of all characters has been registered (S501: YES), CPU 11 ends the font registration process and returns to the print job process of FIG.

[0069] On the other hand, if the identified font is not a PCL font, the CPU 11 registers only the font header and does not register the glyph data of each character in S205. If it is determined that the glyph data is not registered (S501: NO), the CPU 11 generates glyph data of the PCL font based on the glyph data of each character included in the font file read in S203.

[0070] Specifically, CPU 11 acquires a glyph ID of a character that has not yet been registered (S502). Then, CPU 11 acquires glyph data of a character corresponding to the acquired glyph ID from the read font file (S503). Furthermore, CPU 11 generates glyph data of a PCL font based on the glyph data acquired in S503 (S504). Then, CPU 11 registers the generated glyph data (S505). S503 to S505 are the same processes as S312 to S314 in the character intermediate data generation process of the first embodiment (see FIG. 6).

[0071] After S505, the CPU 11 proceeds to S501 to determine whether or not the registration of all glyph data included in the read font file has been completed. If there is unregistered glyph data (S501: NO), the CPU 11 repeats S502 to S505.

[0072] When the registration of all glyph data has been completed (S501: YES), the CPU 11 ends the font registration process and returns to the print job process of Fig. 7. The font header and each piece of glyph data registered by the font registration process are stored in a volatile area of ​​the memory 12.

[0073] Returning to the description of the print job processing in Fig. 7, after the font registration processing in S401, CPU 11 proceeds to S102 to acquire further print data. Then, if CPU 11 determines that the acquired print data is character code (S121: YES), CPU 11 acquires glyph data corresponding to the character code of the acquired print data from among the glyph data registered in the font registration processing (S411).

[0074] Furthermore, the CPU 11 generates intermediate data of the character by using the acquired glyph data (S412). If no glyph data corresponding to the character code is found, the CPU 11 may generate intermediate data of a blank character, for example.

[0075] When it is determined that the acquired print data is a drawing object other than a character (S121: YES), the CPU 11 generates intermediate data based on the drawing object (S132).

[0076] If it is determined that a page end command has been received (S141: YES), CPU 11 generates one page of raster data based on the generated intermediate data (S142). Print engine 15 executes printing of one page based on the raster data.

[0077] When it is determined that a job end command has been acquired (S151: YES), the CPU 11 saves the font header and each glyph 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 in a USB memory connected to the printer 1. S421 is an example of a saving process. After S421, the CPU 11 ends the print job process.

[0078] In S421, CPU 11 generates and stores a font ID that is different from each font file already stored, in association with this font file. Also, for example, CPU 11 may store, in association with this font file, the same font ID as the original font file read in S203 of the font registration process (see FIG. 8), i.e., a font file of a font that is not a PCL font. Alternatively, 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 has been added.

[0079] As described above in detail, the printer 1 of the second embodiment, like the printer 1 of the first embodiment, generates glyph data of a PCL font based on the glyph data of the first font information 22. Therefore, the user can use, for example, downloaded font information without considering the type of print data.

[0080] Furthermore, the printer 1 of the second embodiment generates glyph data for all characters and saves it as a font file. Therefore, for example, if the same font is specified in a subsequent print job, the printer 1 can read the saved font file from the memory 12 and use it. This can save time required to generate glyph data in the processing of subsequent print jobs, and can be expected to speed up printing. Also, by generating glyph data for all characters, the processing algorithm is simpler than that of the printer 1 of the first embodiment, which generates glyph data only for characters used in printing.

[0081] On the other hand, the printer 1 of the first embodiment does not store the generated glyph data in the memory 12. In the first embodiment, since glyph data for not all characters has been generated, the printer 1 does not store it as a font file, thereby suppressing errors in subsequent print jobs. In the first embodiment, the printer 1 generates glyph data only for characters required for printing, so the processing load required to generate the glyph data is reduced compared to when glyph data for all characters is generated. This procedure is particularly effective for fonts with a large number of character types, such as Japanese fonts.

[0082] The embodiment is merely an example and does not limit the present invention in any way. Therefore, the technology disclosed in this specification can be improved and modified in various ways without departing from the spirit of the technology. For example, the printer 1 is not limited to a printer with a single function, but can be a multifunction machine, a copier, a fax machine, or any other device with a printing function.

[0083] Also, it is not essential to distinguish between the first font information 22 and the second font information 23. In other words, it is sufficient for the printer 1 to store a font file for each font. Even in the first embodiment, when glyph data for all characters is generated during the processing of a print job, the font file for the font that generated the glyph data for all characters may be saved.

[0084] In the first embodiment, glyph data of a character to be printed within a job is registered and reused within the same job, but it is not necessary to reuse the glyph data. Specifically, S301 and S302 of the character intermediate data generation process (see FIG. 6) in the first embodiment may be omitted. In that case, CPU 11 reads out glyph data of the specified character from font information such as a TrueType font format each time a character is specified as a print target. Furthermore, CPU 11 may generate and use glyph data of a PCL font based on the read glyph data.

[0085] Furthermore, the printer 1 of the second embodiment is described as saving the font file of the generated PCL font in a non-volatile area of ​​the memory 12 when the processing of the print job is completed, but it is not necessary to save the font file. Specifically, S421 of the print job processing (see FIG. 7) of the second embodiment may be omitted. The printer 1 may also be capable of accepting a user's setting as to whether or not to save the font file.

[0086] The printer 1 may be capable of executing both the process of the first embodiment and the process of the second embodiment. In that case, for example, if the number of characters included in the font file is greater than a predetermined number, the process of the first embodiment may be executed, and if the number of characters is not greater than the predetermined number, the process of the second embodiment may be executed. The printer 1 may also be capable of accepting a user's setting regarding which of the process of the first embodiment and the process of the second embodiment to execute.

[0087] Furthermore, the printer 1 can process not only print data in PCL5 format, but also print data in PDF format, for example. When processing print data in PDF format, the printer 1 can draw text by directly using the font file of the first font information 22. Note that the printer 1 may also be able to use a font file of a PCL font when processing print data in PDF format.

[0088] In addition, in any of the flowcharts disclosed in the embodiments, the execution order of multiple processes in any of the steps can be changed as desired or the processes can be executed in parallel, as long as no contradiction occurs in the process content.

[0089] The processes disclosed in the embodiments may be executed by a single CPU, multiple CPUs, hardware such as ASIC, or a combination of these. The processes disclosed in the embodiments may be realized in various forms, such as a recording medium having a program for executing the processes recorded thereon, or a method. [Explanation of symbols]

[0090] 1. Printer 11 CPU 12. Memory 15 Printing Engine

Claims

1. Memory, A print engine; A controller; A printer comprising: The memory includes: A first type of font data corresponding to the first type of print data is storeable; The controller: An acquisition process for acquiring print data; a generating process for generating font data of a second format corresponding to the second type of print data based on the font data of the first format stored in the memory when the print data acquired in the acquiring process is a second type of print data; a drawing process for drawing text specified in the print data using the font data of the second format generated in the generation process; It is possible to The printer that is configured to:

2. 2. The printer according to claim 1, The controller: When the print data acquired in the acquisition process is the second type of print data, a font specification process is executed to specify a font specified in the acquired print data; The controller further comprises: executes the generating process when the font data of the first format is stored in the memory as the font data of the font specified in the font specifying process. The printer that is configured to:

3. 3. The printer according to claim 2, The memory includes: a second type of font data corresponding to the second type of print data is storeable; The controller: When the font data of the second format is stored in the memory as the font data of the font specified in the font specification process, the generation process is not executed even if the font data of the first format is stored in the memory, and the text specified in the print data is drawn using the font data of the second format stored in the memory. The printer that is configured to:

4. 3. The printer according to claim 2, The memory includes: A first font file is capable of being stored, the first font file including a plurality of font data in the first format; The first font file can store first identification information as identification information of the font in association therewith, The print data may include a command indicating second identification information as a command for specifying a font, The controller: Obtaining the first identification information associated with the first font file stored in the memory; executing the generation process when the first font file associated with the first identification information that matches the second identification information indicated in the command is stored in the memory; The printer that is configured to:

5. 2. The printer according to claim 1, The memory includes: A generating program for generating font data of the second format based on font data of the first format is stored, The controller: In the generating process, the font data of the second format is generated based on the font data of the first format stored in the memory by using the generating program. The printer that is configured to:

6. 2. The printer according to claim 1, The controller: In the generating process, font data of the second format is generated for the font data of the first format corresponding to characters used in the print data acquired in the acquiring process. The printer that is configured to:

7. 7. The printer according to claim 6, The controller: In the generation process, execute a character acquisition process to acquire characters to be used one by one from the print data acquired in the acquisition process; Further, in the generation process, for each character acquired in the character acquisition process, If there is no font data in the second format corresponding to the target character, a character storage process is executed to store the font data in the second format generated in the generation process corresponding to the target character; if there is font data in the second format corresponding to the target character, the character storage process is not executed. The printer that is configured to:

8. 7. The printer according to claim 6, The controller: after a job based on the print data acquired in the acquisition process is completed, the second format font data generated in the generation process is not stored in the memory; The printer that is configured to:

9. 2. The printer according to claim 1, The memory includes: A first font file is capable of being stored, the first font file including a plurality of font data in the first format; The controller: the generating process generates font data in the second format for the plurality of font data in the first format stored in the first font file; The printer that is configured to:

10. 10. The printer according to claim 9, The controller: a storage process is executed to store the second format font data generated in the generation process in the memory after the job based on the print data acquired in the acquisition process is completed. The printer that is configured to:

11. 11. The printer according to claim 10, The controller: When the font data of the second format is stored in the memory as font data necessary for printing the print data acquired in the acquisition process, the generation process is not executed, and the font data of the second format is read from the memory. The printer that is configured to:

12. 2. The printer according to claim 1, The controller: A first font file including a plurality of font data in the first format is received from an external device and stored in the memory; When the print data acquired in the acquisition process is the first type of print data, text specified in the print data can be drawn using a plurality of font data of the first format contained 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. The printer that is configured to:

13. 13. The printer according to claim 12, The memory includes: A second font file including a plurality of font data in the second format is storable; The controller: When the print data acquired in the acquisition process is the second type of print data, a font data identification process is executed to identify font data necessary for printing the acquired print data; In the drawing process, text specified in the print data is drawn using the font data identified in the font data identification process among the plurality of font data of the second format included in the second font file stored in the memory, or using the font data of the second format generated in the generation process based on the font data identified in the font data identification process among the plurality of font data of the first format included in the first font file stored in the memory. The printer that is configured to:

14. 14. The printer according to claim 13, The controller: In the font data identification process, font data corresponding to characters used in the acquired print data is identified as font data necessary for printing the acquired print data. The printer that is configured to:

15. A printer according to claim 13 or 14, The controller: In the drawing process, when the font data specified in the font data specification process is not included in the second font file stored in the memory, text specified in the print data is drawn using the font data of the second format generated by the generation process based on the font data specified in the font data specification process among the plurality of font data of the first format included in the first font file stored in the memory. The printer that is configured to:

Citation Information

Patent Citations

  • Recording apparatus, control method of recording apparatus and program

    JP2014056583A