Distribution server

Abstract

To provide a distribution server for storing and distributing label data, and to offer technology that reduces the possibility of unintended print results from the label data uploader. [Solution] Distribution server 1 connects to network 6 and receives the selection of label data to be uploaded and the identification of the printer from distribution source PC 2 connected to network 6. Distribution server 1 obtains a list of fonts owned by the identified printer from the identified printer. If the selected label data to be uploaded contains text with a specified font, and the font specified in the text is not found in the font list obtained from the identified printer, distribution server 1 accepts the selection of one font from the font list, replaces the selected font specified in the text with the selected font, and saves the target label data.

Description

[[Technical Field]]

[0001] The technical field disclosed herein relates to a distribution server that stores and distributes label data. [[Background Art]]

[0002] Conventionally, techniques for registering and distributing label data via a distribution server are known. For example, Patent Document 1 discloses a configuration in which the server side includes a personal computer for designing labels, a label database for storing labels, and a registration number database for assigning product numbers, while the client side includes a personal computer for issuing labels, a printer, and a cutting plotter. The server and the client are connected, and the processes from label design, label issuance, to label cutting are performed consistently. [[Prior Art Documents]] [[Patent Documents]]

[0003] [[Patent Document 1]] Japanese Unexamined Patent Publication No. 2001-325084 [[Summary of the Invention]] [[Problem to be Solved by the Invention]]

[0004] When downloading and printing label data stored on a distribution server, if the printer does not have the font specified in the label data, the print result may not match the intention of the uploader of the label data, that is, the creator of the label data. [[Means for Solving the Problem]]

[0005] One embodiment of a distribution server designed to solve the above-mentioned problems is a distribution server connected to a network, wherein the distribution server identifies one of the printers connected to the network, obtains a list of fonts owned by the identified printer, and further accepts the selection of label data to be uploaded from a distribution source device connected to the network. If the target label data, which is the selected label data to be uploaded, contains text and the font specified for the text is not in the obtained list of fonts, the distribution server accepts the selection of one font from the obtained list of fonts, replaces the font of the text contained in the target label data with the selected font, and saves the target label data. If the target label data contains text and the font specified for the text is in the obtained list of fonts, the distribution server saves the target label data without changing the font of the text contained in the target label data.

[0006] The distribution server with the above configuration will, if the specified printer does not have the font specified in the text of the target label data to be uploaded, replace the font of the text in the target label data with a font selected from the fonts available to the specified printer before saving the target label data. As a result, when the target label data is printed on the specified printer, the text will be printed with the font selected on the distribution device that uploaded it. Therefore, it is expected that the possibility of printing results that are not intended by the creator of the label data will be reduced.

[0007] Another configuration of the distribution server is a distribution server connected to a network, wherein the distribution server identifies one of the printers connected to the network, obtains a list of fonts owned by the identified printer, and further accepts the selection of label data to be uploaded from a distribution source device connected to the network. If the target label data, which is the label data to be uploaded, contains text and the font specified in the text is not in the obtained list of fonts, the distribution server obtains font data for the font specified in the text from the distribution source device and transfers the obtained font data to the identified printer.

[0008] The distribution server with the above configuration will, if the specified printer does not have the font specified for the text contained in the target label data to be uploaded, obtain the font data for the text contained in the target label data from the distribution source device and pass it to the specified printer. As a result, when the target label data is printed on the specified printer, the text will be printed with the font specified for the target label data. Therefore, it is expected that the possibility of printing results that are not intended by the creator of the label data will be reduced.

[0009] The devices, control methods, computer programs, and computer-readable storage media for implementing the above-mentioned distribution server functions are also novel and useful. [Effects of the Invention]

[0010] The technology disclosed herein provides a distribution server for storing and distributing label data, which reduces the possibility of unintended printing results occurring on the label data uploader. [Brief explanation of the drawing]

[0011] [Figure 1] This is a diagram illustrating the schematic configuration of the distribution system. [Figure 2] This diagram illustrates an example of database record structure. [Figure 3] This is a sequence diagram illustrating an example of the printer registration process. [Figure 4] This is a sequence diagram illustrating an example of the procedure for uploading label data. [Figure 5] This is a diagram illustrating an example of a notification screen without fonts. [Figure 6] This is a sequence diagram illustrating an example of the procedure for a substitution process. [Figure 7] This is a diagram illustrating an example of a font selection screen. [Figure 8] This is a sequence diagram illustrating an example of the transfer process. [Figure 9] This is a sequence diagram illustrating an example of the distribution process. [Modes for carrying out the invention]

[0012] The distribution server that distributes label data will be described in detail with reference to the attached diagram. This configuration discloses a distribution system in which the distribution server, the distribution source device, and the distribution destination device are connected via a network, and label data uploaded from the distribution source device to the distribution server is distributed to the distribution destination device.

[0013] <Outline of the distribution system configuration> The distribution system (hereinafter referred to as "the system") 100 shown in Figure 1 has a distribution server 1 connected to a network 6 such as the Internet. Personal computers (hereinafter referred to as "PCs") 2, 3 and a label printer 5 are connected to the distribution server 1 so that they can communicate via the network 6. The distribution server 1 is a server managed by the vendor of the label printer 5, etc. In this configuration, the distribution server 1 has, for example, a function to store label data that represents labels and a function to distribute the stored label data.

[0014] The PC3 and the label printer 5 are provided in, for example, a store such as a supermarket. The label printer 5 is a device having at least a communication function and a printing function. The label printer 5 includes a main body operation panel 5a. The main body operation panel 5a includes an operation unit that accepts various operations such as print settings and a main body printing instruction for executing printing. The main body operation panel 5a may include a display unit that displays data.

[0015] The label printer 5 stores font data FD1, FD2, and FD3, which are information related to fonts. The font data FD1, FD2, and FD3 respectively correspond to different fonts, and may be prepared in advance in the label printer 5 or may be additionally registered. Fonts that can be registered in the label printer 5 differ depending on the model. The font data includes, for example, information indicating a font such as a font name, a font size, glyph data indicating an outline of the font, and a font color.

[0016] When the label printer 5 receives a print command for printing label data in which a font of the label printer 5 is specified, the label printer 5 performs printing in accordance with the content of the label data. If the label printer 5 does not have font data corresponding to the font specified in the label data, the label printer 5 automatically replaces the font specified in the label data with another font (for example, a default font) corresponding to the font data owned by the label printer 5 and performs printing.

[0017] The PC3 is communicably connected to the label printer 5. The communication method may be wireless or wired. A print application program (hereinafter referred to as a "print application") 32 that controls printing by the label printer 5 is installed in the PC3.

[0018] The printing application 32 is a program provided by a vendor or the like of the label printer 5, and can use a service provided by the distribution server 1. The PC 3 can download label data from the distribution server 1 via the printing application 32. Further, the PC 3 can display a setting screen for accepting print settings based on the capabilities of the label printer 5 via the printing application 32, and accept the print settings. For example, the printing application 32 can output, to the label printer 5, a print command for printing the label data downloaded from the distribution server 1 using the print settings accepted via the setting screen. Hereinafter, the PC 3 is referred to as "distribution destination PC 3".

[0019] The label printer 5 may be connected to the distribution server 1 via the distribution destination PC 3, or may be directly connected to the distribution server 1. Although FIG. 1 shows only one distribution destination PC 3 and one label printer 5, in practice, a plurality of distribution destination PCs 3 arranged in each store and a plurality of label printers 5 are connected to the distribution server 1.

[0020] The PC 2 is provided, for example, in a management company that manages the store. A label editing application program (hereinafter referred to as "label editing application") 22 for editing labels is installed in the PC 2.

[0021] The label editing application 22 can edit text and the like included in label data by using font data FD1, FD2, FD11 held by the PC 2. The font data held by the PC 2 may be registered in an operating system (hereinafter referred to as "OS") of the PC 2, may be registered in the label editing application 22 without being registered in the OS of the PC 2, or may be both of them. The distribution source PC 2 may have font data that the label printer 5 does not have, like the font data FD11, for example.

[0022] The label editing application 22 is a program provided by the vendor of the label printer 5, and can utilize the services provided by the distribution server 1. PC2 can upload the label data edited by the label editing application 22 to the distribution server 1. The uploading of label data will be described later. In the following explanation, PC2 will be referred to as "distribution source PC2".

[0023] The printing application 32 and the label editing application 22 can communicate with the distribution server 1 via their own browser functions or via the browsers of the destination PC 3 or the source PC 2. The browser may be one that is pre-installed on the OS of the destination PC 3 or the source PC 2, or it may be one that is installed separately from the OS.

[0024] The source PC2 is an example of a "source device." The destination PC3 and label printer 5 are examples of "destination devices." Label printer 5 is an example of a "printer." The source device and destination device examples may also be smartphones or tablet devices.

[0025] <Configuration of distribution server 1> Distribution server 1 is a device having at least communication and storage functions. Distribution server 1 has a front-end application 11 and a back-end application 12. The front-end application 11 and the back-end application 12 cooperate to execute processing by distribution server 1. Note that the processing by distribution server 1 may be executed by a single application. Distribution server 1 shown in Figure 1 consists of a single device, but it may also consist of a system of multiple devices.

[0026] Frontend application 11 is a web application that can be used on the browser of the information processing device connected to the distribution server 1, without being installed on the information processing device. Frontend application 11 provides, for example, a screen that accepts user input and can be displayed in a browser. Frontend application 11 contains various page information for displaying the screen on the distribution source PC 2 and the distribution destination PC 3.

[0027] The backend application 12 is a program that executes various processes in response to requests from the frontend application 11. Specifically, the backend application 12 can call various databases to store and retrieve information. Databases that the backend application 12 can access include, for example, the label database 13 (hereinafter referred to as "label DB 13") and the printer database 14 (hereinafter referred to as "printer DB 14"). In Figure 1, the label DB 13 and the printer DB 14 are located within the distribution server 1, but they may also be located outside the distribution server 1.

[0028] Label DB13 stores label data uploaded from the source PC2, etc. Figure 2(A) shows the structure of records registered in Label DB13. Label DB13 stores records for each label data, including fields that indicate the label ID, label name, label data, sample image, and update history.

[0029] The field showing the label ID stores information that identifies the label. The field showing the label name stores the name of the label. The field showing the label data stores the label data uploaded to distribution server 1. The label data includes data indicating the type, content, and layout for each object placed in the label data. For example, if the label data includes a text object, "text" is stored in the type field, and the string "condensed milk" and the specified font "font data FD11" are stored in the content field. The field showing the sample image stores the URL indicating the location where the sample image for the label is saved. The field showing the update history stores the update history of the label data.

[0030] Printer DB14 stores printer information for printers connected to network 6. Figure 2(B) shows the structure of the records registered in Printer DB14. Printer DB14 stores a record for each printer that includes fields indicating the printer ID, printer name, model name, capability information, and destination information.

[0031] The field indicating the printer ID stores information that identifies the printer, such as the serial number. The field indicating the printer name stores the name of the printer. The field indicating the model name stores the model name of the printer. The field indicating the capabilities store information that indicates the capabilities of the printer. The field indicating the capabilities store the configurable settings for each print setting item. The field indicating the destination information stores information that indicates the destination of the printer, such as the IP address.

[0032] <Explanation of streaming operation> Next, the distribution operation of system 100 will be explained. In this embodiment, the explanation will be given as an example in which the distribution server 1 saves label data containing text objects with specified fonts and distributes the saved label data to the destination PC 3 or label printer 5. The procedures and processing steps of each program described below basically represent the CPU processing according to the instructions written in each program. That is, processes such as "judgment," "decision," "acquisition," and "reception" in the following explanation represent CPU processing. CPU processing also includes hardware control using the OS API. In this specification, the description of the OS will be omitted when explaining the operation of each program. Also, "acquisition" is used as a concept that does not necessarily require a request.

[0033] <Creating label data> First, let's explain the process of creating the label data for distribution. The administrator launches the label editing application 22 on the source PC2 (A01) and creates the label data for distribution (A02).

[0034] When a label editing instruction is received, the label editing application 22 displays a label editing screen (not shown) on the source PC 2. The label editing application 22 has several objects prepared in advance, and objects are placed on the label editing screen according to user operations. The objects include, for example, text, images, frames, shapes, barcodes, and QR codes (registered trademarks). For example, an administrator creates label data that includes a text object indicating the product name and a text object indicating the capacity. The label editing application 22 may also use a database to write text and numerical values ​​to the objects.

[0035] The label editing application 22 displays a list of fonts available for use with a text object on the label editing screen when editing the text object. The label editing application 22 allows the user to select one font from the font list to use with the text object. The font list includes font data owned by the source PC2.

[0036] When the label editing application 22 receives a save command, it saves the edited label data to the source PC2 (A03). The label data is saved in format 1. Format 1 is a file format that can save information necessary for editing as well as information used for printing.

[0037] <Printer Registration> Next, we will explain the process of registering the printer. As shown in Figure 3, when the source PC2 receives a command to connect to the distribution server 1 (A11), it connects to the distribution server 1 in a communicable manner using the browser function of the label editing application 22 or the browser of the source PC2 (A12). When the distribution server 1 connects to the source PC2, the front-end application 11 provides the home screen to the source PC2 (A13).

[0038] When the front-end application 11 receives a printer registration request via a home screen (not shown) (B01), it requests the back-end application 12 to search for a printer (B02). The back-end application 12 searches for printers connected to network 6 and obtains printer information from the found printers (B03). The back-end application 12 passes the search results to the front-end application 11 (B04). The front-end application 11 provides the printer registration screen, including the search results, to the source PC 2 (B05). The front-end application 11 accepts the printer specification via the printer registration screen (B11), and upon receiving the registration instruction (B12), it requests the back-end application 12 to register the specified printer in the printer DB 14 (B13). The request is accompanied by the printer ID of the specified printer. The back-end application 12 registers the printer information, including the printer ID attached to the request, in the printer DB 14 and updates the printer DB 14 (B14).

[0039] When the backend application 12 has finished registering the label data, it notifies the frontend application 11 that the registration is complete (B15). The frontend application 11 provides the source PC2 with a screen notifying it that the registration is complete (B16).

[0040] In this configuration, the backend application 12 selected a printer from the searched printers, but it is also possible to specify a printer by manually entering destination information. Furthermore, the order in which printer registration and label data creation occur does not matter.

[0041] <Upload label data> Next, we will explain the operation of uploading label data to the distribution server 1. As shown in Figure 4, when the front-end application 11 receives an upload request via a home screen (not shown) (D01), it requests the back-end application 12 to send the printer list (D12). The back-end application 12 retrieves printer information for printers registered in the printer DB 14 from the printer DB 14 (D13). The back-end application 12 creates a printer list based on the printer information obtained from the printer DB 14 and passes it to the front-end application 11 (D14). The front-end application 11 provides the distribution source PC 2 with a printer identification screen that includes the printer list received from the back-end application 12 (D15).

[0042] When a printer is selected via the printer identification screen, the front-end application 11 accepts the selected printer as the identified printer (D21). In this configuration, the label printer 5 is identified. Once the label printer 5 is identified, the front-end application 11 provides the source PC2 with a label data selection screen for selecting the label data to be uploaded (hereinafter referred to as "target label data") (D22). The label data selection screen displayed on the source PC2 shows a list of label data stored on the source PC2 by the label editing application 22. On the label data selection screen, one label data can be selected from the label list. When one label data has been selected (D23), and the submit button on the label data selection screen is operated, the front-end application 11 accepts a label upload instruction (D24).

[0043] The frontend application 11 requests the backend application 12 to register the label data (D25). The frontend application 11 attaches the printer ID of the label printer 5 selected on the printer identification screen to the registration request. The frontend application 11 also retrieves the target label data selected via the label data selection screen from the label editing application 22 and attaches it to the registration request.

[0044] The backend application 12 retrieves destination information corresponding to the printer ID attached to the registration request from the printer DB 14, connects to the label printer 5 based on the retrieved destination information, and retrieves a font list (D26). For example, the backend application 12 retrieves a font list showing font data FD1, FD2, and FD3 from the label printer 5. By retrieving the font list from the label printer 5, the backend application 12 can include fonts distributed to the label printer 5 after shipment in the font list for selection, thus increasing the flexibility of font selection.

[0045] Furthermore, if the distribution server 1 has a font list for each printer model, the backend application 12 may identify the model of the label printer 5 by matching the printer ID attached to the registration request with the printer DB 14 and obtain the font list for the identified model. By obtaining the font list held by the distribution server 1, the font list can be obtained even when the label printer 5 is offline.

[0046] The backend application 12, which obtained the font list, determines whether the font specified in the text included in the target label data attached to the registration request is present in the font list obtained in D26 (D27).

[0047] For example, if the target label data includes a text object and that text object specifies font data FD1 or font data FD2 owned by the label printer 5, the backend application 12 determines that the font specified in the text included in the target label data is in the font list. If the font specified in the text included in the target label data is in the font list (alt: present), the backend application 12 registers the target label data in the label DB 13. The backend application 12 may save the label data in the label DB 13 in the first format, or it may convert it to a second format different from the first format and save it in the label DB 13. The backend application 12 that has registered the label data notifies the source PC 2 of the completion of registration via the frontend application 11 (D81, D82).

[0048] On the other hand, for example, if the target label data includes a text object and that text object specifies font data FD11 that the label printer 5 does not have, the backend application 12 determines that the font specified in the text included in the target label data is not in the font list. If the font specified in the text included in the target label data is not in the font list (alt: none), the backend application 12 notifies that the font specified in the text included in the target label data is not available on the destination label printer 5 (D41). The notification includes the font ID of the font data FD11 that is not available on the destination label printer 5. The frontend application 11 provides the source PC2 with a font missing notification screen (D42).

[0049] In other words, if the specified printer does not support the font specified in the label data, the printer may convert the font during printing, potentially resulting in a label that does not match the creator's intent. Therefore, distribution server 1 notifies the specified printer that the font specified in the label data is not available.

[0050] Figure 5 shows an example of the font missing notification screen D1. The font missing notification screen D1 displays a message notifying that the target label data specifies a font that is not available on the destination label printer 5, along with the first button SW11, the second button SW12, the third button SW13, and the fourth button SW14. The first button SW11 is an operator that accepts a continue command to continue uploading. The second button SW12 is an operator that accepts a cancel command to cancel uploading. The third button SW13 is an operator that accepts a replace command to replace the font. The fourth button SW14 is an operator that accepts a transfer command to transfer the font.

[0051] As shown in Figure 4, when the front-end application 11 receives a continue instruction in response to the operation of the first button SW11 (D51), it requests the back-end application 12 to continue the upload (D52). The back-end application 12 registers label data specifying a font that is not available at the distribution destination in the label DB 13 without replacing the font (D53). The back-end application 12, having registered the label data, notifies the distribution source PC2 via the front-end application 11 that the registration is complete (D81, D82).

[0052] When the front-end application 11 receives a replacement instruction in response to the operation of the third button SW13 (D61), it requests the back-end application 12 to replace the font (D62). The back-end application 12 performs a replacement process to replace the font specified in the label data according to the replacement request (D63). After registering the label data in the label DB13 during the replacement process, the back-end application 12 notifies the distribution source PC2 via the front-end application 11 that the registration is complete (D81, D82). The replacement process will be described later.

[0053] When the front-end application 11 receives a transfer instruction in response to the operation of the fourth button SW14 (D71), it executes the transfer process (D73). When the label data is registered by the back-end application 12 during the transfer process, and the front-end application 11 receives notification from the back-end application 12 that the registration of the label data is complete (D81), it notifies the source PC2 that the registration is complete (D82). The transfer process will be described later.

[0054] Furthermore, when the front-end application 11 receives a cancel command in response to the operation of the second button SW12, it terminates the upload without registering the label data in the label DB13.

[0055] <Replacement process> The replacement process described above will now be explained. As shown in Figure 6, when the backend application 12 receives a replacement request, it passes the font list obtained in D26 of Figure 4 to the frontend application 11 (D101). The frontend application 11 provides a font selection screen based on the font list to the source PC2 (D102).

[0056] Figure 7(A) shows an example of the font selection screen D6. The font selection screen D6 displays an image of the target label data IM61, a font selection field ST61, and an apply button SW61. When the pull-down button in the font selection field ST61 is operated, a list of fonts L61 obtained from the label printer 5 is displayed. For example, the font list L61 displays font data FD1, FD2, and FD3 owned by the label printer 5, and one font can be selected from the font data FD1, FD2, and FD3.

[0057] As shown in Figure 6, when the apply button SW61 is pressed with one label data selected, the front-end application 11 accepts the font selection (D103) and requests the back-end application 12 to perform the replacement (D104). The execution request includes the font ID of the selected font.

[0058] The backend application 12 connects to the label printer 5 and retrieves font data associated with the font ID attached to the execution request from the label printer 5 (D105). For example, if font data FD3, which is not present on the source PC2, is selected from the font list retrieved from the label printer 5, the backend application 12 retrieves font data FD3 from the label printer 5. Note that although Figure 6 shows the backend application 12 directly retrieving font data FD3 from the label printer 5, the backend application 12 may also retrieve font data FD3 from the label printer 5 via the frontend application 11.

[0059] The backend application 12 replaces the font specified in the text contained in the target label data with the font corresponding to the acquired font data FD3 (D106). The backend application 12 generates a preview image of the label data with the replaced font (D111). The backend application 12 passes the generated preview image to the frontend application 11 (D112).

[0060] The frontend application 11 provides a preview screen containing a preview image to the source PC2 (D113). Figure 7(B) shows an example of the preview screen D7. The preview screen D7 displays a preview image IM71 of the label data in which the font has been replaced from font data FD11 to font data FD3, a submit button SW71, and a back button SW72.

[0061] As shown in Figure 6, when the front-end application 11 receives a posting instruction in response to the operation of the posting button SW71 (D114), it requests the back-end application 12 to register the label data indicated by the preview image IM71 (D115). The back-end application 12 registers the replaced label data with the font replaced in the label DB13 (D116).

[0062] Furthermore, if the back button SW72 is pressed, the front-end application 11 returns to the previous screen.

[0063] <Transfer process> The transfer process described above will now be explained. As shown in Figure 8, the front-end application 11, upon receiving the transfer instruction, requests the label editing application 22 to send font data that the label printer 5 does not possess (D202). The request includes the font ID attached to the notification from the back-end application 12 in Figure 4, D41. For example, if the target label data specifies font data FD11 that the label printer 5 does not possess, the front-end application 11 requests the transmission of font data FD11.

[0064] The label editing application 22 reads font data FD11, which corresponds to the font ID attached to the request, from among the font data FD1, FD2, and FD11 held by the source PC 2, and sends it to the front-end application 11 (D203). The front-end application 11 transfers the received font data FD11 to the label printer 5 (D205). The label printer 5 installs the received font data FD11. As a result, when the label printer 5 prints label data in which font data FD11 is specified, it is possible to print without replacing the font data FD11.

[0065] When the front-end application 11 has finished transferring the font data FD11 to the label printer 5, it notifies the label editing application 22 that the transfer is complete (D207). The front-end application 11 then requests the back-end application 12 to register the uploaded label data in the label DB 13 (D211). Upon receiving the registration request, the back-end application 12 registers the label data in the label DB 13, which includes the uploaded text object and specifies a font corresponding to the font data FD11 in the text object (D212). Note that the registration of the label data may be performed before the transfer of the font data.

[0066] <Distribution to PC3> Next, we will explain the process of distributing label data to the destination PC3. Here, we will explain using the example of distributing label data in response to a distribution request from the destination PC3. When the destination PC3 receives an instruction to connect to the distribution server 1 (F01), it connects to the distribution server 1 using the browser function of the print application 32 or its own browser (F02). The front-end application 11 of the distribution server 1 provides the home screen to the destination PC3 (F03).

[0067] When the frontend application 11 receives a download request via the home screen (G01), it requests the backend application 12 to send a list of labels (G11). When the backend application 12 receives the request to send the list of labels, it reads the label data from the label database 13 (G12). The backend application 12 generates a list of labels based on the label data read from the label database 13 and passes it to the frontend application 11 (G13). When the frontend application 11 receives the list of labels, it provides the download screen containing the received list of labels to the destination PC3 (G14).

[0068] The print application 32 accepts the selection of a label data to be downloaded when one label data is selected from the label list on the download screen (G21). When the front-end application 11 receives the download instruction (G22), it requests the back-end application 12 to distribute the label data (G23). The label data distribution request includes the label ID of the selected label data and the destination information of the destination PC 3, which is the source of the download request. When the back-end application 12 receives the distribution request, it reads the label data associated with the label ID attached to the request from the label DB 13 (G24). The back-end application 12 distributes the read label data to the destination PC 3 according to the destination information attached to the distribution request (G25). The print application 32 on the destination PC 3 saves the received label data (G27). Alternatively, the back-end application 12 may distribute the label data to the destination PC 3 via the front-end application 11.

[0069] In the above explanation, the receiving PC3 received the label data in response to user operation, but it is also possible to automatically download the specified label data at predetermined times, such as when the printing application 32 is launched, or at regular intervals, such as every few hours.

[0070] Alternatively, the distribution server 1 may directly distribute the label data to the label printer 5. For example, the label printer 5 may download the label data from the distribution server 1 in response to an operation on the main unit's control panel 5a, or it may download the label data from the distribution server 1 at a pre-configured timing. In this case as well, the distribution server 1 may either have the backend application 12 directly distribute the label data to the label printer 5, or it may distribute it via the frontend application 11.

[0071] Furthermore, the distribution server 1 may push the label data to the designated destination PC 3 or label printer 5 at the timing set on the distribution server 1.

[0072] <Printing label data> For example, if the printing application 32 receives a print command to print downloaded label data, it generates a print command instructing the printer to print based on the downloaded data and sends it to the label printer 5. The label printer 5 prints the label data according to the print command.

[0073] For example, the label printer 5 stores the label data distributed from the distribution server 1, and when it receives the specification of the distributed label data and a print command via the main unit's operation panel 5a, it performs printing based on the label data.

[0074] If label data to be printed is created using a font that is not available on label printer 5 and is delivered to label printer 5, label printer 5 will automatically replace the missing font with the default font available on label printer 5 before printing. Therefore, the print result may not conform to the intentions of the label data creator.

[0075] However, if the distribution server 1 replaces any fonts not present in the label printer 5 with fonts available in the label printer 5 when the label data is uploaded, and then distributes the label data with the replaced fonts to the label printer 5, the label printer 5 can print the distributed label data without replacing the fonts. Since the distribution server 1 can accept the selection of fonts to be replaced, it can be expected that the printed result of the label data with replaced fonts will conform to the creator's intentions.

[0076] Furthermore, if the distribution server 1 transfers font data for fonts not present in the label printer 5 to the label printer 5 when the label data is uploaded, the distribution server 1 can save the uploaded label data without replacing the fonts and distribute it to the label printer 5, and the label printer 5 can print the distributed label data without replacing the fonts.

[0077] As described above, in the above embodiment, if the identified label printer 5 does not have the font specified for the text included in the target label data to be uploaded, the distribution server 1 replaces the font of the text included in the target label data with a font selected from the fonts available to the identified label printer 5 before saving the target label data. As a result, when the target label data is printed on the identified label printer 5, the text will be printed with the font selected on the distribution PC 2 that uploaded the data. Therefore, it is expected that the possibility of printing results that are not intended by the creator of the label data will be reduced.

[0078] Furthermore, if the identified label printer 5 does not possess the font specified for the text contained in the target label data, the distribution server having the above configuration will obtain the font data for the text contained in the target label data from the distribution PC 2 and pass it to the identified label printer 5. As a result, when the target label data is printed by the identified label printer 5, the text will be printed using the font specified for the target label data. Therefore, it is expected that the possibility of printing results that are not intended by the creator of the label data will be reduced.

[0079] The embodiments disclosed herein are merely illustrative and do not limit the present invention in any way. Therefore, the technology disclosed herein can naturally be improved and modified in various ways without departing from its essence. For example, the layout and content of each screen are not limited to the embodiments described above.

[0080] For example, the distribution server 1 may perform either font replacement or font data transfer, but not both.

[0081] For example, D111 to D113 in Figure 6 may be omitted. However, the distribution server 1 allows the uploader to choose whether or not to save the label data by displaying a preview of the font-replaced text on the uploading PC 2, and the label data can be saved with the font intended by the uploader.

[0082] For example, in the above embodiment, the distribution server 1 obtained the font data necessary for font replacement from the identified label printer 5, but the font data may also be held by the distribution server 1. However, by obtaining the font data of the selected font from the identified label printer 5, it is possible to reliably replace it with a font that the identified label printer 5 can print.

[0083] For example, if distribution server 1 has font data, distribution server 1 may check whether it has font data of its own and then decide whether or not to obtain the font data from the identified label printer 5.

[0084] For example, in the above embodiment, when uploading label data, the printer was identified from the printers registered in the printer DB14, but the printer could also be identified manually by entering destination information, etc. However, it becomes easier to identify the printer by registering the printers to be delivered to in the printer DB14 in advance and then identifying the printer from among them.

[0085] For example, in the above embodiment, the uploader was given the option to replace the font via the font absence notification screen D1. Alternatively, the font could be replaced without accepting an option to replace the font. However, the distribution server 1 can avoid replacing fonts unintentionally by replacing the font in response to an acceptance of the option to replace the font.

[0086] For example, in the above embodiment, the uploader was given the option to transfer the font data via the font-less notification screen D1. Alternatively, the font data could be transferred without accepting an option to transfer it. However, the distribution server 1 can avoid transferring font data unintentionally by transferring the label data to the identified label printer 5 in response to receiving an option to transfer the font data.

[0087] In any sequence diagram disclosed in the embodiments, any multiple processes can be executed in any order or in parallel, provided that no inconsistencies arise in the processing content. For example, in the above embodiment, as shown in Figure 4, the printer was identified before the label data was selected, but the label data could also be selected before the printer was identified.

[0088] The processes disclosed in the embodiments may be executed by a single CPU, multiple CPUs, hardware such as an ASIC, or a combination thereof. Furthermore, the processes disclosed in the embodiments can be implemented in various forms, such as a recording medium or method that stores a program for executing the process. [Explanation of Symbols]

[0089] 1 Distribution Server 2. Source PC 3. Distribution destination: PC 5 Label printers 6 Network

Claims

1. A distribution server connected to a network, The aforementioned distribution server is Identify one of the printers connected to the aforementioned network, Obtain a list of fonts owned by the identified printer, The aforementioned distribution server further: The source device connected to the aforementioned network accepts the selection of label data to be uploaded. If the target label data, which is the selected label data to be uploaded, contains text, and the font specified for the text is not in the retrieved list of fonts, the system accepts the selection of one font from the retrieved list of fonts, replaces the font of the text contained in the target label data with the selected font, and saves the target label data. If the target label data contains text and the font specified for the text is present in the acquired list of fonts, the target label data is saved without changing the font of the text contained in the target label data. A distribution server configured in this way.

2. A distribution server as described in claim 1, The aforementioned distribution server is If the target label data contains text and the font specified for the text is not found in the acquired list of fonts, the font of the text contained in the target label data is replaced with the selected font, and then the text with the replaced font is displayed on the distribution device. Subsequently, upon receiving a save instruction transmitted from the distribution source device, the target label data is saved. A distribution server configured in this way.

3. A distribution server as described in claim 1, The aforementioned distribution server is From the identified printer, obtain a list of fonts owned by the identified printer. A distribution server configured in this way.

4. A distribution server as described in claim 3, The aforementioned distribution server is If the target label data contains text and the font specified for the text is not found in the acquired list of fonts, font data indicating the selected font is acquired from the identified printer, and the font of the text contained in the target label data is replaced with the selected font based on the acquired font data. A distribution server configured in this way.

5. A distribution server as described in claim 1, The aforementioned distribution server is Multiple printers connected to the aforementioned network can be registered. The system identifies one of the printers connected to the network by receiving a selection of one of the registered printers from the distribution source device connected to the network. A distribution server configured in this way.

6. A distribution server as described in claim 1, The aforementioned distribution server is If the target label data contains text and the font specified for the text is not found in the acquired list of fonts, the system accepts a choice to replace the font or not, and in response to the acceptance of the choice to replace the font, it accepts a choice of one font from the acquired list of fonts, replaces the font of the text contained in the target label data with the selected font, and saves the target label data. A distribution server configured in this way.

7. A distribution server as described in claim 1, The aforementioned distribution server is After saving the target label data, which includes the text with the replaced font, the saved target label data is distributed to the identified printer. A distribution server configured in this way.

8. A distribution server as described in claim 1, The aforementioned distribution server is After saving the target label data, which includes the text with the replaced font, the device receives a delivery request from a delivery destination device, which is a different device from the distribution source device, specifying the saved target label data. The target label data specified in the received distribution request is distributed to the distribution destination device. A distribution server configured in this way.

9. A distribution server as described in claim 1, The aforementioned distribution server is If the target label data contains text and the font specified in the text is not found in the acquired list of fonts, the system accepts an option to choose whether or not to transfer the font data to the printer. In response to receiving the selection to transfer font data to the printer, the distribution source device obtains font data for the font specified in the text, transfers the obtained font data to the identified printer, and saves the target label data. If the selection to transfer font data to the printer is not accepted, the system accepts the selection of one font from the acquired list of fonts, replaces the font of the text contained in the target label data with the selected font, and saves the target label data. If the target label data contains text and the font specified for the text is present in the acquired list of fonts, the target label data is saved without changing the font of the text contained in the target label data. A distribution server configured in this way.

10. A distribution server connected to a network, The aforementioned distribution server is Identify one of the printers connected to the aforementioned network, Obtain a list of fonts owned by the identified printer, The aforementioned distribution server further: The source device connected to the aforementioned network accepts the selection of label data to be uploaded. If the target label data, which is the selected label data to be uploaded, contains text, and the font specified in the text is not in the acquired list of fonts, the font data of the font specified in the text is acquired from the distribution source device, and the acquired font data is transferred to the identified printer. A distribution server configured in this way.

11. A distribution server as described in claim 10, The aforementioned distribution server is If the target label data contains text and the font specified in the text is not found in the acquired list of fonts, the system accepts a choice of whether or not to transfer font data to the printer. In response to the acceptance of the choice to transfer font data to the printer, the system acquires font data for the font specified in the text from the distribution source device and transfers the acquired font data to the identified printer. A distribution server configured in this way.

Images