KR101321130B1 - Multilingual electronic publishing management system and method thereof - Google Patents

Abstract

The present invention relates to a multilingual electronic publication management system and a method for managing the same, which can effectively translate and manage contents only while maintaining a layout for electronic publication with respect to an electronic publication requiring multilingual translation. In order to translate into a high translation matching rate to create a file to be provided to the translator to provide, and to immediately reflect the translated results without a separate DTP rework, it is possible to increase the productivity extremely. In addition, only the content to be translated using the DTP publication format to be translated directly is extracted while assigning a separate identifier as a tag of a type that cannot be modified to generate a translation file, and the translation result of the generated translation file. Recombines the translated content based on the tag given in the original DTP publication format, and replaces only the contents of the DTP publication with the translated content, thereby maintaining complex layout information such as index or cross-reference combined with the content. There is an effect available.

Description

Multilingual electronic publishing management system and method thereof

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a multilingual electronic publication management system and a method for managing the same. In particular, a multilingual electronic publication management system for efficiently translating and managing only contents while maintaining a layout for electronic publication for an electronic publication requiring multilingual translations It relates to a system and a management method thereof.

Most offline and online publications are made through desktop publishing (DTP) software, and various features are constantly being added to meet the needs of different users.

Therefore, a single DTP publication output is composed of complex interworking with information on various layouts and information on actual contents, so that complex DTP work can be performed to provide a desired publication output when the contents are changed. Should be done again.

For example, in the case of producing a multilingual manual in which the same form or content of the language is different, DTP work is performed for each language. In particular, the translation work for multilingual translation is often done separately from the workers who perform the DTP work, and most of them are referred to a professional translator or translation company for translation. assisted translation) is provided in the form that can be used in the software, and the translator who receives it returns the translation result through CAT software. Because of the loss of indexes, cross-references, and links in the DTP output, a significant amount of modification is required when the translated file is imported back into the DTP software.

1 shows a configuration and procedure for a general multilingual manual operation, as shown, a translation requestor (mainly a DTP worker) is provided with an electronic publishing system including at least a DTP unit 10, and corresponding to more smooth operation. The system may further include a CAT unit 20. The translator uses a translation system including the CAT unit 30. In general, the CAT units 20 and 30 may be provided with databases 25 and 35, respectively, because they are configured to store translations once and present them in subsequent translations to increase translation efficiency.

For example, the DTP unit 10 is InDesign of Adobe, which is widely used as DTP software, and the CAT units 20 and 30 are SDL, which is widely used as CAT software. Assume Trados.

In the above configuration, the translation requester imports the original language publication 1 completed by the user through the DTP unit 10 (process ①) and converts it into an output format of a shareable format (process ②, ② ' ). The shareable output format is an INX (Indesign Interchange) file (2) or an Extensible Markup Language (2X) file (2 ') that constitutes a publication content in a combination of components that can be shared for compatibility with lower versions in InDesign. Use

The translation requester can deliver the converted output format files 2, 2 'directly to the translator, and if the CAT unit 20 is provided to collect and recycle the translation data as shown, the CAT unit 20 Receive the corresponding shareable file (2, 3) through () and convert it to the multi-language file format (TTX) for the tag editor used for actual translation in CAT 20, 30 and request TTX. Create file 3 (step ④).

The translation requester provides the generated request TTX file 3 to the translator, and the translator imports the request TTX file 3 through the tag editor of the CAT unit 30 (step ⑤). Thereafter, the translation requester performs translation using the tag editor of the CAT unit 30 to generate a translation TTX file 4 including the final translated contents (process 6).

The translator provides the generated translation TTX file 4 back to the translation requester. The translated TTX file 4 may include only translated content, may also include content requested for translation, and may also include information about the relationship. On the other hand, the translator can also be provided with the translation memory (TM) information, terminology information, etc. obtained in the process of performing the translation in addition to the translation TTX file (4) in general.

The translation requester receives the translation TTX file 4 provided by the translator, loads it into the CAT unit 20 (process ⑦), and again, an INX file which is a common format for managing it as a publication through the DTP unit 10. (2) or convert it to an XML file (2 ') (steps ⑧ and ⑧'). The process ⑦ and process ⑧, ⑧ 'may be provided by the translator if the translation requester does not have the CAT unit 20.

Thereafter, the translation requester imports the converted INX file 2 or XML file 2 'into the DTP unit 10 (processes ⑨ and ⑨').

In the case of the translated common file imported into the DTP unit 10, a large number of internal settings are changed by format changes, and a considerable amount of DTP rework is required due to tags modified during the translation process.

After this DTP rework, the translated publication (5) can be generated (process iii).

As described above, the present method is actually used for multilingual translation. In this case, the common file uses the INX file, and the INX file translated through the CAT unit 30 is called by the DTP unit 10. In this case, the internal setting is changed a lot, and the amount of DTP rework is considerably increased. In addition, since the INX file is for version design of InDesign, when translation is imported by Trados, the translation matching rate (degree to be similar when presenting similar previous translation results) is not good, so the translation time is low. There is also a long problem. However, there are still many cases where translation work is done in this way.

In order to compensate for this problem, when using the XML file among the common files, the memory matching rate is improved to some extent, and when importing it back into InDesign, the amount of DTP work is reduced compared to the case of using the INX file. Also, it is cumbersome to re-enter internal settings such as resetting indexes and cross-referencing from the beginning, which requires time-consuming DTP work.

Accordingly, there is a need for a new multilingual publication management system that can reduce the amount of work when the translation matching rate of the translation request file provided to the translator and the translated result are applied to the DTP publication.

Korean Patent Publication No. 10-2000-0049891 Korean Patent Publication No. 10-2000-0072164 Korean Patent Publication No. 10-2006-0030876

An object of the embodiments of the present invention for improving the above-mentioned problem is to generate and provide a file to provide the translator so that the translation matching rate is high to translate the publication for Desktop Publishing (DTP) in multiple languages, and provide the translated results It is to provide a multilingual e-publish management system and its management method to increase productivity by immediately reflecting without DTP rework.

Another object of the embodiments of the present invention is to directly extract the content to be translated using the DTP publication format to be translated, assigning a separate identifier to a tag of a type that cannot be modified, extracting it, and generating a translation file, and generating the corresponding translation. In the translation result for the file, the content translated based on the above-mentioned tag is recombined into the original DTP publication format so that only the contents of the DTP publication are replaced with the translated contents. The present invention provides a multilingual electronic publication management system and a method of managing the complex layout information.

Another object of the embodiments of the present invention is to provide a multilingual electronic publication management system and a method for managing the translated content in a web page form as needed so that an online publication or HTML-based output can be easily generated. To provide.

Another object of the embodiments of the present invention is to consider the translation content as a module based on the identifier applied to the translated content and track their modifications to manage the version so that data can be easily recycled without building an expensive module management system. To provide a multilingual electronic publishing management system and its management method to enable multiple publications.

In order to achieve the above object, a multilingual electronic publication management system according to an embodiment of the present invention receives an original publication file composed of a software format for electronic publishing in the form of a markup language including a tag, and translates the contents in the corresponding format. An identifier assigning unit for selecting a region including content to be extracted and extracting the selected selection region while assigning an identifier to a predetermined tag among the selection regions using XSLT (Extensible Stylesheet Language Transformations); A request format output unit for outputting the selection region extracted by the identifier granter as a request XML file for a translation request; A result format receiver for receiving a translation XML file having completed translation of the request XML file; Providing a translation result for generating an output of a web page format in which the identifier included in the translation XML file provided by the result format receiving unit is replaced with the contents of the corresponding selection area of the original publication format or the identifier is not maintained or maintained using XSLT. It is characterized by including a wealth.

The markup language type of electronic publishing software format is characterized in that the InDesign Markup Language (IDML).

The identifier assigning unit may include a story file extracting unit which selects at least a part of the story file included in the publication file in the IDML format as an area including the content to be translated.

The story file extracting unit of the identifier assigning unit may assign a GUID (Global Unique ID) to each ParagraphStyleRange tag included in the story file using XSLT.

The story file extracting unit of the identifier assigning unit may assign an identifier to an individual content tag included in the story file.

The identifier providing unit or the request format output unit adds information about an IDML file to which the extracted story file belongs as a new tag.

Based on the identifier given by the identifier assigning unit, the content to be translated and the translated content received through the result format receiving unit are modularized and stored in a database while assigning a version, and withdrawing the module from the database and updating the version as requested. Characterized in that it further comprises a Component Content Manager (CCM).

The CCM is characterized in that it works with electronic publishing software or CAT (Computer-assisted translation) software.

At least a part of the multilingual electronic publication management system is configured as a web application.

The multilingual electronic publication management method according to another embodiment of the present invention is a multilingual electronic publication management method implemented in a multilingual electronic publication management system interoperating with electronic publishing software and translation software, and for markup language type electronic publications including tags. Receiving an original publication file composed of a software format to select the region containing the content to be translated among the contents of the format, the identifier assignment step of extracting the selected region while assigning an identifier to the predetermined tag of the selected region using XSLT Wow; A request format output step of outputting a selection region extracted by the identifier granter as a request XML file for a translation request; A result format receiving step of receiving a translation XML file having completed translation on the request XML file; Providing a translation result for generating an output of a web page format in which the identifier included in the translation XML file provided by the result format receiving unit is replaced with the contents of the corresponding selection area of the original publication format or the identifier is not maintained or maintained using XSLT. Characterized in that it comprises a step.

The multilingual electronic publication management system and its management method according to an embodiment of the present invention generate and provide a file to be provided to the translator so that the translation matching rate is high so as to translate the publication for DTP into a multilingual language, and provide the translated result as a separate DTP material. It is effective to increase productivity by reflecting immediately without work.

The multilingual electronic publication management system and management method thereof according to an embodiment of the present invention extracts only the content to be translated using a DTP publication format to be translated directly while assigning a separate identifier to a tag of a type that cannot be modified to translate the file. And convert the content translated based on the tag given in the translation result of the generated translation file into the original DTP publication format so that only the contents of the DTP publication are replaced with the translated content. Complex layout information such as index and cross reference combined with can be used as it is.

The multilingual electronic publication management system and its management method according to an embodiment of the present invention can easily transform the translated content into a web page form as needed to easily generate an online publication or an HTML-based output.

The multilingual electronic publication management system and its management method according to an embodiment of the present invention are considered to be a module based on the translated content and the identifier applied to the translated content, and the modified module is managed by tracking the version of the expensive module management system. Even if it is not built, there is an effect of easy data recycling and multiple publishing.

1 is a conceptual diagram showing a procedure for a conventional multilingual electronic publishing.
Figure 2 is a block diagram showing the configuration of a multilingual electronic publishing management system according to an embodiment of the present invention.
FIG. 3 is a conceptual diagram showing the configuration of a markup language-type electronic publishing software format (IDML). FIG.
4 is an exemplary view showing an example of a story file of IDML.
5 is an exemplary view showing an example of representation of the IDML story file of FIG.
6 is an exemplary view showing an example of a story file of IDML to which an identifier is assigned according to an embodiment of the present invention.
7 is an exemplary screen diagram of a tag editor showing a process of translating a request XML file according to an embodiment of the present invention.
8 is a conceptual diagram illustrating an operation method of a component content manager (CCM) according to an embodiment of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS The above and other objects, features and advantages of the invention will become more apparent from the following detailed description of the present invention when taken in conjunction with the accompanying drawings.

2 is a block diagram showing a configuration of a multilingual electronic publication management system 100 according to an embodiment of the present invention. In an embodiment of the present invention, the multilingual electronic publication management system 100 includes DTP (Desktop Publishing) software and CAT. It can be configured to work with computer-assisted translation software, or it can be configured as standalone if necessary. On the other hand, the recent electronic publishing includes online publishing such as HTML, and the electronic publishing management in the form of a web service running on a web server for efficient management. Accordingly, at least a part of the system 100 for managing multilingual electronic publishing in cooperation with the DTP software and the CAT software may be configured in the form of a database-linked web application. Such a web service type electronic publishing management system may have a DTP function or a CAT function as needed, and may be more closely linked with individual DTP software or CAT software.

InDesign, which is widely known as the DTP software mentioned while explaining the multilingual publication management system 100 shown in the embodiment of the present invention, will be described as an example, but another type of DTP software having a file format similar to InDesign. Note that the same can be applied to.

First, the illustrated multilingual publication management system 100 performs a CAT for translation of a file 201 of an original DTP publication format (IDML (InDesign Markup Language) format, which is a native format of InDesign) of a basic language generated through DTP software. Instead of transforming the tag editor into a recognizable shareable file (XML or INX), it receives the file 201 of the format as it is, and selects and extracts only the content that needs to be translated while maintaining the format. The tag editor converts and provides a request XML file 211, which is a recognized common format file, and receives the translation XML file 221 translated from the request XML file 211 through CAT software. Create a multi-language DTP publication format file 231 incorporating content into a file of the original DTP publication format (IDML) to generate various indexes, cross-references, Various settings for publishing the layout and the like are maintained. In other words, no post-translational DTP rework is required, and if necessary, it is only simple enough to be difficult to compare with the existing method.

In order to operate in this manner, the multilingual publication management system 100 according to an exemplary embodiment of the present invention distinguishes and extracts a content area in consideration of structural characteristics of an IDML file, and extracts a unique identifier (GUID: Global Unique ID) for the extracted content. To give. The unique identifier may be assigned by assigning a unique identifier to a tag related to a content that can be distinguished from a tag editor of a CAT software in a state where it cannot be modified.

The multilingual publication management system 100 provides the content to which the unique identifier is assigned to the request XML file 211, and receives the translation XML file 221 translated from the request XML file 211 to receive the corresponding translation XML file. The translation integrated IDML file 231 may be generated by substituting the contents of the original IDML file based on the GUID maintained at 221.

Meanwhile, in this process, the multilingual publication management system 100 may further perform a task of converting the contents of the translation XML file 221 into a web page such as HTML, and converts multilingual translation content based on the GUID. It can be considered as a module of, and can be recycled or managed through multiple publications.

Referring to the block diagram of the multi-language publishing management device 100 according to an embodiment of the present invention for the above-described operation, first, the original DTP file format (IDML) in the form of a unique markup language comprising a plurality of XML-type files Extensible Stylesheet Language Transformations (XSLT) is used for a preset tag included in the content while extracting at least some of the story files included in the original IDML file 201 as a target for translation. A GUID granter 110 for granting a GUID, a request format outputter 120 for outputting a story file extracted by the GUID granter 110 as a request XML file 211 for a translation request, A result format receiver 160 for receiving a translation XML file 221 having been translated into the request XML file 211 and the GUID included in the translation XML file provided by the result format receiver 160. Translation result provider 150 for providing a translation-integrated IDML file 231 by substituting the contents of the corresponding selected region of the original IDML file using XSLT or generating an output 232 of a web page format in which the GUID is not maintained or maintained. ) Is basically provided. On the other hand, the GUID granting unit 110 and the translation result providing unit 150 grants a GUID and performs the substitution based on this XSLT may be configured as a separate XSLT unit 130, the function as necessary It may be included in the GUID providing unit 110 or the translation result providing unit 150.

The translation result providing unit 150 internally replaces the corresponding location content of the original IDML file with the translated content based on the GUID included in the translation XML file 221 or the IDML integrating unit 151 for integrating in multiple languages. If necessary, the translation XML file 221 may be provided with a web page conversion unit 152 for converting and outputting the web page in various xML formats such as HTML, SGML, XML, and the like.

On the other hand, each function unit may operate according to a request of each function, but a separate control unit or a management unit may not be necessary, but for the purpose of integrated management for user authentication, access management and various additional functions for the multilingual publication management system. Control unit 140 for managing the operation of the GUID granting unit 110, request format output unit 120, XSLT unit 130, result format receiving unit 160, translation result providing unit 150 and receiving the result It may further include.

In addition, the multilingual publication management system 100 internally modifies the content to be translated based on the GUID given by the GUID granting unit 110 and the translated content received through the result format receiving unit 160 to give a version. It may further include a CCM (Component Content Manager) 170 for storing in the database 180, and withdraws the module from the database 180 and updates the version on request. Through this, modularized contents can be utilized in various ways, such as the use of modularized translations as material for subsequent differential translations or multiple publications. Therefore, even if an expensive separate content management system (CMS) is not constructed, It can be used efficiently.

As a result, the multilingual publication management system 100 may be used by a translation client requesting a translation to request a translator in the same manner as before, and the translator receives the IDML file itself from the translation client and transmits the IDML file itself. 100 can also be used to deliver multilingual IDML files. In addition, in the case of a company managing both a multilingual publication and a translator, the multilingual publication management system 100 may be used to maximize work efficiency. Therefore, the multilingual publication management system 100 may be configured as local software, but for effective application, the multilingual publication management system 100 may be implemented as a service that is configured as a database-linked web application and can be used through web login.

Multilingual Translation Example

An example of managing a multilingual publication through the configuration of the embodiment of the present invention described above will be described with reference to FIGS. 3 to 7.

First, the GUID assigning unit 110 receives the original IDML file 201 and extracts a story file among contents of the IDML file 201 into a content area to be translated, thereby assigning a GUID to a predetermined tag.

3 is a conceptual diagram showing the configuration of IDML, which is a kind of markup language format for electronic publishing software. As shown, the IDML file format 310 internally defines MIMETYPE information 311 and designates the data format. XML 312 for the map, resource region 313 for defining information about various resources in an XML file, spread region 314 for defining information about various spreads in an XML file, story XML files corresponding to actual contents A story area 315 is included, an XML area 316 having setting information for functioning as XML, a master spread 317, and meta information 318.

Recently, DTP software is basically written in a scripting language, and since XML is used to efficiently organize it, the native format of DTP software also has a markup language form as shown, thus not only IDML but other DTP native formats. It is also common to have a similar form.

Accordingly, the GUID granter 110 assigns a GUID to each content of the story file while extracting the story file 314 having the actual content while maintaining various setting related contents in the DTP-specific format. . If necessary, additional identifiers may be additionally used internally.

4 is an exemplary view showing some contents of a story file of IDML. As shown in FIG. 4, it can be seen that contents having various tags in XML form exist when looking at the internal source of the story file 320.

The illustrated configuration uses English as the original language and can be seen as part of the manual.

Looking at the structure of the illustrated story file, it can be seen that the tags <ParagraphStyleRange> </ ParagraphStyleRange> classify paragraphs 321 to 323 of each content to be internally translated.

The illustrated story file is substantially represented by the screen 330 shown in FIG. 5 when viewed in InDesign. Here, each paragraph 321, 322, 323 of FIG. 4 is represented by three different representations 331 in FIG. 5.

Therefore, since each of these paragraphs should be distinguished from each other, the GUID granting unit 110 according to the embodiment of the present invention selects a GUID to the <ParagraphStyleRange> tag through the XSLT unit 130 while selectively extracting the story file from the original IDML file. Grant. Since the XSLT is known as one of methods for converting XML into a desired format or form, a detailed description thereof will be omitted.

In addition, the GUID grantor 110 or the request format outputter 120 adds information about the IDML file to which the story file belongs as a new tag to determine what is the original IDML of the request XML or the translation XML. It is desirable to be able to confirm.

FIG. 6 is an exemplary diagram illustrating an example of a story file of IDML to which an identifier is assigned according to an embodiment of the present invention. As illustrated, the GUID unit is an example of a result of converting the story file of FIG. 4 into a request XML form. After granting the GUID according to whether or not 110, some of the sources 340 of the request XML file 211 output by the request format output unit 120 are shown.

First, information about an IDML file to which a corresponding story file originally belongs was added as a new tag 341. It can be seen that each <ParagraphStyleRange> tag has been given a GUID (342, 343, and 344).

 If necessary, an additional identifier (local identifier) may be assigned to a <content> tag, which is a content tag for each sentence in each <ParagraphStyleRange> </ ParagraphStyleRange> tag.

Thereafter, the translator imports the request XML file 211 into a tag editor of CAT software (in the embodiment of the present invention, the tag editor of Trados) and translates it. The <ParagraphStyleRange> tag is generally prohibited from modification. This setting ensures that GUID assignments remain safe even if the tags for rendering are slightly modified during translation.

7 shows an example of the translation screen 350 of the tag editor of Trados.

As shown, the <ParagraphStyleRange> tag with a GUID is not visible in the tag editor and cannot be modified.

When the translation of the original is made through the tag editor, only the corresponding translation can be generated as a translation XML file 221, and a bilingual file including the original can also be created, and the interrelation information about them It can also be included.

Although not shown, translation memory (TM) or terminology information used for such translation may also be provided with the translation XML file 221, which may be IDML-specific or information to which the corresponding GUID belongs. Can be recycled.

The translated translation XML file 221 is received through the result format receiving unit 160 and modularized with the original content based on the GUID and managed by the CCM 170, and the received translation XML file 221 is stored in the translation result. The IDML integrator 151 provided to the study 150 replaces or adds the translated content based on the GUID to the original IDML file with the existing contents (that is, each paragraph of the existing story file) or adds the translation integrated IDML file (231). ) Of course, the manner of integrating the translation content may be more diverse and may be modified as necessary, but may be easily performed by the methodology of reflecting the translation content based on the GUID.

Meanwhile, the translation result providing unit 150 may convert each story file of the translated XML file into a separate web page through the web page conversion unit 152, and may be recycled based on the GUID even if this conversion is performed. have. Of course, you can also remove the GUID during conversion.

FIG. 8 is a conceptual diagram illustrating an operation method of a component content manager (CCM) according to an embodiment of the present invention. When the CCM 170 receives the translated XML file, the CCM 170 includes one module for each paragraph of an original and a translation. Make a version and store it in the database 180, and provide the module at the request of DTP software or CAT software or user, and if there is a modification, the module received is modified to store the version by saving the cashier and managing the version. Conduct.

After the translation is modularized by the CCM 170 in paragraph units and managed with GUIDs, hash values, and version values of the contents, it is easy to search and reuse. It can be widely used for multilingual automatic matching of specific words, multiple publications, etc.

The foregoing and other objects, features and advantages of the present invention will become more apparent from the following detailed description of the present invention when taken in conjunction with the accompanying drawings. However, the present invention is not limited to the above-described embodiments, and various changes and modifications may be made by those skilled in the art without departing from the scope of the present invention. .

100: multilingual publishing management system 110: granting GUID
120: request format output unit 130: XSLT unit
140: control unit 150: translation result providing unit
160: result format receiving unit 170: CCM
180: Database 201: Source IDML File
211: Request XML File 221: Translation XML File
231: Translation Integration IDML File 232: Web Page

Claims (18)

Receives an original publication file composed of a software format for electronic publishing in the form of a markup language including a tag, selects an area including the content to be translated among the contents of the format, and then sets an XSLT (Extensible Stylesheet) to a preset tag among the selected areas. An identifier assigning unit configured to extract a selected region while assigning an identifier using Language Transformations;
A request format output unit for outputting the selection region extracted by the identifier granter as a request XML file for a translation request;
A result format receiver for receiving a translation XML file having completed translation of the request XML file;
Providing a translation result for generating an output of a web page format in which the identifier included in the translation XML file provided by the result format receiving unit is replaced with the contents of the corresponding selection area of the original publication format or the identifier is not maintained or maintained using XSLT. Includes wealth,
The markup language type of electronic publishing software format is InDesign Markup Language (IDML), and the identifier providing unit selects at least a part of the story file included in the publication file in the IDML format as an area including the content to be translated. And a story file extracting unit, wherein the story file extracting unit of the identifier assigning unit assigns a Global Unique ID (GUID) to each ParagraphStyleRange tag included in the story file using XSLT.
delete delete delete The multilingual electronic publication management system of claim 1, wherein the story file extracting unit of the identifier providing unit assigns an identifier to individual content tags included in the story file.
The multilingual electronic publication management system of claim 1, wherein the identifier providing unit or the request format output unit adds information about an IDML file to which the extracted story file belongs as a new tag.
The method of claim 1, wherein the content to be translated and the translated content received through the result format receiving unit are modularized and stored in a database while assigning a version, and the module is stored in the database according to a request. Multilingual electronic publication management system, characterized in that it further comprises a component content manager (CCM) to update the version.
8. The system of claim 7, wherein the CCM is interoperable with electronic publishing software or computer-assisted translation software.
The system of claim 1, wherein at least a portion of the multilingual electronic publication management system comprises a web application.
A multilingual electronic publishing management method implemented in a multilingual electronic publishing management system that interworks with electronic publishing software and translation software.
Receiving an original publication file composed of a software format for electronic publishing in the form of markup language including a tag, selecting an area including the content to be translated among the contents of the format, and using XSLT to a predetermined tag among the selected areas An identifier assigning step of extracting the selected selection area while assigning an identifier;
A request format output step of outputting a selection region extracted by the identifier granter as a request XML file for a translation request;
A result format receiving step of receiving a translation XML file having completed translation on the request XML file;
Providing a translation result for generating an output of a web page format in which the identifier included in the translation XML file provided by the result format receiving unit is replaced with the contents of the corresponding selection area of the original publication format or the identifier is not maintained or maintained using XSLT. Steps,
The markup language type of electronic publishing software format is InDesign Markup Language (IDML), and the identifier assignment step includes at least a part of a story file included in a publication file of the IDML format as an area including content to be translated. And a story file extraction step of selecting, wherein the story file extraction step assigns a GUID to each ParagraphStyleRange tag included in the story file using XSLT.
delete delete delete The method of claim 10, wherein the extracting the story file comprises assigning identifiers to individual content tags included in the story file.
The method of claim 10, wherein the identifier assignment step or the request format output step add information about an IDML file to which the extracted story file belongs as a new tag.
The method of claim 10, wherein the content to be translated and the translated content received through the result format receiving unit are modularized and stored in a database while assigning a version, and the module is stored in the database according to a request. The method for managing multilingual electronic publications, further comprising: stepping in and out of the component content to update the version.
17. The method of claim 16, wherein in the component content management step, withdrawal of the module is requested by electronic publishing software or translation software.
The multilingual electronic publishing management method according to claim 10, wherein the multilingual electronic publishing system in which at least a part of each step of the multilingual electronic publishing management method is performed is configured as a web application on a web server.

Images