KR20090092158A - System and method of font management - Google Patents

Abstract

A system and method of font management are provided to make effective operation with file system is possible. A font information management unit(111) includes font related information and performs registration, renewal, and deleting the font related information. A font file administration unit(112) manages the font file which is transformed in order to fit for the inspection environment which can do the simulation. A font format conversion administration unit(113) converts the font file in order to fit for the inspection environment can simulate. A schedule management unit(114) manages the supplying font whether or not to the contents service and the constant related to the font inspection.

Description

Font management system and method {System and method of font management}

 The present invention relates to a font operation management system and method, and more particularly, to efficiently manage assets of fonts that are applied and sold in a digital device environment such as a web environment or a mobile device.

 When the MCP (Main Contents Provider), which currently provides font services, tries to add a new site or service to which fonts are applied, it requests a web font modification for each CP provided by creating a font, and then inspects all fonts by font size. It takes a lot of time, manpower and money.

There is a business inefficiency of manually delivering the fonts to be uploaded by CP to each individual company and manually receiving the completed files and inspecting them manually, and at the same time, quality errors and time delays caused by manual font distribution. This will occur.

Therefore, in terms of CP supplying a product (font), the quality of the product cannot be completely trusted, and there is a problem in that each CP does not recognize an item to be specifically inspected because the criteria for font inspection are insufficient. In addition, since the history of the file worked when adding the URL due to the service addition is not maintained, the service URL is added to the other file instead of the work done on the last file. In addition, service may occur.

As such, it is expensive and very inconvenient if the technical standardization of font inspection of MCP that distributes fonts is expensive, which is not only for MCP, but also for CP.

First, fonts created by a particular company are based on the specific system and inspection criteria used by that company. This is a waste of time and money and less reliable by using fonts of the same format that are not organized according to other companies' systems and inspection standards.

Second, there are no regulations and standards when constructing URLs for security in fonts and there is no environment to systemize and manage them, resulting in a problem of reducing font quality while performing simple and repetitive tasks.

At present, the web font service has a small burden on CPs for font updating due to the increase of URLs, but the number of font types is increasing exponentially. The increase in work loads new and additional URLs. In addition, the original source is not properly managed during the conversion process of the font, the problem is that you can continue to carry on the existing problem by importing the error file instead of converting to the final file. have.

There is little need for management system for font service in web or mobile environment, but standardized management of exponentially increasing fonts is required to increase CP and service large number of fonts to meet various customers' needs.

In addition, this work creates a burden on both sides of MCP and CP when both service URLs are added, and also leads to a decrease in font quality and reliability due to frequent domain additions and changes. Until this added, there was a problem in that the inconvenience of being unable to use the purchased font in a new service.

The present invention is to solve the problems of the prior art as described above is equipped with a system for verifying the quality of the font through the font operation management system and embedding the URL in the web font for the font license range within the font operation management system The present invention provides a font operation management system and its method for database management to enable efficient operation with a file system.

As a first aspect for achieving the above object, the present invention, after the inspection of the font registered from the CP (Contents Provider) and the inspection history during the font inspection process and the inspection of the font itself is completed wired and wireless A font management server including converting a format of the font file to match a corresponding content service providing environment of a main contents porvider (MCP) providing a content service through a network; And receiving the converted font file from the font management server and providing the font file to the corresponding content service server to which the font is to be applied, and the device type, the content service type, the application area within the content service, and the font to which the font is applied are applied. Characterized in that it comprises a font operating server for performing management related to the operation of the font including at least one of the service quantity record.

As a second point of view for achieving the above object, the present invention provides a font file from a CP (Contents Provider) to which a registration authority is granted for a font file configured according to a font implementation type suggested by an MCP (Main Contents Provider). And receiving font operation information related to a font and registering the same in a font information management unit. (b) converting the registered font file into a file format suitable for the inspection environment and storing it in a font file management unit upon receiving a request for proceeding with a font inspection process from a CP for the registered font file; (c) after the font file format is converted to match the inspection environment, loading the font file in which the format is converted, and then proceeding with the font inspection process through a inspection item manager which manages inspection items for the font; (d) recording and managing the inspection history of the font through the font inspection process through an inspection history management unit; (e) if the verification of the registered font through the font verification process is completed, storing the final file in which the verification is completed, in the font file management unit; And (f) converting the format of the font file through a font format conversion management unit so as to be suitable for an environment to which an actual font is applied by loading the final file whose inspection has been completed from a font file management unit through a search history management unit. It is characterized by.

The present invention improves the quality of fonts and manages the database of the history of font services by systematically managing the quality and license management of font assets through the operating system. And can be used as various basic data when establishing a strategy.

 In addition, system simplification and reliability of the font generation and inspection process, which has been done by hand, are increased.

Both MCP and CP can check fonts in a systematic way on the system, which can significantly lower the error rate.

In addition, by adding and updating the URL that the web font will be serviced on the system, it is possible to easily convert the file, thereby improving the font font coping ability of the web font and extending the service area to various environments such as the digital device environment including mobile. Becomes possible.

In case of MCP, it is possible to reduce the time, manpower and cost of font inspection after requesting fonts from CPs, and provide the inspection criteria and environment to CP side clearly, thus reducing the burden of MCP on the inspection work. Can give

In case of CP, the records from font registration to inspection are recorded in the database, and statistical analysis on this can be used as data for establishing strategy for future services. In addition, CP provides a database for analyzing error patterns. It plays a role to reduce the occurrence of errors by systematically managing errors that occur frequently in the font production process.

1 is a block diagram showing the configuration of a font operation management system.

2 is a diagram illustrating an operation relationship between a font operation management server and an MCP and a CP.

3 is a block diagram illustrating a schematic process of CP and MCP tasks for fonts to be applied to a web-based content service.

4 illustrates an embodiment of a font checking process.

Figure 5 is a flow diagram illustrating an embodiment of taking a pattern of grips and checking for errors.

6 is a flow diagram illustrating one embodiment of a process on a system for inspection before embarking on an actual inspection.

7 is a flowchart illustrating an embodiment of code inspection.

8 is a flowchart illustrating an embodiment of sentence inspection.

9 is a flowchart for converting a font to suit a service.

FIG. 10 is a diagram illustrating a screen for checking individual characters according to individual codes.

11 is a view showing a screen for checking each code.

Fig. 12 is a view showing the inspection screen for each size.

FIG. 13 is a diagram illustrating an embodiment in which a size is selected and inspected for each size.

14 is a diagram illustrating an embodiment of a simulation screen for an actual service screen.

15 illustrates an embodiment of a simulation screen in a mobile device environment.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

While the invention allows for various modifications and variations, specific embodiments thereof are illustrated in the drawings and will be described in detail below. However, it is not intended to be exhaustive or to limit the invention to the precise forms disclosed, but rather the invention includes all modifications, equivalents, and alternatives consistent with the spirit of the invention as defined by the claims.

1 shows a configuration of a font operation management system.

That is, the font operation management system 100 according to the present invention associated with the content service server 130 includes a font operation server 120 and a font management server 110 as main components, and the DB server 140 in addition. , File server 150 may be configured to include all.

The font management server 110 includes a font information management unit 111, a font file management unit 112, a font format conversion management unit 113, a schedule management unit 114, an inspection item management unit 115, an inspection history management unit 116, and a URL. Among the modules such as the management unit 117, the authority management unit 118, the contract management unit 119, and the service management unit, all the management units may be included or only some of the management units may be included, depending on the system implementation direction. You may.

In general, the font management server 110 receives the font from the CP, inspects the quality of the font and manages the history thereof. In addition, it regulates the usage (font, web, mobile, other devices, etc.) for the font service, and manages the usage range according to the usage.

The management of the scope of use manages the list of URLs to be served by the web font when the font is a web font, and manages the history of URL embedding and updating. In the case of a mobile font, a license for the mobile environment is embedded in the font and the history is managed. In the case of other digital devices, like the web and mobile fonts, the use range and limits of the fonts are managed in a database and the histories are managed.

Looking at the details, the font information management unit 111 included in the font management server 110 is a font name, font category, font-related image name, font price, font service availability, font service provision period, font style, font Font-related information such as author, font authoring company, font authoring date, font registration date, font update date and font deletion date, and the like, may be implemented to execute a task of registering, updating and deleting such information.

The font file management unit 112 may convert the original file of the font provided from the CP, a font file converted to fit the inspection environment that can be simulated based on the environment in which the font service is to be provided, a final font file that has been inspected, and the final font file. From the font file, it is possible to manage the font file converted in accordance with the content service environment to which the font is to be applied and the image file associated with the font.

The font format conversion management unit 113 converts the font file to match the inspection environment that can be simulated based on the environment in which the font service is provided for the font registered from the CP. Type1, Type3, Open Type Font (OTF), One or more of the font types of CID (Character Identifier Font), TTF (True Type Font), and EOT (Embedding Open Type) may be selected or automatically generated as needed, and the search history manager 116 may be searched for. The final font file is checked from the font file management unit to convert the font file into a format suitable for the content service environment to which the font is to be applied.

In addition, when the font registered from the CP is applied to the web-based inspection environment, the font format conversion management unit 113 performs a font inspection test URL provided by the system before converting the font file format for the inspection of the font. It is automatically embedded in the font.

In addition, when the font registered from the CP is applied to the web-based content service, the inspection history management unit searches for the final font file that has been inspected from the font file management unit, and then the corresponding web-based content selected by the CP from the URL management unit. The service URL may be automatically embedded in each font and then converted into a font file in a format suitable for a content service environment.

The schedule manager 114 manages a schedule related to font provision to a content service and font inspection for a font provision service. That is, the registration schedule from the CP for the font providing service to be executed, the inspection schedule, the re-registration and re-examination schedule due to the rejection of registration in case of an error in the inspection process, and the schedule in which the font is applied to the actual content service. It can be implemented to include and manage items.

The inspection item management unit 115 generates a font file converted for the inspection environment that can be simulated based on the environment in which the font service is to be provided, and then proceeds to the inspection process. When each code check and font form a sentence, the sentence can be configured to examine whether the appearance of the fonts fits harmoniously in the sentence, and the operation environment check to simulate by providing the actual device environment of the content service to which the font is applied.

This inspection process can be further subdivided and added as necessary, and the inspection type can be selected and selectively executed.

The inspection history management unit 116 manages errors of the font checked during the inspection process and sequentially manages the file in which the inspection process is recorded and the files in which the inspection is completed.

The URL manager 117 manages the URL for the web-based content service to be provided with the font registered from the MCP.

 The authority management unit 118 includes information on access rights related to the access from the CP and the MCP and the use of the system, and thus the authority of the CP and the MCP is approved.

 The contract manager 119 may be implemented to manage contract contents such as contract period, contract details, security contents, revenue distribution, and fee settlement management between the MCP and the CP.

The service manager may be implemented to include information about the type of content service to which the font is applied and the device environment.

The font operation server 130 actually manages the use of fonts in Internet services, such as web pages or bulletin boards, such as blogs or mini homepages provided by Internet content service servers such as Naver, Daum, and Cyworld. Server. The service provided by the content service server of the present invention collectively includes not only a service based on the Internet but also a content service based on various environments to which fonts are applied.

That is, the font management server 120 receives the converted font file from the font management server 110 and provides the font file to the corresponding content service server to which the font is to be applied, and also the device type, content service type and content service to which the font is applied. The application area and the font are applied to record the quantity of services, etc., to implement management of the operation of the font.

In addition, it manages the content service information including each device information provided by the MCP content service and the font information to be applied to the content service, and transmits the corresponding font file to the content service server of the MCP through the wired or wireless network.

If the content service of the MCP is a web-based content service, it manages the content service information including the URL and the font information to be applied to the content service, and transmits the corresponding font file to the content service server of the MCP through a wired / wireless network. May be

In the case of a web-based service, the content service server 130 obtains user information and information on a font selected through the user terminal from a user terminal connected to the content service server and displays the selected font at a designated place from the user. In the case of not providing a web-based service, the server may be configured to redistribute the received fonts to be adapted to an environment, such as a device to which the font is applied, or to be applied to additional devices.

Referring to the relationship between the font management server 120 and the font management server 110 of the present invention, the font registered in the font management server 110 is converted into a format suitable for each service environment and data on which service will be serviced. It is implemented to pass the font to the operation server 120.

The font operation server 120 receives and operates the fonts to be serviced, that is, fonts that have been converted to meet the quality check and service format from the font management server 110, and various environments such as digital devices including web and mobile devices. The service will be provided according to its characteristics.

While the font management server 110 manages the quality and assets of the fonts for the sale of the fonts and the user's use of the fonts, the font operation server manages the services related to the font operation and the fonts are located on any part of a device. Operational management is performed on how much (eg, the number of content services to which the font has been applied) has been applied.

2 is a view illustrating the role and relationship between a font management server and a font management server included in a font operation management system of the present invention, CP, and MCP, and FIG. 3 shows a relationship between an MCP and a CP for a font to be applied to a web-based content service. One embodiment of a business process is shown. In case of MCP and CP, each authority can be flexibly changed according to the situation. Both MCP and CP can be implemented to be authorized to proceed with the inspection.

As shown in FIG. 3 and FIG. 4 illustrating the font inspection process, the CP accessing the font operating system (S410) grants the font upload authority when the system access date matches the font upload schedule according to information obtained from the schedule database table. give. The CP is authorized to upload the font produced in the TTF format (S420). The format of the original file, which is an upload file of the CP, can be uploaded to a file of various formats as well as the TTF shown in FIG.

Simultaneously upload the font and register the font operation information such as font name, font English name, font concept, image thumbnail of font to be serviced, font style, service category and so on in the database.

In this case, the registered data is interlocked with the real service database and applied in the real service environment.

If the font is normally registered, the CP goes through the inspection process. The CP enters the verification process, checks the font name and font information, and clicks the item to be inspected. At this time, in order to proceed with the font check to the web, the web font embedded with the URL of the CP site is automatically generated (S430). If the format of the uploaded TTF file is not correct or the input information does not match the information of the font to be inspected, an error message is output and the verification process is converted into a companion process. The returned CP checks the font file and contents information and uploads the modified file or information again to proceed with the inspection process. If the CP does not re-upload or update the file or information within the inspection schedule, the font content is excluded from the service. It can also be implemented by imposing a penalty in accordance with the policy.

When the test URL is embedded in the above, the CP enters the result of the inspection history into the database through the inspection process in the system automatically or by user input. At this time, if an error occurs in the font, the font is re-created and goes through the above process again. If the error of the font does not occur, the inspection process is successfully completed (S440 ~ S470).

As shown in FIG. 5, if the format and information of the uploaded font are correct, the pattern check of the font glyph is performed. The glyph pattern check is performed on the system to determine whether the pattern of the font area in each glyph area matches the pattern of each glyph. Each code has a pattern of glyphs, and the coordinates and information of the glyphs are obtained through the glyph index, and the glyph information of the font uploaded through the CP is compared with the coordinates of the code through the XOR operation (S510). If the coordinate value comparison is out of the allowable range in the system (S520), an error message is output (S530), or the inspector can inspect only the glyph in error.

If the font and the information are registered properly, the system creates a web font by embedding the URL of the inspected web environment. The web font automatically generated by the system is displayed in the inspection item. At this time, the generated web font is stored in the examiner's temporary folder. The font file in the server system is encrypted and stored, and the file system in the system where the original file is located and the file system of the server in which the generated web fonts are encrypted are not directly accessible. This ensures security so that other CPs do not download or intercept other CP's font files in the server.

By the above process, the original TTF file is converted into a web font file incorporating the URL of the operating system and automatically generated. The generated web font is loaded into the inspection processing item in the operating system. When the CP clicks on the inspection item, the web font is loaded in the inspection item.

When the web font is normally generated, the inspection process is performed after selecting the inspection item as shown in FIG. 6. The inspection process is largely divided into code inspection, sentence inspection, and operational environment inspection.

All inspection screens have the option of selecting a font size and provide output for all inspection screen sheets. This provides an environment where you can see the representation of the font in the printer environment, not just the font quality on the monitor.

Items that can be inspected when checking the code are composed of Unicode Korean, Variable English, Half-width English, Full-width English, KS Special Characters, KS Additional Special Characters, and Empty Source.

Unicode Hangul is again classified into the following code items.

That is, AC, AD, AE, AF, B0, B1, B2, B3, B4, B5, B6, B7, B8, B9, BA, BB, BC, BD, BE, BF, C0, C1, C2, C3, C4, C5, C6, C7, C8, C9, CA, CB, CC, CD, CE, CF, D0, D1, D2, D3, D4, D5, D6, D7, and Unicode Hangul is 11,172 characters. Hangul complete code is 2,350 characters. Chinese characters are 4,850.

The system supports 11,172 characters of Unicode Hangul, and provides a 2,350 character inspection sheet and a 4,850 character inspection sheet according to the characteristics of the service.

All items of Unicode Hangul can be loaded at one time or classified as above code items. The reason for classifying the code items as above is that when the Unicode items consisting of 11,172 characters are loaded at one time, it becomes difficult to check the history of the inspection by giving the inspector a cognitive burden.

Figure 6 illustrates one embodiment of a process of preprocessing on a system for inspection before entering the actual inspection, wherein the code classification stores the web font in a user's Internet temporary file via a style sheet designation code within the HTML file and the HTML document. Get the code for each glyph in the file and parse it into the corresponding webfont file. In order to load a web font in an HTML file, the URL address of the web font file generated in the cascade style sheet (CSS) and the URL of the font file providing account in which the HTML is displayed must be embedded in the web font.

In addition to the above method, it is possible to express a check font on a web page using a basefont tag and a special HTML tag.

The inspector may visually inspect the inspection item loaded on the system according to the code classification. Visually inspect and record the items of completion and return in the database when there is a problem. If a detailed record is needed in connection with the inspection, the content of the code item is recorded in the database in text form. The recorded information is used to manage the history of the font later. In addition, the inspection environment may be implemented to provide an environment that can be inspected even offline by providing each print sheet.

When visually inspecting the quality of fonts loaded on the system, missing glyphs are treated as blanks, and the glyphs corresponding to the code and the glyphs to be inspected on the system are loaded at the same time to determine whether there is an error for the missing glyphs. Can be.

When the code check ends, the process goes to the sentence check as shown in FIG. In the sentence inspection, a sample sentence in the system may be taken, and the screen may be provided by applying a corresponding font to the HTML document. In addition, sentence inspection consists of a combination of Korean, English, special characters, Korean / English / special characters, and direct input. In sentence review, the harmony of each glyph and whether the space between the stems, stems, widths, and lines are appropriate are visually inspected. If there is a broken character in the example, record the error in the database. In addition, it is recorded in the database whether or not the tracking, stem, line width, and line width are appropriate as a whole.

When the sentence is completed, the inspector simulates the use of the font in the actual service environment as shown in FIG. In the case of FIG. 9, after the font inspection process is completed, the font is converted in accordance with the service type. In this case, the font is converted into a format suitable for web, mobile, and other digital devices according to the service type.

For web fonts, for example, if you want to use fonts on your blog or mini homepage such as Cyworld or Naver, try to simulate fonts in the same environment as Cyworld mini homepage or blog environment. Check whether there is no problem in the overall service design or design flaw when the font is actually serviced through the WISWIG (What you see is What you get: Web editor) editor on the same environment as the service system. . Mobile fonts provide the same environment as the mobile environment to check if there are any font problems in the real environment such as web font simulation.

When a modification to the font file occurs, register the font on the system again. After re-registering the font, retry the above verification process. If a problem does not occur in the inspection process, the font is changed to a format for servicing.

The system goes through a process of converting the format according to the purpose of use of the font. Convert the font to be used in the actual service environment. At this time, the inspection is completed and the final uploaded TTF file is converted into a format for web or mobile environment.

The font to be used in the mobile environment is converted to the TTF font file into the mobile format font by calling the mobile font conversion function. In other words, the font whose quality is over is the format of the mobile font in the case of the font to be serviced in the mobile environment. The font conversion process will be performed. Font conversion work for the font service environment of each mobile phone manufacturer is performed in the system. The font is registered in the conversion process and the administrator selects a format suitable for the mobile phone device environment in which the font will be served. The font conversion processor goes through the process of converting the font to suit the service environment. The converted font is actually subjected to a simple inspection process to verify that the font is converted for the mobile phone environment. After that, the font of the mobile format that has been inspected is transferred to the mobile font operating server.

The font to be used in web environment gets URL item of font to be serviced from database before changing to web font format. The MCP manager stores and updates the list of URLs to be embedded for each service on the system. In addition, since the number of fonts and the service status are serviced by the database, the system can manage the font service.

When the font is checked, the CP selects and adds a list of URLs to be served to the font. The font management server embeds the input URL list into a TTF file and converts it into a web font. To do this, you need to manage the URL in the database.

After creating the font, check if the web font is running at the URL that should be actually served. The font management system allows the font file to be loaded by font notation such as CSS in the HTML file in the URL environment. The CP checks whether the web font works properly in the service URL. If there is a URL that does not work or there is a missing URL, go back to the font conversion and creation process and proceed to the font creation.

If the URL is correctly embedded and generated in the web font, the CP requests the MCP for approval. If the checks for all inspection items are not databased, the system checks all inspection items and prints a message asking for approval. If data for all inspection processes is stored in the database, the CP requests the MCP for approval.

The MCP receives the fonts that the CP registers on the system and undergoes the verification process and converted to the service format. After receipt, the MCP checks on the MCP management screen whether the CP has gone through the inspection process properly.

When the MCP clicks check the CP's inspection process history, the system reports and prints the inspection history of the CP in the database. On the MCP system, the same inspection menu as the CP is provided, so that the inspection screen of the CP can be examined in the same way as the MCP.

The MCP checks the inspection history of the CP, checks whether the font is created in accordance with the service environment format, and returns the request for correction if the item that does not meet the inspection item criteria is approved when the MCP inspects it. do.

After the CP checks the returned content, the content is corrected again and re-registered after the inspection process as described above. After confirmation, the font and product information are sent to the actual service server. In the actual service server, the font can be applied or sold.

The above process can be applied not only to web fonts and mobile fonts, but also to font services in formats suitable for various digital devices. When the inspection process is completed, not only the conversion to web or mobile font format, but also to fonts of a format applicable to embedded software as well as various handheld devices such as DMB and navigation are possible. This conversion is performed by the operation of the font conversion engine on the system, not by hand.

In order to perform the above process, the present invention includes a font inspection item, a font inspection history, a service URL item management, a URL management embedded in a font, a schedule management, a companion history, a category management, an operator management, and an authority management item. .

The file server manages font files and font-related image files. The font file consists of the original file and the font file created by converting it to the service environment.

If an error occurs that does not match the inspection process procedures and items, record it in the database. Rewrite the TTF file for the code or statement that caused the error and go to the start of the verification process.

Checked items are stored in the database, the history related to font check is recorded and the URL is checked before the final service to make sure there are no missing URLs for the service.

CP and MCP can check various statistical data related to font error through the system and can check the data on the number of error glyphs and time according to the inspection period through the statistical system. Statistical reports bring items such as inspection status and error occurrence rate by inspection item, service category (web, mobile, PDA,…).

For example, in a case where a font implementation form is presented from a Main Contents Provider (MCP), the presented font implementation form may be an outline and / or a bitmap. Of course, other font types may be possible.

In the case of outline fonts, the appearance of characters is represented with a function curve. When displaying or printing a font, a process of first converting the information into dots is required. As a result, the output speed will be slower, but even if the screen is displayed or printed in large sized characters, it can be printed in clean and high quality characters without being distorted like bitmap fonts. However, if a small size character is created in a function, the character may not be displayed cleanly due to an error, and it may take time, so a small size screen display may use a bitmap font. When the outline font is displayed or printed on the screen, a change to a dot image is called 'rasterize' and the part of executing the outline font is called a rasterize processor (RIP).

Bitmap font is a simple structure that expresses characters as a set of dots after copying the structure of the output device. Since the Raseter operation is performed in memory, the bitmap font is displayed quickly in one-to-one correspondence with the image memory of the output device. It is used for display. The character is represented by coding 1 and 0 in the rectangular grid of the bit corresponding to the character size. However, due to the nature of the digital data represented by 0 and 1, when geometrical transformations such as enlargement, reduction, rotation, and tilting, the shape is distorted and aliasing appears. Be prepared. As a result, bitmap screen fonts need to register as many sizes as possible, which increases the amount of data. Bitmap fonts take the form of a computer that cuts out a sequence of bits of memory and arranges them horizontally and arranges them vertically by a certain number.

In the case of the CP, the font may be configured according to the above-described description of the MCP, or according to another font type. For the font file, the font file and the font may be associated with the font file from a CP (Contents Provider) to which registration authority is granted. Receives font operation information and registers it to the font information management unit. Upon receiving a request for proceeding the font inspection process from the CP with respect to the registered font file, the registered font file is converted into a file format suitable for the inspection environment and the font file management unit is converted into the font file management unit. Will be saved.

The inspection environment is generated through a web page or by a plug-in, an ActiveX program, a mobile or other OS-based program, or embedded software.

Afterwards, the font file format is one or more of the following font types: Type1, Type3, Open Type Font (OTF), Character Identifier Font (CID), True Type Font (TTF), and Embedded Open Type (EOT). After the conversion, the font conversion process is performed through the inspection item management unit which manages the inspection items for the font after loading the font file in which the format is converted, and the inspection history for the font through the font inspection process is checked through the inspection history management unit. When the inspection is completed for the registered font through the font inspection process, the final file is stored in the font file management unit.

Through the above process, the file whose final inspection is completed is loaded from the font file management unit by searching the inspection history management unit, and the format of the font file is converted through the font format conversion management unit so as to suit the environment in which the actual font is applied.

If the font is actually applied to the digital device, the font file is registered in the font conversion process and a format suitable for the digital device type is selected. Then, the device font conversion function is called to check the completed font file. Converts to device format font.

If the format of the font file is converted so that the font is adapted to the actual application environment as described above, the font file is transmitted to the content service server of the MCP according to a schedule registered from the MCP or CP.

When registering a font produced by the CP without the font implementation type suggested by the MCP, the font is received from the CP (Contents Provider) granted the registration authority and font operation information related to the font according to the font implementation form. The registration information is registered in the information management unit. When the font inspection process request from the CP is received for the registered font file, the registered font file is converted into a file format suitable for the inspection environment and stored in the font file management unit.

After the font file format is converted to match the inspection environment, the font inspection process is performed through the inspection item management unit which manages inspection items for the font after loading the converted font file. During the font inspection process, The inspection history for the font of the recording and management is made through the inspection history management unit. Thereafter, when the verification of the registered font is completed, the final file in which the verification is completed is stored in the font file management unit, and a screen configured to select one or more of various devices is displayed, wherein any one of the displayed various devices is displayed. When the selection signal for the above is received from a person who has authority to select or execute the format, the format for the selected device is automatically selected.

After the completion of the inspection, the final font file stored is searched by the inspection history management unit to configure a list of the final font files stored in the font file management unit, and the display is performed. When at least one of the displayed final font file list is selected, The font file format is converted by the font format conversion management unit to match the selected font file with a preselected device format.

FIG. 7 is a diagram illustrating a process of displaying and inspecting a glyph divided by code in a code inspection, and separately checking whether the proper glyph is included in the position of each code for the font inspection that was inspected according to the font creator's own inspection criteria. Check code and glyph errors with a single click on the web without writing an inspection sheet. When checking the error of code and glyph, the glyph is properly divided by code to reduce the error rate of code inspection due to cognitive overload.

In the case of code review, it is possible to inspect selectively or all items including at least one of Unicode, variable English, half-width English, full-width English, KS special character, KS additional special character, and empty sender.

In the case of FIGS. 10 to 13, examples of code checking are shown.

FIG. 10 shows a screen for checking each letter according to an individual code, and shows a screen for confirming whether a comparison glyph and a manufactured glyph at a corresponding position of each glyph match.

FIG. 11 shows an inspection screen for each code, in which codes of which inspection is completed can be confirmed by changing an image of a button, and the operation history can be recorded and statistically calculated by a report provided in the system.

In the case of FIG. 12, a print screen for checking an error of a font at each size may be provided as a screen for checking the size of each sheet.

FIG. 13 is a screen illustrating an example in which a font size is selected to be inspected for each size. The font size can be selected according to individual fonts, and selected and applied for each category.

When the code inspector selects at least one of the items from the inspector, fonts arranged in the code value of the selected item are loaded, and image matching is performed by dividing each section of the image by dividing the font and inspecting an image pattern for each section. The glyph of the font is automatically inspected by an error checking program for a glyph pattern that determines whether an error is detected and records an error item of a font corresponding to a code value where an error is found and stores it in the inspection history management unit. can do. In addition, an error item of a font corresponding to a code value in which an error is found may be displayed to the inspector.

Unicode can be displayed for each category of subdivided components that make up a character considering the characteristics of each language. Each language includes at least one language of Chinese, Japanese, Korean, and Latin. By subdividing the code for each letter, it is possible to implement a code that can be loaded on a screen in a predetermined amount and then displayed in turn so as to increase the cognitive efficiency of the examiner.

In case of sentence inspection, standardized error check on whether the appearance of sentences is appropriate by displaying sentences input from the examiner composed of at least one of Korean, English, special characters, a combination of Korean, English, and special characters, and direct input If an error is found by executing the program, the item and its contents can be recorded and stored in the inspection history management unit.

The standardized error checking program for the proper appearance of these sentences is fixed-width to match the specified values for items including spaces, stems, line widths, line widths, widths, and sizes between fonts according to font type. It may include a method of measuring according to a variable width, and may be implemented in various ways.

In the case of operating environment inspection, it is as shown in Figs. 14 and 15. Fig. 14 is a simulation screen of an actual service screen. When the font is applied to the web-based content service, the simulation is provided by providing the same editor as the editor provided in the content service. The editor may use a WISWIG (What you see is What you get) editor. When the font is applied in the real environment, it can provide an environment to check the overall design harmony such as kerning, stem, line width, and line spacing.

In addition, when the operating environment inspection is applied to a digital device such as a mobile phone as shown in FIG. 15 in which a font is embedded, the inspection may be implemented by implementing the same simulation environment as the corresponding digital device.

The above embodiments are an example for describing the technical spirit of the present invention in detail, and the present invention is not limited to the above embodiments, and various modifications are possible, and various embodiments of the technical spirit are all protected by the present invention. It belongs to the scope.

Claims (44)

The MCP (Main Contents Porvider) that provides content services through wired and wireless networks after completing the inspection of the fonts registered in the Contents Provider (CP) and the inspection history in the font inspection process and the inspection of the fonts themselves. A font management server including converting a format of the font file to suit a content service providing environment; And The converted font file is received from the font management server and provided to the corresponding content service server to which the font is to be applied, and the device type, content service type, application area within the content service, and the font are applied to the font. And a font operation server for managing management of the operation of the font including at least one of the recorded quantity records. The font operating server of claim 1, wherein Font management further comprising managing the content service information including the device information provided by each of the MCP content services and the font information to be applied to the content service, and transmitting the corresponding font file to the content service server of the MCP through a wired or wireless network. Management system. According to claim 1 or 2, wherein the font operating server When the content service of the MCP is a web-based content service, the method further includes managing content service information including a URL and font information to be applied to the content service, and transmitting the corresponding font file to the content service server of the MCP through a wired or wireless network. Font management system. The method of claim 1, The content service server obtains user information from the user terminal connected to the content service server and information on the font selected through the user terminal, and displays the selected font at a designated place from the user. The font management server of claim 1, wherein At least one of font name, font category, font related image name, font price, font service availability, font service provision period, font style, font author, font authoring company, font authoring date, font registration date, font update date and font deletion date A font information manager including font related information; Font file converted from the original file of the font provided from the CP, the inspection environment that can be simulated based on the environment in which the font service is to be provided, the final font file that has been inspected, and the content to which the font is applied from the final font file. A font file manager configured to manage the font file converted to fit the service environment and an image file related to the font; A inspection item management unit which manages inspection items for the fonts in the process of proceeding to the inspection process after generating a font file converted for the inspection environment that can be simulated based on the environment in which the font service is to be provided; An inspection history management unit which manages error items of the font checked during the inspection process and sequentially manages files in which the inspection process is recorded and files in which the inspection is completed; The font file is converted from the CP to match the inspection environment that can be simulated based on the environment in which the font service is to be provided, and the inspection history management unit is searched for the final font file that has been inspected from the font file management unit. A font format conversion management unit for converting a font file into a format suitable for a content service environment to which fonts are loaded; And And a URL management unit for managing a content service URL to which a registered font is provided from an MCP. According to claim 1 or 5, wherein the font management server A schedule manager configured to manage a schedule related to font provision to a content service and font inspection for a font provision service; And And an authority management unit including information on access from the CP and the MCP and access authority on the use of the system. According to claim 1 or 5, wherein the font management server The font operation management system, characterized in that it further comprises a contract management unit for managing the contract contents including at least one of the contract period, contract details, security content, revenue distribution and fee settlement management between the MCP and CP. The method of claim 5, The inspection environment that can be simulated based on the environment in which the font service is to be provided is generated by at least one of web pages, plug-ins, ActiveX programs, mobile and other OS-based programs, and embedded software. . The method of claim 5, wherein the font format conversion management unit When the font registered from the CP is applied to the web-based inspection environment, the font inspection test URL provided by the system is automatically embedded in the font before converting the font file format for the inspection of the font. Font operation management system. The method of claim 5, wherein the font format conversion management unit When the font registered from the CP is applied to the web-based content service, the inspection history management unit searches for the final font file that has been inspected from the font file management unit, and then the corresponding web-based content service selected by the CP from the URL management unit. And further including automatically embedding URLs in each font, and converting the font file into a format suitable for a content service environment. The method of claim 6, The schedule management unit includes a registration schedule from the CP for executing the font providing service, an inspection schedule, a re-registration and re-examination schedule due to rejection of registration when an error occurs in the inspection process, and a schedule in which the font is applied to the actual content service. Font management system comprising at least any one management. The method of claim 5, wherein the format conversion management unit It is generated by including at least one of Type1, Type3, Open Type Font (OTF), Character Identifier Font (CID), True Type Font (TTF), and Embedded Open Type (EOT) to suit the inspection environment. Font operation management system. The font management server of claim 5, wherein And a service management unit including information on a type of content service to which the font is applied and device environment. 6. The font inspecting process of claim 5 wherein At least one of each code check of the font and the font check together to form a sentence, at least one of the sentence check to check whether the appearance of the fonts harmonious in the sentence, and the operating environment check to simulate by providing the actual device environment of the content service to be applied to the font Font operation management system comprising a. The method of claim 14, The code inspection is a font operation management system, characterized in that it comprises at least one item of Unicode, variable English, half-width English, full-width English, KS special characters, KS additional special characters and binja. The method of claim 15, In the case of Unicode, the font management system, characterized in that displayed by the category of the subdivided components that make up a character in consideration of the characteristics of each language.  The method of claim 16, Each language zone includes at least one language zone among Chinese, Japanese, Korean, and Latin language zones, and in the case of Korean, the codes for each letter are subdivided so that a predetermined amount of codes can be loaded on one screen and then displayed sequentially. Font operation management system, characterized in that for adjusting. The method of claim 15, In the code review, when at least one or more of the items is selected from the inspector, fonts arranged in the code value of the selected item are loaded, and the glyph of the font is automatically checked by an error check program relating to a font glyph pattern. And record an error item of the font corresponding to the code value where the error is found and store it in the inspection history management unit. The method of claim 18, An error checking program relating to a font glyph pattern may be configured to image an font, divide each section of an image, examine an image pattern corresponding to each section, determine whether there is a match, and notify whether there is an error. The method of claim 18, And an error item of a font corresponding to a code value in which the error is found is displayed to an inspector. The method of claim 14, The sentence check is a standardized error check on whether the appearance of the sentence is appropriate by displaying a sentence input from the examiner composed of at least one of Hangul, English, special characters, a combination of Korean, English, and special characters, direct input If an error is found by executing the program, the font operation management system, characterized in that the record and store the entry and the inspection history management unit. The method of claim 21, The standardized error check program for determining whether the sentence forms the proper appearance is fixed width whether it meets the numerical value specified for the items including spaces, stems, line widths, lines, horizontal, and sizes between fonts according to font type. , Font operation management system comprising a method of measuring according to the variable width. The method of claim 14, The operation environment check is a font operation management system comprising a simulation provided by the same editor provided in the content service when the font is applied to the web-based content service. The method of claim 23, wherein The editor is a font management system, characterized in that it comprises a WISWIG (What you see is What you get) editor. The method of claim 14, When the operating environment check is applied to a digital device in which the font is embedded, the font operation management system, characterized in that it comprises the same simulation environment as the digital device. (a) Receives font operation information related to font files and fonts from CP (Contents Provider), which is granted the registration authority, for font files configured according to the font implementation type suggested by the MCP (Main Contents Provider), and registers them with the font information management unit. Making; (b) converting the registered font file into a file format suitable for the inspection environment and storing it in a font file management unit upon receiving a request for proceeding with a font inspection process from a CP for the registered font file; (c) after the font file format is converted to match the inspection environment, loading the font file in which the format is converted, and then proceeding with the font inspection process through a inspection item manager which manages inspection items for the font; (d) recording and managing the inspection history of the font through the font inspection process through an inspection history management unit; (e) if the verification of the registered font through the font verification process is completed, storing the final file in which the verification is completed, in the font file management unit; And (f) converting the format of the font file through a font format conversion management unit so as to fit the environment in which the actual font is applied by loading the final file whose inspection has been completed from the font file management unit by searching the inspection history management unit; Font operation management method. (a) receiving a font file according to a font implementation form and font operation information related to a font from a contents provider (CP) to which registration authority is granted and registering the same in a font information management unit; (b) converting the registered font file into a file format suitable for the inspection environment and storing it in a font file management unit upon receiving a request for proceeding with a font inspection process from a CP for the registered font file; (c) after the font file format is converted to match the inspection environment, loading the font file in which the format is converted, and then proceeding with the font inspection process through a inspection item manager which manages inspection items for the font; (d) recording and managing the inspection history of the font through the font inspection process through an inspection history management unit; (e) if the verification of the registered font through the font verification process is completed, storing the final file in which the verification is completed, in the font file management unit; (f) displaying a screen configured to select one or more of various devices; (g) automatically selecting a format for the selected device upon receiving a selection signal for one or more of the displayed various devices; (h) searching the inspection history management unit for the final font file stored in the inspection and constructing and displaying a list of the final font files stored in the font file management unit; (i) converting a format of a font file through a font format conversion management unit to match the selected font file with the selected device format when at least one or more of the displayed final font file list is selected; Font operation management method. The method of claim 26 or 27, The authority granted to the MCP or CP is a font operation management method, characterized in that the authority type and the time limit is determined through the authority management unit including information on the access authority for access and use of the system. The method of claim 27, The authority management unit is a font, characterized in that for granting authority in connection with the entire schedule for font registration, font inspection and font provision to the content service server from the schedule management unit stored the schedule registered from at least one of the MCP and CP Operational management method. The method of claim 26 or 27, The font implementation form in step (a) comprises at least one of an outline and a bitmap. The method of claim 26 or 27, The font operation information related to the font in step (a) includes at least one of font names, font concepts, image thumbnails of fonts, font styles, and environmental categories to which fonts are to be provided. Way. The method of claim 26 or 27, In step (a), if the font file registered from the CP and the font operation information related to the font do not conform to the format of the designated registration file or the input information does not match the font information to be inspected, an error message is sent to the CP. Font operation management method further comprising the step of returning. 33. The method of claim 32, If the request for re-registration of the font operation information related to the font file and the font modified from the CP after the error message transmission and return processing for the font file and the font operation information related to the font, the font operation further comprising: How to manage. The method of claim 26 or 27, In the step (b), the inspection environment is a font operation management method, characterized in that generated by at least one of a web page, a plug-in, ActiveX, mobile, other OS-based programs, embedded software. The method of claim 26 or 27, When the font is applied to the web-based content service in converting the font file format suitable for the inspection environment in the step (b), the method further includes the step of automatically embedding the inspection URL in the font. Font operation management method. The method of claim 26 or 27, When converting the font file registered in step (b) into a file format suitable for the inspection environment, Type1, Type3, Open Type Font (OTF), Character Identifier Font (CID), True Type Font (TTF), EOT (Embedding) Open Type) font management characterized in that it comprises at least one or more of the font type. The method of claim 26 or 27, In the step (c), the font inspection process checks whether the code of each font and the fonts form a sentence, and examines the appearance of the fonts in harmony with the sentence. Font operation management method characterized in that it comprises at least one or more of the operating environment check to simulate by providing. The method of claim 26 or 27, In the step (d), the inspection history includes sequential information about a file in which the inspection process including the error items of the font checked in the inspection process and its contents is recorded, and files in which the font inspection at each stage is completed. Font operation management method characterized in that. The method of claim 26 or 27, All font files and files including information associated with the font is stored in a font operation management method characterized in that the stored. The method of claim 26 or 27, For font files that have been checked in step (e), when the font is applied to a web-based content service, a corresponding content service URL registered from the MCP selected by the CP is read from the URL management unit and automatically embedded in each font. Font operation management method characterized in that it further comprises a step. The method of claim 26, And if the format of the font file is converted in accordance with the environment in which the font is actually applied in step (f), transmitting the font file to a content service server of an MCP. The method of claim 26, If the environment in which the font is actually applied in the step (f) is a digital device, Registering a font file in a font conversion process and selecting a format suitable for a digital device type; And And when the format is selected, converting the font file whose verification is completed into a font of the selected digital device format by calling a digital device font conversion function. 42. The method of claim 41 wherein When the font file is transmitted to the content service server of the MCP, the font operation management method, characterized in that the transmission according to the schedule registered from the MCP or CP. The method of claim 26 or 27, If the font inspection process in step (c), the font operation management method further comprising the step of providing a print sheet of the corresponding inspection item for each inspection screen.