Program and server

Abstract

To propose suitable fonts to individual users in a system promoting use of label data.SOLUTION: A label management server 3 incorporated with a web application 36 can connect to a terminal 1 via the Internet 9. The label management server 3 can access a label DB 6 in which a plurality of pieces of label data can be registered and a font DB 7 in which a plurality of pieces of font data can be registered. When there is a font proposal request (E01), the web application 36 extracts related label data related to a specified user from the label DB 6 (E32), and determines language on the basis of a text object included in the extracted related label data (E41). The web application 36 displays, on the terminal 1, font data corresponding to the determined language from the pieces of font data registered in the font DB 7, and proposes the displayed font data (E56).SELECTED DRAWING: Figure 9

Description

[Technical Field]

[0001] The technical field disclosed in this specification relates to a program and a server used in a system that utilizes label data. [Background technology]

[0002] A conventional system for utilizing content data is known in which a server that stores content data is provided on the Internet, content data is posted from a user's device, i.e., uploaded to the server, and the content data is then downloaded to another user's device.

[0003] An example of a document disclosing the above-mentioned system is Patent Document 1. In the points management system disclosed in Patent Document 1, when photo data is uploaded from User A's PC to a WWW server and purchased by User B's PC and downloaded from the WWW server, points are added to User B, the purchaser, according to the purchase amount, and further points are added to User A, the contributor, according to the data size of the photo data when the photo data is uploaded or downloaded. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-99746 Summary of the Invention [Problem to be solved by the invention]

[0005] In recent years, there have been systems that utilize label data used to print labels on label printers as content data. In addition to providing label data, such systems may also provide various font data that can be used with the label data to increase the variety of label designs. However, it is difficult for the fonts indicated in the font data to support all languages, and many of them only support a limited number of languages. Therefore, a mechanism that can suggest suitable fonts for individual users is desirable. [Means for solving the problem]

[0006] A program made to solve the above-mentioned problems is a program executable by a server computer, the server having access to a label database and a font database, wherein a plurality of label data can be registered in the label database, the label data can include text objects, and wherein a plurality of font data can be registered in the font database; the program causes the computer to execute a transmission process, when a download request is made specifying one of the font data registered in the font database, to transmit the specified font data to a device that has requested the download; and, when a font suggestion request is made and a user is specified, the computer is further caused to execute a determination process, when a font suggestion request is made and a user is specified, to extract associated label data, which is the label data related to the specified user, from the label data registered in the label database, and determine a language based on the text objects included in the extracted associated label data; and a proposal process, when a font suggestion request is made and a user is specified, to propose, to the device that has requested the proposal, the font data corresponding to the language determined in the determination process from the font data registered in the font database.

[0007] The program having the above configuration extracts associated label data related to a specified user from the label data registered in the label database, and determines the language based on text objects included in the extracted associated label data. The program then suggests font data corresponding to the determined language from font data registered in the font database. This makes it easier for the program to suggest fonts suitable for the user.

[0008] A server, a system, an apparatus, a control method for realizing the functions of the above program, and a computer-readable storage medium storing the program are also novel and useful. [Effects of the Invention]

[0009] The technology disclosed in this specification realizes a technology that can propose a suitable font to each user in a system that utilizes label data. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is an explanatory diagram schematically illustrating a label data sharing system according to a first embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a user database. [Figure 3] FIG. 2 is a diagram illustrating an example of a label database. [Figure 4] FIG. 2 is a diagram illustrating an example of a font database. [Figure 5] FIG. 10 is a sequence diagram illustrating an example of a posting process. [Figure 6] FIG. 10 is a diagram illustrating an example of a screen transition. [Figure 7] FIG. 10 is a sequence diagram illustrating an example of a procedure for a download printing process. [Figure 8] FIG. 10 is a sequence diagram illustrating an example of a procedure for content purchase processing. [Figure 9] FIG. 10 is a sequence diagram illustrating an example of a recommended font suggestion process. [Figure 10] 10 is a flowchart illustrating an example of a language determination process. [Figure 11] FIG. 10 is a sequence diagram showing an example of the procedure of a recommended font suggestion process executed in the label data sharing system of the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] An embodiment of a program for sharing label data will be described in detail with reference to the accompanying drawings. This embodiment discloses a program that is installed in a server that can be connected to an information processing device via a network.

[0012] (First embodiment) A label data sharing system 100 (hereinafter referred to as "system 100") of the first embodiment shown in Fig. 1 is a system provided by, for example, a label printer vendor. The system 100 comprises a label management server 3 and a terminal 1, and the label management server 3 and terminal 1 are connected via the Internet 9. The terminal 1 is connectable to a label printer 2. The label management server 3 is an example of a "server." The terminal 1 is an example of a "device" and an "information processing device." The Internet 9 is an example of a "network."

[0013] 1 shows only one terminal 1 that can be connected to the label management server 3, but in reality, many terminals 1 are connected to the label management server 3. The label printer 2 may be connected to multiple terminals. Furthermore, the terminal 1 may be used by multiple users.

[0014] The label printer 2 is a device that has at least a printing function and a communication function. The label printer 2 is connected to the terminal 1 via wireless LAN communication such as Wi-Fi (registered trademark) or short-range wireless communication such as Bluetooth (registered trademark). The label printer 2 may also be connected to the terminal 1 via a wired connection using the USB communication standard.

[0015] For example, the tape that can be attached to each label printer 2 is predetermined for each model. When the label printer 2 receives a print job that includes label data, it prints based on the label data while feeding the tape and ejects the printed tape outside the machine. A label of a specified size is formed using the ejected tape.

[0016] The terminal 1 is an information processing device used by the owner or user (hereinafter referred to as "user") of the label printer 2. The terminal 1 is, for example, a smartphone, a tablet terminal, or a personal computer (PC). The terminal 1 has a controller 10 including a CPU 11 and a memory 12. The terminal 1 has a user interface (hereinafter referred to as "user IF") 13 and a communication interface (hereinafter referred to as "communication IF") 14, which are connected to the controller 10.

[0017] The label management server 3 is a server provided by the vendor of the label printer 2. The label management server 3 of this embodiment comprises a controller 30 including a CPU 31 and a memory 32. The CPU 31 is an example of a "computer." The label management server 3 comprises a user interface (hereinafter referred to as "user IF") 33, a communication interface (hereinafter referred to as "communication IF") 34, and an interface 35, which are connected to the controller 30.

[0018] Note that the controllers 10 and 30 in Figure 1 are general terms for the hardware and software used to control the terminal 1 or the label management server 3, and do not necessarily represent a single piece of hardware that actually exists in the terminal 1 or the label management server 3.

[0019] The CPU 11 of the terminal 1 and the CPU 31 of the label management server 3 execute various processes according to programs read from the memory 12 of the terminal 1 and the memory 32 of the label management server 3, respectively, and based on user operations. The memories 12 and 32 store various programs and various data. The memories 12 and 32 are also used as work areas when various processes are executed. The buffers provided in the CPUs 11 and 31 are also an example of memory. Note that examples of the memories 12 and 32 are not limited to ROM, RAM, HDD, etc. built into the terminal 1 or the label management server 3, but may also be storage media readable and writable by the CPUs 11 and 31, such as recording media, for example, CD-ROM, DVD-ROM, etc.

[0020] The user IF 13, 33 includes hardware that displays a screen for notifying the user of information and hardware that accepts user operations. For example, the user IF 13 includes a display 13a that displays information. The user IF 13, 33 may be a combination of a display that can display information and a mouse, keyboard, or the like that has an input acceptance function, or may be a touch panel that has both a display function and an input acceptance function.

[0021] The communication IFs 14 and 34 include hardware for communicating with external devices. The terminal 1 and the label management server 3 can connect to the Internet 9 via the communication IFs 14 and 34 and communicate with each other. The terminal 1 can connect to the label printer 2 via the communication IF 14. The communication IFs 14 and 34 can use communication standards such as Ethernet (registered trademark), Wi-Fi (registered trademark), and USB. The terminal 1 and the label management server 3 may be equipped with multiple communication IFs 14 and 34 that support multiple communication standards.

[0022] Various programs and data, including an operating system (hereinafter referred to as "OS") 21, a browser 45, and a print application program (hereinafter referred to as "print app") 46, are stored in the memory 12 of the terminal 1. The browser 45 and the print app 46 are also referred to as "client apps."

[0023] OS21 is a multitasking OS that can process multiple tasks in parallel by managing and switching between them. Examples of OS21 include Windows (registered trademark), macOS (registered trademark), Linux (registered trademark), iOS (registered trademark), and Android (registered trademark).

[0024] The browser 45 is a program used to browse websites. The browser 45 is launched by the user of the terminal 1, and when launched, has the function of displaying on the display 13a a web page provided by a web server (e.g., the label management server 3) indicated by a specified URL. The browser 45 may be supplied by the OS 21 vendor and incorporated into the OS 21, or may be installed on the terminal 1 separately from the OS 21.

[0025] The print application 46 is an application program provided by the vendor of the label printer 2. The print application 46 has a function to send a print job including label data to the label printer 2 and cause the label printer 2 to print based on the label data. The label printer 2 that performs printing may be registered in advance in the print application 46, or may be selected during print settings. The print application 46 may also have a function to create and edit label data on the terminal 1.

[0026] The memory 32 of the label management server 3 stores various programs and data, including a web application program (hereinafter referred to as a "web app") 36. The web app 36 is an application program that can be used on the browser of the terminal 1 without being installed on the terminal 1. The web app 36 is an example of a "program."

[0027] The terminal 1 can access the Web application 36 using the browser 45 or the browser function of the print application 46 and use the services provided by the Web application 36. For example, the Web application 36 can provide services such as registering label data uploaded, i.e., posted from the terminal 1 (hereinafter also referred to as "posted label data"), to the label management server 3 and downloading the registered label data from the label management server 3 to the terminal 1, on the condition that the terminal 1 is logged in.

[0028] The Web application 36 of this embodiment includes a front-end application 37 and a back-end application 38. The front-end application 37 and the back-end application 38 may be held by different servers.

[0029] The front-end application 37 has, for example, a web server function. The front-end application 37 can be directly accessed from the terminal 1. The front-end application 37 has prepared therein various types of page information to be displayed on the screen of the terminal 1.

[0030] The backend application 38 has a function separate from the web server function. The backend application 38 cannot generally be accessed directly from the terminal 1. The backend application 38 can call, for example, a user database (hereinafter referred to as "user DB 5") 5, a label database (hereinafter referred to as "label DB") 6, or a font database (hereinafter referred to as "font DB") 7 via the interface 35 to store and search for information.

[0031] 2, the user DB 5 can store user information about users who can use the services provided by the system 100. In the user DB 5, a record including a user ID 51, a user name 52, a password 53, a name 54, an address 55, purchase information 56, and owned points 57 is created for each user.

[0032] The user ID 51 stores information for identifying a user. The user name 52, password 53, name 54, and address 55 store the user name, password, name, and address entered by the user at the time of user registration and used when using the system 100. The user DB 5 may store personal information other than the name and address, such as an email address, postal code, or telephone number. The purchase information 56 stores, for example, information indicating content that the user has purchased and downloaded to the terminal 1. The content may be, for example, fonts, emoticons, images, or functions. The owned points 57 stores points that the user has earned. The points can be used to purchase various products, such as content and consumables. The user DB 5 is an example of a "purchase database." The purchase information may be stored in association with the user ID in a database separate from the user DB 5.

[0033] 3, the label DB 6 stores information about label data that can be provided to users. The label data stored in the label DB 6 may be data prepared in advance by the vendor of the label printer 2, or may be posted label data posted by users who use the label management server 3. In the label DB 6, a record including a label ID 61, a user ID (creator) 62, label data 63, label supplemental information 64, and a label data posting date 65 is created for each piece of label data. The user ID (creator) 62 is an example of "posting user information."

[0034] Information for identifying label data is stored in the label ID 61. The user ID of the user who posted the label data is stored in the user ID (creator) 62. For label data created by someone other than the user, the ID of an administrator may be stored in the user ID (creator) 62, or the user ID (creator) 62 may be left blank.

[0035] The label data 63 stores label data including information constituting the label data in a predetermined storage format. For example, the label data is stored in the label data 63 in XML (Extensible Markup Language) format using UTF-8 (UCS Transformation Format 8). The label data may be stored in any format other than XML, such as HTML (Hyper Text Markup Language), rich text, JSON (Java Script Object Notation), or a vendor-specific format.

[0036] The information that makes up label data includes, for example, information about the objects that make up the label data, their placement, character strings, and images. For example, label data that includes a text object includes text and font attributes. Font attributes include, for example, the font name, font ID, and character code. The character code is a unique numerical value assigned to each character or symbol so that it can be handled by a computer. The character code is not limited to UTF-8 and can be specified as a tag in XML along with the language setting. The specified character code is, for example, Shift-JIS or GB18030.

[0037] The label supplemental information 64 stores information received on the posting screen for posting label data. The label supplemental information 64 includes, for example, the label name, category, and an image showing an example of how the label is used. The label data posting date 65 stores information indicating the date the label data was posted.

[0038] As shown in FIG. 4, the font DB 7 stores information about font data available to users. For example, the print application 46 installed on the terminal 1 pre-stores common fonts. However, fonts affect the quality of labels. Therefore, when creating or editing label data using the print application 46, the use of customized fonts in addition to common fonts increases the variety of label designs. Therefore, the label management server 3 prepares a font DB 7, in which font data prepared by the vendor of the label printer 2 and font data submitted by users are registered and available for download.

[0039] In the font DB7, a record including a font ID 71, a font name 72, font data 73, a font type 74, a character set included 75, a supported language 76, supplemental font information 77, and a font posting date 78 is created for each font data.

[0040] The font ID 71 stores information for identifying font data. The font name 72 stores the name of the font entered by the user when submitting the font. The font data 73 stores font data that stores information constituting each character to be included. The information constituting a character is, for example, line thickness and character color. The font data 73 also includes a character code.

[0041] The font type 74 stores information indicating the type of font, such as a Japanese font, a Roman font, or a multi-font that supports multiple languages. The included character set 75 stores the name of the character set included in the font data. Character sets that support Japanese include, for example, hiragana, katakana, JIS Level 1 kanji, JIS Level 2 kanji, and Greek characters. Note that the included character set 75 does not have to include all character sets of supported languages. For example, the included character set 75 of a font that supports Japanese does not have to include JIS Level 2 kanji.

[0042] Supported languages ​​76 store languages ​​that the font data can support. Supported languages ​​76 may store one or more languages. Font supplemental information 77 stores information entered when posting font data. Font supplemental information 77 includes, for example, a font description introducing the font and the name or title of the designer who designed the font. Font posting date 78 stores information indicating the date the font data was posted.

[0043] Next, the operational procedures executed in the system 100 of this embodiment will be described with reference to the drawings. Note that in this embodiment, each process other than user operations basically indicates the processing of the CPUs 11 and 31 in accordance with instructions written in programs such as the print application 46, front-end application 37, and back-end application 38. In this specification, various processes performed by the controllers 10 and 30 or the CPUs 11 and 31 in accordance with programs such as the OS 21, browser 45, print application 46, front-end application 37, and back-end application 38 may be described as if each program independently performs various processes, for convenience's sake. The processing by the CPUs 11 and 31 also includes hardware control using the API (application programming interface) of the OS. In this specification, the operation of each program will be described without a detailed description of the OS. Furthermore, the term "acquire" is used as a concept that does not necessarily require a request.

[0044] (Posting process) The posting process for posting label data to the label management server 3 will be described with reference to Fig. 5. Here, the case where user A (hereinafter referred to as "poster A") posts label data will be described as an example. For ease of explanation, the reference numerals of the terminal 1 used by poster A and its components will be given the suffix "A".

[0045] As shown in Fig. 5, poster A, for example, starts the print application 46A and performs an upload operation on terminal 1A (A01). The print application 46A accesses the label management server 3 using its own browser function, and then, upon receiving, for example, an operation of the post button, requests the label management server 3 to send a posting screen using the communication IF 14A. The front-end application 37, on the condition that poster A has logged in, provides a posting screen (not shown) to the print application 46A and displays it on the display 13aA of terminal 1A. For example, upon receiving, on the posting screen displayed on terminal 1A, instructions to specify label data to be posted, input supplemental label information, and execute a new post, the front-end application 37 accepts a posting instruction from terminal 1A (A02). The posting instruction includes the label data specified on the posting screen.

[0046] When the front-end application 37 receives a posting instruction from terminal 1A via communication IF 34, it transfers the posting instruction to back-end application 38 (A03). The posting instruction includes the posted label data posted from terminal 1A, the label supplemental information entered on the posting screen, and the user ID of logged-in poster A. The back-end application 38 calls the label DB 6 using interface 35 and registers the posted label data of poster A in the label DB 6 (A04). A04 is an example of a "registration process."

[0047] 2, the backend application 38 creates a new label ID and creates a record in which the new label ID is stored in label ID 61 in the label DB 6. After that, for the record including the new label ID 61, the backend application 38 stores the user ID attached to the posting instruction, the posted label data of poster A, and label supplemental information in user ID (creator) 62, label data 63, and label supplemental information 64, respectively. In addition, the backend application 38 stores the posting date of the posted label data in label data posting date 65.

[0048] When the registration of the label data is completed, the back-end application 38 notifies the terminal 1A of "registration complete" via the front-end application 37 (A05, A06). Upon receiving the "registration complete" notification, the terminal 1A displays, for example, a message indicating that the registration of the posted label has been completed (A07). This allows the poster A to know that the posting has been completed.

[0049] In this embodiment, the posting process is performed using the browser function of the print application 46A, but for example, the terminal 1A may perform the posting process using the browser 45A. That is, the poster A may log in to the label management server 3 via the browser 45A and display the posting screen on the browser 45A.

[0050] (Download printing process) The process of downloading and printing label data will be described with reference to Figures 6 and 7. Here, we will explain an example in which user B (hereinafter referred to as "printer B") downloads poster A's posted label data to terminal 1 and prints it on a label printer. For ease of explanation, the reference numerals for terminal 1 used by printer B and its components will be given the suffix "B."

[0051] For example, when the print application 46B of the terminal 1B connects to the label management server 3 using its own browser function, it displays on the display 13aB a web page provided by the label management server 3. For example, as shown in FIG. 6(A), the web page 300 includes a login button 312, a posted label display tab 321, a content display tab 322, and a label search field 323. When the posted label display tab 321 is operated, the web page 300 switches to a screen that displays label data registered in the label management server 3.

[0052] 7, for example, the print user B operates the login button 312 to log in to the label management server 3 (B01). If the print application 46B stores the most recent login information, it may automatically use that login information to log in to the label management server 3 when connecting to the label management server 3. The timing of the login is not limited to this embodiment, and may also be when a download is requested.

[0053] For example, when label search conditions are entered in the label search field 323 shown in Fig. 6 and a search is executed, the front-end application 37 receives a label data search request from the terminal 1B (B02) and transfers the label data search request to the back-end application 38 (B03), as shown in Fig. 7. The label data search request includes the search conditions entered in the label search field 323.

[0054] The back-end application 38 accesses the label DB 6, searches for label data that includes the search criteria (B04), and passes the search results to the front-end application 37 (B05). The front-end application 37 includes the search results in a web page and transmits it to the terminal 1B (B06), which then displays it (B07).

[0055] In this embodiment, poster A's posted label data (including text objects) is found in the search and is displayed along with other label data on a web page containing the search results. When poster B selects the posted label data posted by poster A on terminal 1B, front-end application 37 accepts a request to view the selected posted label data (B11). The front-end application 37 includes content information indicating the content of the selected label data in a web page and sends it to terminal 1B, the source of the view request (B12), and displays it on display 13aB (B13). The content information includes, for example, a sample image of the posted label data, the label name, and the category. B11 to B13 are an example of a "viewing process."

[0056] The front-end application 37 passes address information indicating the address of the viewed page to the back-end application 38 (B14). The address information may include, for example, the user ID of the logged-in printer B and the label ID of the viewed posted label data. The back-end application 38 stores the received address information, the user ID of printer B, the label ID of the viewed posted label data, and the date and time of viewing in a predetermined storage area (B15). The predetermined storage area may be inside or outside the label management server 3. This leaves a history of the viewing of the submitted label data by printer B by poster A. Note that the viewing history of label data prepared by parties other than the user, such as the vendor of the label printer 2, is also left in the same way.

[0057] When the download button is operated on terminal 1B with the posted label data of poster A selected, front-end application 37 receives a download request for the selected label data from terminal 1B (B21). The front-end application 37 transfers the received download request to back-end application 38 (B22). The download request includes the label ID of the selected posted label data.

[0058] The back-end application 38 calls the label DB 6, acquires the posted label data of poster A based on the label ID attached to the download request (B23), and passes it to the front-end application 37 (B24). The front-end application 37 transmits the posted label data of poster A to terminal 1B, which is the source of the download request, via the communication IF 34 (B25). Upon receiving the posted label data via the communication IF 14B, terminal 1B stores it in a storage area for print application 46B provided in memory 12B (B26).

[0059] Thereafter, the print application 46B can display the label data downloaded to the terminal 1B on an editing screen for editing the label data and accept edits (C01). When the print application 46B accepts a print instruction (C02), it sends a print job including the edited label data to the selected label printer 2B (C03). The label printer 2B executes printing based on the print job (C04).

[0060] The print application 46B may also accept print instructions without using the edit screen. For example, the print application 46B may display a list of label data stored in terminal 1B on terminal 1B, and accept the selection of label data to be printed and the print instruction on that screen.

[0061] (Content download processing) The process of downloading content from the label management server 3 to the terminal 1 will be described. For example, if a text object included in downloaded posted label data uses a font that has not been purchased, the posted label data cannot be printed. Furthermore, label data created using the print app 46 can use fonts downloaded from the label management server 3, thereby expanding the design variations. Here, the process will be described using an example in which a user downloads a font registered in the label management server 3.

[0062] For example, when the print application 46 of terminal 1 accepts an operation on the content display tab 322 displayed on the web page 300 while logged in to the label management server 3 (B51), the front-end application 37 receives a request to search for font data from terminal 1 (B52), as shown in Fig. 7. The front-end application 37 transfers the font data search request to the back-end application 38 (B53). The request includes search conditions such as newest arrival order.

[0063] The back-end application 38 calls the font DB 7, searches for font data that matches the search criteria (B54), and passes the search results to the front-end application 37 (B55). The search results include a list of font data that was found in the search. The front-end application 37 includes the search results for font data in a web page and sends it to the terminal 1 (B56), which then displays it (B57).

[0064] When one of the font data that matches the search criteria is selected on terminal 1, front-end application 37 accepts a request to view the selected font data (B61). The front-end application 37 includes content information indicating the content of the selected font data in a web page, transmits the web page to terminal 1 that has requested the view (B62), and displays the web page on display 13a (B63). The content information includes, for example, a sample image of the font and the font name.

[0065] For example, a download button is provided on a font browsing screen that displays content information of selected font data. When the download button is operated, the front-end application 37 receives a download request from the terminal 1 specifying the font data displayed on the font browsing screen (B71). The front-end application 37 transfers the received download request to the back-end application 38 (B72). The download request includes the font ID of the specified font data.

[0066] The backend application 38 calls the font DB 7 and acquires font data corresponding to the font ID attached to the download request (B73). The backend application 38 updates the user DB 5 based on the acquired font data (B74). For example, if the acquired font data is for a fee, the backend application 38 calls the user DB 5 and adds and stores the font ID of the acquired font data to the purchase information 56 on the condition that the points required for purchase are paid from the owned points 57 associated with the user ID of the logged-in user. For example, if the acquired font data is free of charge, the backend application 38 calls the user DB 5 and adds and stores the font ID of the acquired font data to the purchase information 56 without calculating the points. B74 is an example of an "update process."

[0067] Thereafter, the back-end application 38 passes the acquired font data to the front-end application 37 (B75). The front-end application 37 transmits the font data to the terminal 1, which is the source of the download request, via the communication IF 34 (B76). B76 is an example of a "transmission process." Upon receiving the font data via the communication IF 14, the terminal 1 stores the font data in a storage area for the print application 46 provided in the memory 12 (B77).

[0068] After settling the payment for the content acquired in E73, the backend application 38 may transmit the acquired content to the terminal 1 via the frontend application 37 (B75, B76), and then include the content ID of the acquired content in the purchase information 56 of the user DB 5. In other words, the purchase information 56 may be updated after the font data is transmitted to the terminal 1.

[0069] In this way, as font data is downloaded to terminal 1, the purchase information 56 of the logged-in user is updated, and thus Web application 36 can manage downloaded font data for each user based on the purchase information in user DB 5 without accessing print application 46.

[0070] (Recommended font suggestion process) The process of proposing recommended fonts will be described with reference to Figure 9. By downloading font data that is not stored in the print application 46 from the label management server 3, the user can expand the font selection range and create a wide variety of label data. For example, the system 100 can expect to promote the use of label data by posting a wide variety of label data to the label management server 3.

[0071] However, it is difficult for fonts indicated in font data to support all languages, and many fonts support only a limited number of languages. It is virtually impossible for general users to individually grasp the supported languages ​​for font data registered in the label management server 3. Furthermore, the languages ​​used by users for label data are becoming more diverse due to inbound tourism and other factors. On the other hand, posted label data is actually created by the logged-in user, and the language used in the posted label data is likely to be used by the logged-in user when creating subsequent label data. Therefore, the recommended font suggestion process of this embodiment is configured to determine the language used by the logged-in user based on the posting history when a font suggestion request is received, and to suggest font data corresponding to the determined language.

[0072] Here, an example will be described in which a recommended font is proposed to a user C (hereinafter referred to as "proposal requester C"). For ease of explanation, the reference numerals of the terminal 1 used by the proposal requester C and its components will be given the suffix "C".

[0073] For example, the browser 45C of the terminal 1C connects to the label management server 3 using the communication IF 14C and displays the web page 300 shown in FIG. 6(A) on the display 13aC. The terminal 1C may display the web page 300 using the browser function of the print application 46C. For example, when the content display tab 322 is operated, the web page 300 switches to a screen that displays a list of content registered in the label management server 3. The content is, for example, art, fonts, and functions that can be set for objects that make up the label data. Each piece of content is displayed, for example, in order of latest arrival.

[0074] The font display area includes a font suggestion button 330. The font suggestion button 330 is an operator that accepts an instruction to suggest a font. When the front-end application 37 accepts an operation of the font suggestion button 330 on the terminal 1C, it accepts a font suggestion request from the terminal 1C (E01), as shown in FIG.

[0075] The front-end application 37 that has received the font proposal request determines whether or not the user can be identified (E11). For example, if proposal requester C is not logged in to the label management server 3, the front-end application 37 determines that the user cannot be identified (alt: Unidentifiable). In this case, the front-end application 37 requests the back-end application 38 to send a font list of popular label data (E21).

[0076] For example, the back-end application 38 can count the number of accesses for each font data item based on the HTTP access information stored in a predetermined storage area. The back-end application 38, for example, identifies a predetermined number of fonts with the highest number of accesses, extracts the font data of the identified fonts from the font DB 7, and creates a popular font list (E22). The back-end application 38 passes the created popular font list to the front-end application 37 (E23).

[0077] If the back-end application 38 can store the download history of label data and content in association with the user ID, label ID, font ID, and download date and time, for example, it may create a list of popular fonts based on the number of downloads.

[0078] The front-end application 37 includes the popular font list received from the back-end application 38 in a web page and sends it to the terminal 1C that has made the font suggestion request (E24), and displays the list of popular fonts on the browser 45C (E25). For example, thumbnail images of the fonts arranged in order of popularity are displayed on the terminal 1C.

[0079] If the front-end application 37 cannot identify the proposal requester C, it may display an authentication screen for logging in on the browser 45C and request authentication. If the Web application 36 is successful in authentication based on the user ID and password entered on the authentication screen and can identify the proposal requester C, it proceeds to processing E31, which will be described later, without executing the processes of E21 to E25. On the other hand, if the authentication fails, the Web application 36 cannot identify the proposal requester C, and therefore executes the processes of E21 to E25.

[0080] For example, if terminal 1C is used by proposal requester C and another user, there is a risk that the other user may masquerade as proposal requester C and use the services of Web application 36. Therefore, Web application 36 may always request login authentication when font suggestion button 330 is operated. Also, for example, if the Web application 36 is in a logged-in state when browsing, it may pass account information to print application 46C, and when it receives a notification from print application 46C that the account information does not match the account information set in print application 46C, it may request login authentication from proposal requester C.

[0081] In response to this, the front-end application 37 determines that the user can be identified (alt: Identifiable) if, for example, the proposal requester C is logged in to the label management server 3. In this case, the front-end application 37 requests the back-end application 38 to transmit associated label data related to the identified proposal requester C (E31). The request includes the user ID of the proposal requester C.

[0082] The backend application 38 calls the label DB 6 and extracts, as related label data, the posted label data in which the user ID of the proposal requester C is stored in the user ID (creator) 62 (E32). The backend application 38 returns a response including all of the extracted related label data to the frontend application 37 (E33). Note that if the backend application 38 is unable to extract any related label data, it returns an empty response to the frontend application 37.

[0083] The front-end application 37 that has received the response executes language determination processing (E41). In the language determination processing of this embodiment, the language is determined based on the text object included in the related label data. Steps E31 to E33 and E41 are examples of "determination processing."

[0084] The language determination process will be specifically described with reference to Fig. 10. The CPU 31 of the label management server 3 determines whether or not related label data has been acquired (S1). For example, if the response received by the front-end application 37 from the back-end application 38 includes related label data, the CPU 31 determines that the related label data has been acquired (S1: YES).

[0085] The CPU 31 analyzes the acquired associated labeled data and extracts associated labeled data including text objects (S2), and determines whether the extraction of associated labeled data including text objects has been successful (S3).

[0086] If the CPU 31 can extract related labeled data including a text object in S2, it determines that the extraction was successful (S3: YES). The CPU 31 limits the extracted related labeled data to related labeled data posted within a predetermined period (S4). For example, the CPU 31 limits the target of the judgment to related labeled data posted within one year from the current time based on the label data posting date included in the extracted related labeled data.

[0087] In the process of S4, the target of the judgment may be limited by a method other than a predetermined period. For example, the Web application 36 may limit the target of the judgment to a predetermined number of related label data items in descending order of their registration in the label DB 6, based on the label data posting date included in the extracted related label data items.

[0088] In this way, the front-end application 37 limits the related label data to be judged based on a predetermined period or number, which allows the Web application 36 to shorten the judgment time. Also, the language used for old registered related label data may differ from the language currently used by the user. In response to this, the Web application 36 increases the possibility of proposing a font that is suitable for the current usage situation of the proposal requester C by limiting the judgment target to the most recently registered related label data based on the most recent period or number.

[0089] Thereafter, the CPU 31 determines whether or not there is any related-labeled data remaining to be judged (S5). For example, if all or part of the extracted related-labeled data has been posted within a predetermined period, the number of related-labeled data after the restriction in S4 is not 0. In this case, the CPU 31 determines that there is any related-labeled data remaining to be judged (S5: YES), and proceeds to S6, which will be described later.

[0090] The CPU 31 determines the language used for each remaining determination target based on the text object included in the associated label data (S6).

[0091] For example, the CPU 31 determines the language used in the text of the post label data based on the character code included in the text object to be determined.

[0092] Specifically, if the related label data includes Chinese characters, it is not possible to determine whether the data is Chinese or Japanese based on the Chinese characters alone. Therefore, for example, if the character code included in the text object to be determined is UTF-8, the CPU 31 acquires the code positions of the characters included in the text in the Basic Multilingual Plane (BMP) one by one, and determines the language used in the related label data. For example, if the acquired characters include hiragana or katakana, the CPU 31 determines the language used in the related label data to be Japanese. On the other hand, if the acquired characters include Hangul, the CPU 31 determines the language used in the related label data to be Korean. Furthermore, if the acquired language does not include hiragana, katakana, or Hangul, the CPU 31 determines the language used in the related label data to be Chinese.

[0093] For example, if the character code included in the text object to be determined is not UTF-8, the CPU 31 may determine the language used from the character code specified in the XML. In this case, for example, if the character code is Shift-JIS, the CPU 31 determines that the language used in the associated label data is Japanese. For example, if the character code is GB13030, the CPU 31 determines that the language used in the associated label data is Chinese.

[0094] For example, if the supported languages ​​76 associated with the related label data in the label DB 6 only include a specific language, the font of the text object included in the related label data only supports that specific language. Therefore, if the supported languages ​​76 only include a specific language, the CPU 31 may determine that the specific language is the language used in the related label data.

[0095] For example, the CPU 31 may perform a dictionary search based on words in the text included in the related label data, or may perform a determination using AI, and determine the language that is most likely to be used as the language.

[0096] For example, the CPU 31 may refer to the font DB 7 based on the font ID set as a font attribute in the text object included in the associated label data, and estimate the corresponding language.

[0097] For example, if the text included in the related label data is composed only of alphabets without accent marks, the CPU 31 may determine that the language used is English. Also, if there are characters that are used only in a specific language, such as German characters with umlauts, the CPU 31 may determine that the specific language is the language used in the related label data. When the CPU 31 has determined the language for all determination targets, it ends the language determination process.

[0098] If multiple languages ​​are detected in S6, the CPU 31 may include all of the languages ​​in the determination result, or may include only one of the languages ​​in the determination result. For example, the CPU 31 may include the language with the largest number of associated label data used in the determination result. By specifying one language when multiple languages ​​are detected, the web application 36 can limit the fonts it proposes to those corresponding to the specific language, allowing it to simply propose fonts suitable for the specified user.

[0099] On the other hand, if the response from the backend application 38 does not include related label data, the CPU 31 is unable to acquire the related label data (S1: NO). Furthermore, even if the response from the backend application 38 includes related label data, if none of the related label data includes a text object, the CPU 31 determines that extraction was unsuccessful (S3: NO). Furthermore, if extraction of related label data including a text object is successful, but all of the extracted related label data has not been posted within a predetermined period, the number of related label data after the restriction is zero in S4. In this case, the CPU 31 determines that there is no related label data remaining to be judged (S5: NO).

[0100] In these cases, the CPU 31 acquires the language set in the terminal 1C (hereinafter referred to as the "set language") from the terminal 1C that has made the font proposal request (S11). Specifically, the CPU 31 uses the communication IF 34 to inquire about the set language from the terminal 1C. The terminal 1C responds to the label management server 3 with the set language set in the OS 21C. The CPU 31 can acquire the set language of the terminal 1C by receiving the response using the communication IF 34.

[0101] The label management server 3 determines the language based on the acquired set language (S12). For example, the set language acquired from the terminal 1C is determined to be the language used in the label data. After that, the CPU 31 ends the language determination process.

[0102] 9, after completing the language determination process, the front-end application 37 requests the back-end application 38 to transmit a recommended font list (E51). The request includes the language determined in E41.

[0103] The back-end application 38 creates a recommended font list based on the language specified in the request (E52).

[0104] For example, if the request specifies one language, the back-end application 38 calls the font DB 7 and reads out font data corresponding to the specified language. The back-end application 38 then creates a recommended font list based on the read out font data. For example, the back-end application 38 creates a recommended font list that includes sample images of the extracted fonts, the font name, supported languages, included character sets, descriptions, the designer's name, and so on.

[0105] For example, if a request includes multiple languages, the back-end application 38 reads corresponding font data from the font DB 7 for each language and creates a recommended font list.

[0106] The back-end application 38 passes the created recommended font list to the front-end application 37 (E53).

[0107] The front-end application 37 excludes font data that has already been downloaded by the proposal requester C from the recommended font list received from the back-end application 38 (E54). For example, the front-end application 37 calls the user DB 5 and reads out a font ID from the purchase information 56 associated with the user ID 51 of the proposal requester C. The front-end application 37 then excludes font data associated with the read-out font ID from the recommended font list. As a result, the downloaded font data is excluded from the proposal targets.

[0108] The front-end application 37 sorts the font data included in the recommended font list in order of priority for display (E55). The order of priority may be, for example, the most recent font data registered in the font DB 7, the most frequently included font data, the most popular font data, or alphabetical order.

[0109] For example, if multiple languages ​​are determined in the language determination process, the front-end application 37 may give font data corresponding to all languages ​​a higher priority than font data corresponding to some of the languages, so that the font data is displayed at a higher position.

[0110] The rearrangement method may be a method of sorting all determination targets, or a method of leaving font data with a higher priority in the recommended font list and excluding font data with a lower priority from the recommended font list. Specifically, for example, when multiple languages ​​are determined in the language determination process, the front-end application 37 may leave fonts corresponding to all languages ​​in the recommended font list and exclude fonts corresponding to some of the languages ​​from the recommended font list. This makes it easier for the web application 36 to propose fonts that are more suitable for the proposal requester C.

[0111] For example, the priority order may be such that font data that includes characters used in the submitted label data of proposal requester C is higher than font data that does not include characters. Specifically, for example, if proposal requester C has submitted submitted label data that uses JIS level 2 kanji, font data that does not use JIS level 2 kanji may be excluded from the recommended font list.

[0112] The front-end application 37 includes the recommended font list edited in E54 and E55 and the language determined in E41 in a web page, sends it to the terminal 1C that sent the font suggestion request (E56), and displays it on the browser 45C (E57). Note that if the front-end application 37 has not edited the recommended font list received from the back-end application 38 in E54 and E55, it can include the received recommended font list in the web page as is.

[0113] For example, as shown in FIG. 6(B), after operating the font suggestion button 330, a recommended font list screen 400 is displayed on the terminal 1C. A sample image 401 and a font name 402 are displayed on the list screen 400 for each font. The list screen 400 also displays a corresponding language 404 for each font based on the determined language. The fonts are also displayed in order of priority. Therefore, in response to a font suggestion request, the web application 36 can display on the terminal 1C fonts that are likely to be used by the suggestion requester C, increasing the likelihood that the suggestion requester C will be able to select a font suitable for the language to be used. E51 to E56 are an example of a "suggestion process." E56 is an example of a "notification process."

[0114] When Web application 36 receives a request to view font data when one of the font data displayed on recommended font list screen 400 is selected, it can transmit content information of the specified font data to terminal 1C and display it on display 13aC. Furthermore, when Web application 36 receives a designation of font data to be downloaded and a download request, it can transmit the specified font data to terminal 1C. These processes are similar to B61 to B63 and B71 to B76 in FIG. 8, so a description thereof will be omitted.

[0115] When setting a font on the editing screen, the print application 46C can include the font data downloaded to the terminal 1C in the font list. When the print application 46C is notified of the language determined in the language determination process by the Web application 36, the print application 46C may display the downloaded font data in the font list in priority over other font data when opening label data containing a font corresponding to the notified language and setting the font.

[0116] As described above, the Web application 36 of the first embodiment determines the language based on text objects included in the associated label data related to the logged-in user from among the label data registered in the label DB 6. The Web application 36 then proposes font data corresponding to the determined language from among the font data registered in the font DB 7. This makes it easier for the Web application 36 to propose fonts suitable for the logged-in user.

[0117] For example, it is assumed that a user in Japan will use a Japanese printing application 46 to create a Japanese label. Therefore, when a request to view fonts stored in the label management server 3 is received from the terminal 1, the label management server 3 may preferentially suggest a Japanese font that includes kanji, hiragana, and katakana. However, recently, even users in Japan are increasingly creating labels that contain a mixture of Japanese and other languages ​​to accommodate inbound tourists. Therefore, it is assumed that a user will create a label using both Japanese fonts and other language fonts while using the Japanese printing application 46. In such cases, it is desirable to suggest a font that can support both Japanese and other languages.

[0118] The Web application 36 of the first embodiment determines the language based on text objects included in the posted label data of the logged-in user, and can therefore determine the language that the logged-in user is likely to use to create labels and suggest fonts that correspond to that language to the user. In other words, if a logged-in user in Japan is creating a label that contains a mixture of Japanese and Korean, fonts that correspond to both Japanese and Korean can be suggested in preference to fonts that correspond to only one of Japanese or Korean.

[0119] Furthermore, the language used in the posted label data is likely to be used for subsequent label creation and tends to be highly useful to the user. Therefore, by determining the language from text objects included in the label data posted by the logged-in user, the web application 36 of the first embodiment is more likely to be able to suggest a font in a language that is more suitable for the user.

[0120] (Second embodiment) Next, a program according to the second embodiment will be described with reference to the drawings. As shown in FIG. 11, the program according to the second embodiment determines the language based on the browsing history. This is different from the first embodiment, which determines the language based on the posting history. Here, the differences from the first embodiment will be mainly described, and the same reference numerals as in the first embodiment will be used for the configurations and processes common to the first embodiment, and the description will be omitted as appropriate.

[0121] 11, when the backend application 38 receives a request to send related label data from the frontend application 37 (E01, E11, alt: identifiable, E31), it extracts related label data based on the browsing history (E132). For example, the backend application 38 identifies the label ID associated with the user ID of the identified user (in this embodiment, the logged-in proposal requester C) from the HTTP access information. The backend application 38 calls the label DB 6 and extracts the label data corresponding to the identified label ID as related label data.

[0122] The extracted related label data may be all label data that the proposal requester C has viewed at least once, or may be limited to a maximum of N pieces of label data that have been viewed most recently, or may be limited to label data that have been viewed M or more times.

[0123] The back-end application 38 passes the extracted related label data to the front-end application 37 (E33). In the process of E41, the front-end application 37 determines the language based on the text object of the related label data extracted based on the browsing history of the proposal requester C. The process of E41 is the same as that of the first embodiment, except that the determination is based on the related label data extracted based on the browsing history. E31, E132, E33, and E41 are examples of "determination process."

[0124] The front-end application 37 displays the font data of the font corresponding to the determined language on the terminal 1C that has made the font proposal request (E51 to E57). The processes of E51 to E56 are an example of a "proposal process."

[0125] The language used in the viewed label data is likely to be used for subsequent label creation and tends to be highly useful to the user. The Web application 36 of the second embodiment determines the language from text objects included in the label data viewed by the proposal requester C, who is the logged-in user. This increases the likelihood that the Web application 36 of the second embodiment can propose a font in a language that is more suitable for the proposal requester C.

[0126] When the front-end application 37 of the Web application 36 executes the language determination process shown in FIG. 10 at E41, it causes the CPU 31 of the label management server 3 to limit the related label data received from the back-end application 38 to those that have been specified in a viewing request by the proposal requester C within a predetermined period of time (S4), and if there are any determination targets remaining after the limiting (S5: YES), it causes the CPU 31 to determine the language based on the remaining determination targets (S6).

[0127] The front-end application 37 may cause the CPU 31 to limit, as determination targets, a predetermined number of related label data from among the related label data received from the back-end application 38, in descending order of the date and time specified in the browsing request by the proposal requester C (S4), and if determination targets remain after the limiting (S5: YES), determine the language based on the remaining determination targets (S6). The front-end application 37 may limit the predetermined period and number based on, for example, HTTP access information.

[0128] In this way, the front-end application 37 limits the targets of judgment to related label data viewed within a specified period, or to a specified number of most recently viewed items, thereby enabling the Web application 36 to shorten the judgment time. Also, since the language used in related label data with an older viewing date and time may differ from the language currently used by the proposal requester C, limiting the targets of judgment to related label data with the most recent viewing date and time, based on a specified period or number, increases the possibility of proposing a font suitable for the current usage situation of the proposal requester C.

[0129] The embodiments disclosed herein are merely examples 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 the spirit of the invention. For example, the program used by the terminal 1 when executing the posting process, download printing process, and recommended font suggestion process may be either the print application 46 or the browser 45.

[0130] For example, the font suggestion button 330 shown in FIG. 6 may be omitted. In this case, for example, when the content display tab 322 shown in FIG. 6A is operated on the terminal 1, the web application 36 may regard the request for font suggestion as having been received at E01 in FIGS. 9 and 11 and execute the processing from E11 onward. In this case, the terminal 1 displays fonts suitable for the user in response to the operation of the content display tab 322 on the web page 300. This reduces the number of operations required to display recommended fonts compared to operating the font suggestion button 330, and is therefore more user-friendly. Furthermore, for example, when the operator 331 for viewing all fonts is operated on the terminal 1, the web application 36 may regard the request for font suggestion as having been received at E01 in FIGS. 9 and 11 and execute the processing from E11 onward. In this way, when the content display tab 322 or the operator 331 serves as the font suggestion button 330, the operation of the content display tab 322 or the operator 331 is an example of a "font suggestion request."

[0131] For example, in the above embodiment, the language is determined using either the posting history or the viewing history. However, the web application 36 may weight and use both the posting and viewing histories. For example, since the language of the text included in the posted label data is likely to be a language with high usefulness, the posted label data may be given a higher priority than the label data that is only viewed.

[0132] For example, S4 in Fig. 10 may be omitted, and the backend application 38 may limit the number of related label data in E32 in Fig. 9 or E132 in Fig. 11. For example, the backend application 38 may limit the number of related label data based on a predetermined period or a predetermined number of data registered in descending order of most recent.

[0133] For example, the label DB 6 may store posted label data with an embedded user ID in the label data 63. This allows the backend application 38 to extract related label data by referring only to the label data 63 in the label DB 6, for example, at E32 in FIG.

[0134] 10, the web application 36 may perform the process of S6 by omitting S4 and S5 and determining the text objects included in all related label data. This allows all posted label data of the identified user to be subject to language determination, improving the accuracy of the determination.

[0135] For example, the Web application 36 may omit the processes of S11 and S12 in Fig. 10. However, if there is no associated label data containing a text object, the Web application 36 determines the language based on the language set in the terminal 1 (OS 21) that has made the font suggestion request, thereby increasing the possibility of suggesting a font in a language suitable for the user even if there is no associated label data containing a text object.

[0136] For example, the web application 36 may omit the process of E55 in Fig. 9. However, by displaying the fonts to be suggested according to the display priority order, the web application 36 can more easily suggest fonts that are more suitable for the user.

[0137] For example, the Web application 36 may omit the process of E54 in Fig. 9. However, since there is no need to suggest font data that has already been downloaded, the Web application 36 excludes font data that has already been downloaded by the identified user from the recommended font list. In other words, by excluding the font data from the list of fonts that are to be suggested, it becomes easier to suggest fonts that are more suitable for the user.

[0138] 9 and 11, the front-end application 37 may not notify the terminal 1C of the determined language, and may omit display of the corresponding language 404 on the recommended font list screen 400. However, by notifying the user of the language determination result along with the font proposal, the user can know which language the proposed font corresponds to.

[0139] For example, in E56 of FIG. 9 and FIG. 11, the front-end application 37 may transmit the determined language to the terminal 1C by including it in a web page so that the determined language is displayed all at once, rather than displaying it for each font.

[0140] For example, in S3 of FIG. 10, if the number of related label data including text objects exceeds a threshold, it may be determined that extraction has been successful, and if the number is equal to or less than the threshold, it may be determined that extraction has failed.

[0141] For example, in S11 of FIG. 10, if proposal requester C uses multiple terminals, the set language may be acquired from each terminal, and in S12, the most frequently used language may be determined to be the language to be used.

[0142] For example, when the language setting is changed in terminal 1C, in S11 of Fig. 10, the language setting history may be acquired from terminal 1C, and in S12, the language set in the setting history may be determined to be the language to be used. In this case, in E55 of Fig. 9, the priority of font data may be increased in descending order of the most recently set language.

[0143] For example, the user DB 5 may store the label IDs of the viewed label data and the font IDs of the font data as a viewing history in association with the user ID. In this case, the backend application 38 may call the user DB 5 at E132 in Fig. 11, identify the label ID associated with the user ID of the identified user, and extract the label data associated with the identified label ID from the label DB 6 as related label data. The viewing information may be stored in association with the user ID in a database separate from the user DB 5.

[0144] In any sequence diagram disclosed in the embodiments, any of a plurality of processes can be executed in any order or in parallel as long as no contradiction occurs in the process content.

[0145] The processes disclosed in the embodiments may be executed by hardware such as a single CPU, multiple CPUs, or ASIC, or a combination thereof. The processes disclosed in the embodiments may also be realized in various ways, such as a recording medium on which a program for executing the processes is recorded, or a method. [Explanation of symbols]

[0146] 1 device 2. Label printer 3 Label Management Server 6 Label DB 7 Font DB 9 Network 31 CPU 36 Web Apps

Claims

1. A program executable by a server computer, the server being capable of accessing a label database and a font database, the label database being capable of registering a plurality of label data, the label data being capable of including text objects, and the font database being capable of registering a plurality of font data, The computer, When a download request is made specifying one of the font data registered in the font database, a transmission process is executed to transmit the specified font data to the device that has made the download request; The computer further comprises: When a font suggestion request is made and the user is identified, a determination process of extracting associated label data, which is the label data related to the identified user, from the label data registered in the label database, and determining the language based on a text object included in the extracted associated label data; a proposal process for proposing, to the device that has made the proposal request, the font data corresponding to the language determined in the determination process from among the font data registered in the font database; Execute A program that is structured as follows.

2. The program according to claim 1, The computer, when a posting instruction specifying label data is received, a registration process is executed in which the label data uploaded in association with the posting instruction from the device that requested the posting instruction is associated with posting user information indicating the user who posted the label data, and the associated label data is registered in the label database; In the determination process, extracting, from the label data registered in the label database, the label data associated with the posting user information corresponding to the identified user as the related label data, and determining a language based on a text object included in the extracted related label data; A program that is structured as follows.

3. The program according to claim 2, In the determination process, Among the related label data containing text objects, the related label data registered in the label database within a predetermined period is selected as a target for determination, and a language is determined based on the text objects included in the related label data to be determined. A program that is structured as follows.

4. The program according to claim 2, In the determination process, a predetermined number of related label data items, which are registered in the label database in descending order of their most recent registration, among the related label data items including text objects, are selected as judgment targets, and language is determined based on the text objects included in the related label data items to be judged; A program that is structured as follows.

5. The program according to claim 1, The computer, When a viewing request is received specifying one of the label data registered in the label database, a viewing process is executed to transmit content information indicating the content of the specified label data to the device that has made the viewing request, In the determination process, extracting, from the label data registered in the label database, label data that has been specified in the browsing request by the identified user as the related label data, and determining a language based on a text object included in the extracted related label data; A program that is structured as follows.

6. The program according to claim 5, In the determination process, Among the related labeled data containing text objects, the related labeled data that has been designated in the browsing request by the identified user within a predetermined period is selected as a target of judgment, and a language is judged based on the text objects included in the related labeled data to be judged. A program that is structured as follows.

7. The program according to claim 5, In the determination process, a predetermined number of the related labeled data including text objects are selected as judgment targets in order of the most recent date and time specified in the browsing request by the identified user, and language is determined based on the text objects included in the related labeled data to be judged; A program that is structured as follows.

8. The program according to claim 1, In the determination process, When the related label data including a text object is extracted from the label database, a language is determined based on the text object included in the extracted related label data; If the related label data including a text object is not extracted from the label database, a language is determined based on a language set in the device that is the request source of the proposal request. A program that is structured as follows.

9. The program according to claim 1, In the proposal process, Proposing the font data corresponding to the language determined in the determination process to the device that has requested the proposal request by displaying the font data corresponding to the language determined in the determination process on the device that has requested the proposal request in accordance with a display priority order. A program that is structured as follows.

10. The program according to claim 1, the server can access a purchase database, and purchase information indicating downloaded font data is registered in the purchase database for each user; The computer, when the download request is received, the download request specifying one of the font data registered in the font database and specifying a user, the transmission process and the update process are executed, and in the update process, the purchase database is updated so that the font data transmitted in the transmission process is included in the purchase information corresponding to the specified user; In the proposal process, Excluding the font data included in the purchase information corresponding to the identified user from the font data to be proposed. A program that is structured as follows.

11. The program according to claim 1, The determination process is capable of determining a plurality of languages, In the proposal process, If a plurality of languages ​​are determined in the determination process, the font data corresponding to at least one of the plurality of languages ​​determined in the determination process is proposed to the device that has made the proposal request, from among the font data registered in the font database. A program that is structured as follows.

12. The program according to claim 1, The determination process is capable of determining a plurality of languages, In the proposal process, When a plurality of languages ​​are determined in the determination process, the font data corresponding to all of the plurality of languages ​​determined in the determination process among the font data registered in the font database is proposed to the device that has made the proposal request, with priority over the font data corresponding to some of the plurality of languages ​​determined in the determination process. A program that is structured as follows.

13. The program according to claim 1, In the determination process, When a plurality of languages ​​are detected based on the extracted plurality of related label data, the language having the largest number of the related label data used is determined. A program that is structured as follows.

14. The program according to claim 1, The computer, executes a notification process in which, in association with the execution of the proposal process, the language determined in the determination process is notified to the device that has made the proposal request. A program that is structured as follows.

15. A server connectable to an information processing device via a network, The server A label database and a font database are accessible, a plurality of label data can be registered in the label database, the label data can include a text object, and a plurality of font data can be registered in the font database; The server further comprises: when a download request is received from the information processing device specifying one of the font data registered in the font database, a transmission process is executed to transmit the specified font data to the information processing device; The server further comprises: When a font suggestion request is received from the information processing device and the user is specified, a determination process of extracting associated label data, which is the label data related to the identified user, from the label data registered in the label database, and determining the language based on a text object included in the extracted associated label data; a suggestion process of suggesting to the information processing device the font data corresponding to the language determined in the determination process from among the font data registered in the font database; To execute A server configured to:

Images