CN112650724A - Document file processing method, system, computing device and medium - Google Patents

Abstract

The present disclosure provides a method for processing a document file, including: determining the type of an original document file in response to a first import request including the original document file; converting the original document file into a text file based on a lightweight markup language according to the type of the original document file; and storing the text file and generating a version identification corresponding to the text file. The present disclosure also provides a document file processing system, a computing device, and a computer storage medium. The document file processing method, the device computing equipment and the computer storage medium can be used in the technical field of cloud computing or other fields.

Description

Document file processing method, system, computing device and medium

Technical Field

The present disclosure relates to the field of cloud computing technologies, and in particular, to a method and a system for processing a document file, a computing device, and a computer storage medium.

Background

With the wide application of computer and network technology in various industries, people rely on computers more and more for daily office work. Taking document (including table) processing in a daily office scene as an example, when a plurality of persons are involved to cooperatively process the same document, a cooperative head-up person needs to send an original document to each cooperative participant by means of mails and the like, the cooperative participants are respectively modified and then sent to the head-up person by means of mails and the like, then the head-up person opens the documents fed back by each cooperative participant one by one, each modification point is identified, and then modification and summarization are manually performed on the basis of the original document.

The original cooperation mode has low efficiency and high error rate, and particularly, as the number of persons participating in cooperation increases, the problems of low efficiency and high error rate can be rapidly amplified, so that multi-person cooperation is difficult to smoothly develop.

Disclosure of Invention

One aspect of the present disclosure provides a method for processing a document file, including: determining the type of an original document file in response to a first import request comprising the original document file; converting the original document file into a text file based on a lightweight markup language according to the type of the original document file; and storing the text file and generating a version identification corresponding to the text file.

Optionally, the determining the type of the original document file includes: acquiring a suffix name of the original document file; and determining the type of the original document file by analyzing the suffix name of the original document file.

Optionally, the converting the original document file into a text file based on a lightweight markup language according to the type of the original document file includes: according to the type of the original document file, analyzing the content of the original document file to determine format data and text data of the original document file; and converting the format data and the text data of the original document file into the text file.

Optionally, the method further comprises: in response to an export request comprising a first version identification, determining a first text file corresponding to the first version identification in stored text files according to the first version identification; converting the first text file into a first document file; and sending the first document file to the second client.

Optionally, the method further comprises: in response to a second import request comprising a second version identification and a second document file, converting the second document file into a second text file; determining a third text file corresponding to the second version identification in the stored text files; merging the second text file and the third text file to obtain a fourth text file; and storing the fourth text file and generating a version identification corresponding to the fourth text file.

Optionally, the merging the second text file and the third text file to obtain a fourth text file includes: determining data of the second text file which is modified relative to the third text file as modified data; and modifying the third text file according to the modification data to obtain the fourth text file.

Optionally, the method further comprises: recording the modification data; presenting the modification data in response to a modification history query request for the fourth text file; and in response to a rollback request for the fourth text file, undoing a modification corresponding to the modification data from the fourth text file. Another aspect of the present disclosure provides a document file processing system, including: the file importing method comprises the steps that a file importing module is used for responding to a first importing request comprising an original file and determining the type of the original file; the file conversion module is used for converting the original document file into a text file based on a lightweight markup language according to the type of the original document file; and the version management module is used for storing the text file and generating a version identifier corresponding to the text file.

Another aspect of the disclosure provides a computing device comprising: one or more processors; storage means for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method as described above.

Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the method as described above when executed.

Another aspect of the disclosure provides a computer program comprising computer executable instructions for implementing the method as described above when executed.

According to the embodiment of the disclosure, the original document file is converted into a text file based on a lightweight markup language according to the type of the original document file; and storing the text file and generating the version identification corresponding to the text file, thereby facilitating the management of the document file by the user and having higher efficiency.

Drawings

For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

FIG. 1 schematically illustrates an application scenario of a document file processing method and a document file processing system according to an embodiment of the present disclosure;

FIG. 2 schematically shows a flow chart of a method of processing a document file according to an embodiment of the present disclosure;

FIG. 3 schematically shows a flowchart of a method of processing a document file according to another embodiment of the present disclosure;

FIG. 4 schematically shows a flowchart of a method of processing a document file according to another embodiment of the present disclosure;

FIG. 5 is a schematic diagram illustrating a method of processing a document file according to another embodiment of the present disclosure;

FIG. 6 schematically illustrates an exemplary block diagram of a document file processing system according to an embodiment of the disclosure;

FIG. 7 schematically illustrates an exemplary block diagram of a document file processing system according to another embodiment of the disclosure;

FIG. 8 schematically illustrates an exemplary block diagram of a document import module, according to another embodiment of the present disclosure;

FIG. 9 schematically illustrates an exemplary block diagram of a file conversion module according to another embodiment of the disclosure;

FIG. 10 schematically illustrates an exemplary block diagram of a file transfer module according to another embodiment of the disclosure;

FIG. 11 schematically illustrates an exemplary block diagram of a version management module according to another embodiment of the disclosure;

FIG. 12 schematically shows an exemplary block diagram of a document export module according to another embodiment of the disclosure; and

FIG. 13 schematically illustrates a block diagram of a computer system suitable for implementing the methods described in embodiments of the present disclosure, in accordance with embodiments of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

Some block diagrams and/or flow diagrams are shown in the figures. It will be understood that some blocks of the block diagrams and/or flowchart illustrations, or combinations thereof, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the instructions, which execute via the processor, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks. The techniques of this disclosure may be implemented in hardware and/or software (including firmware, microcode, etc.). In addition, the techniques of this disclosure may take the form of a computer program product on a computer-readable storage medium having instructions stored thereon for use by or in connection with an instruction execution system.

The embodiment of the disclosure provides a document file processing method and a document file processing system capable of applying the method. The method comprises the steps of responding to a first import request comprising an original document file, and determining the type of the original document file; converting the original document file into a text file based on a lightweight markup language according to the type of the original document file; and storing the text file and generating a version identification corresponding to the text file.

It should be noted that the method and the apparatus for processing the document file provided by the embodiment of the present disclosure may be used in the technical field of cloud computing, and may also be used in any field other than the technical field of cloud computing.

Fig. 1 schematically shows an application scenario of a document file processing method and a document file processing system according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a scenario in which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, but does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.

As shown in fig. 1, the system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).

The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 105 may be a server providing various services, such as a background management server (for example only) providing support for websites browsed by users using the terminal devices 101, 102, 103. The background management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a webpage, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that the processing method of the document file provided by the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the processing system of the document file provided by the embodiment of the present disclosure may be generally disposed in the server 105. The processing method of the document file provided by the embodiment of the present disclosure may also be executed by a server or a server cluster which is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and/or the server 105. Accordingly, the processing system for the document file provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server 105.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Fig. 2 schematically shows a flowchart of a processing method of a document file according to an embodiment of the present disclosure.

As shown in fig. 2, the method includes operations S210 to S230.

In operation S210, a type of an original document file is determined in response to a first import request including the original document file.

According to an embodiment according to the present disclosure, an import request is used to import a document file into a system. The type of document file may include, for example, Word, Excel, and the like.

According to the embodiment of the disclosure, the suffix name of the original document file can be obtained, and the type of the original document file is determined by analyzing the suffix name of the original document file.

In operation S220, the original document file is converted into a text file based on the lightweight markup language according to the type of the original document file.

According to the embodiment of the disclosure, according to the type of the original document file, the content of the original document file can be analyzed in an analysis mode corresponding to the type, so as to determine the format data and the text data of the original document file. And then converts the format data and text data of the original document file into a text file.

According to embodiments of the present disclosure, a text file may be based on markdown, for example.

In operation S230, the text file is stored, and a version identification corresponding to the text file is generated.

According to an embodiment of the present disclosure, a text file may be stored in a server. For example, in this embodiment, the text file may be stored in a distributed version management apparatus, and version tracking information may be established by the version management apparatus, where the version tracking information includes version identification, archive time, and other information.

According to the embodiment of the disclosure, an original document file is converted into a text file based on a lightweight markup language according to the type of the original document file; and storing the text file and generating the version identification corresponding to the text file, thereby facilitating the management of the document file by the user and having higher efficiency.

Fig. 3 schematically shows a flowchart of a document file processing method according to another embodiment of the present disclosure.

As shown in fig. 3, the method includes operations S310 to S330 in addition to operations S210 to S230.

In operation S310, in response to an export request including a first version identifier, a first text file corresponding to the first version identifier among the stored text files is determined according to the first version identifier.

According to an embodiment of the present disclosure, the export request includes a version identification for requesting export of the document file corresponding to the version identification. Export requests may be issued by users who upload the original document (e.g., collaboration leaders) or by other users who have editing rights (e.g., collaboration participants).

In operation S320, the first text file is converted into a first document file.

According to the disclosed embodiments, the first text file may be converted back to the first document file in the reverse operation of converting the first document file to the first text file when uploading the first document file.

In operation S330, the first document file is transmitted to the second client.

According to the embodiment of the disclosure, the stored text file can be converted into the document file to be exported to the user terminal based on the export request of the user, so that the user can conveniently check or edit the document file.

Fig. 4 schematically shows a flowchart of a document file processing method according to another embodiment of the present disclosure.

As shown in fig. 4, the method includes operations S410 to S440 in addition to operations S210 to S230 and operations S310 to S330.

In operation S410, the second document file is converted into a second text file in response to a second import request including the second version identification and the second document file.

According to an embodiment of the present disclosure, the second import request is for uploading the exported document file again. It will be appreciated that the document file that is uploaded again may have been modified relative to the document file at the time of export.

According to the embodiment of the present disclosure, the operation of converting the second document file into the second text file is similar to operation S220, which may be specifically referred to as operation S220, and is not described herein again.

In operation S420, a third text file corresponding to the second version identification among the stored text files is determined.

According to the embodiment of the present disclosure, the second version identifies the corresponding third text file, i.e., the text file of the current version corresponding to the second document file already stored in the server.

In operation S430, the second text file is merged with the third text file to obtain a fourth text file.

According to an embodiment of the present disclosure, operation S430 may include, for example, determining data of the second text file that is modified with respect to the third text file as modified data, and then modifying the third text file according to the modified data to obtain a fourth text file.

In operation S440, the fourth text file is stored, and a version identification corresponding to the fourth text file is generated.

According to the embodiment of the disclosure, the fourth text file may be stored in the version management module, and the version tracking information may be updated by the version management module, where the version tracking information includes the version identification, the archive time, and other information of the fourth text file.

According to another embodiment of the disclosure, modification data corresponding to each modification of a document file can be recorded for a user to view or rollback the modification. For example, in this embodiment, the user terminal may send a modification history query request to the server, and the server presents the modification data to the user terminal in response to the modification history query request for the fourth text file.

In addition, the user terminal may also send a rollback request to the server. And the server responds to the rollback request, determines the text file to be rolled back and the modification data according to the rollback request, and then cancels the modification recorded by the modification data in the text file to be rolled back according to the modification data.

According to the document file processing method disclosed by the embodiment of the invention, the same document can be processed by multiple persons, the system records modification information every time, the combination of modification contents is automatically carried out, the document modification history can be traced back, and the document can be returned to the state before the specified modification occurs, so that the user can be helped to quickly, efficiently and accurately carry out daily office cooperation of multiple persons.

The method illustrated in fig. 2-4 is further described with reference to fig. 5 in conjunction with specific embodiments. Those skilled in the art will appreciate that the following example embodiments are only for the understanding of the present disclosure, and the present disclosure is not limited thereto.

Fig. 5 schematically shows a processing method of a document file according to another embodiment of the present disclosure.

As shown in fig. 5, the method includes steps 501 to 511.

Wherein the collaboration lead imports the document into the system, step 501.

In step 502, the system identifies the type of document, parses the format and content of the document.

In step 503, the system converts the document to a markdown type text file.

In step 504, the system transmits the text file to the distributed version management device.

In step 505, the distributed version management apparatus manages the text file and creates version tracking information.

At step 506, the collaboration participants select the document imported by the lead person, and send an identifier containing the document to the system.

In step 507, the system obtains a markdown type text file corresponding to the identifier of the document from the distributed version management apparatus.

At step 508, a markdown type text file is converted to a document and exported.

In step 509, the collaboration participants modify the exported document and import the modified document into the system, and after steps 502, 503 and 504 are sequentially performed, step 510 is performed.

In step 510, the distributed version management apparatus automatically performs file modification and merging, and records the modification history. If there are multiple collaboration participant modifications, then steps 506, 507, 508, 509 are repeated.

In step 511, the collaboration leader selects a specified document, exports it, and repeats steps 506, 507, and 508.

According to the embodiment of the disclosure, when a plurality of persons collaborate to process office documents, an original document is firstly compiled by a collaborating leader and then uploaded to a system, the system automatically converts the original document into a simple text file based on a standard lightweight markup language (markdown), and the simple text file is managed by using a distributed version control technology (such as git). When each cooperation participant selects a file from the system to export, the simple text file is automatically converted into a daily office document by the system, the cooperation participant is modified and then imported into the system, the system automatically completes the conversion from the office document to the simple text file, the modification of the simple text file is automatically recorded each time, and the modifications are automatically combined, so that the efficiency and the accuracy of the conventional daily office cooperation can be greatly improved.

FIG. 6 schematically shows an exemplary block diagram of a document file processing system according to an embodiment of the disclosure.

As shown in fig. 6, the processing system 600 of a document file includes a document import module 610, a file conversion module 620, and a version management module 630. The document file processing system 400 may perform the methods described above with reference to fig. 2-5.

Specifically, the document import module 610 may be configured to determine a type of an original document file in response to a first import request including the original document file.

The file conversion module 620 may be configured to convert the original document file into a text file based on a lightweight markup language according to the type of the original document file.

The version management module 630 may be configured to store the text file and generate a version identifier corresponding to the text file.

FIG. 7 schematically shows an exemplary block diagram of a document file processing system according to another embodiment of the present disclosure.

As shown in fig. 7, in addition to the document import module 610, the file conversion module 620, and the version management module 630, the processing system 700 of the document file may further include:

the file transfer module 740 may be configured to perform text file transfer, transfer the text file to the version management module 630, or obtain the text file from the version management module 630.

Document export module 750 may be used to export a specified document from the system.

According to the embodiment of the disclosure, when the document import system is managed, a user can be connected with the file conversion module through the document import module, and the document file is converted into the text file and then transmitted to the version management module through the file transmission module. When office files need to be exported from the system, the file export module can acquire the text files from the version management module through the file transmission module, and then the text files are converted into document files through the file conversion module and exported to users.

FIG. 8 schematically shows an exemplary block diagram of a document import module, according to another embodiment of the present disclosure.

As shown in fig. 8, the document import module 610 may further include a document type identification unit 611 and a document content parsing unit 612:

the document type identification unit 611 may be configured to determine a type of the document, specifically, EXCEL, WORD, etc., according to the suffix name of the document.

The document content analyzing unit 612 may be configured to read a document file according to a document type, perform content analysis, obtain a format and text content in the document, and facilitate subsequent file content conversion.

FIG. 9 schematically shows an exemplary block diagram of a file conversion module according to another embodiment of the disclosure.

As shown in fig. 9, the file conversion module 620 includes the following 4 processing units:

a word to markdown unit 621, which may be configured to convert a word file into a markdown file.

The excel to markdown unit 622 may be configured to convert an excel file into a markdown file.

The markdown to word unit 623 may be configured to convert a markdown file into a word file.

The markdown to excel unit 624 may be used to convert a markdown file into an excel file.

FIG. 10 schematically illustrates an exemplary block diagram of a file transfer module according to another embodiment of the disclosure.

As shown in fig. 10, the file transfer module 740 includes the following 2 processing units, which are respectively:

the file sending unit 741 may be configured to send the markdown file to the version management module.

The file obtaining unit 742 may be configured to obtain a markdown file from the version management module.

FIG. 11 schematically illustrates an exemplary block diagram of a version management module according to another embodiment of the disclosure.

As shown in fig. 11, the version management module 630 may also be used to perform version management of markdown files, maintain file modification history, automatically merge and modify, view file modification history, and rollback file modification. The version management module 630 includes 1 processing unit, which is:

the version library management unit 631 may be configured to provide writing and reading functions of a version library, track and maintain changes of written files, automatically combine modifications of files each time, and provide an interface for the document export module 5 to query a file modification history, reset a file to a specific historical version of a file, or delete a specified modification. The version library management unit may be based on git, for example, or the like.

FIG. 12 schematically shows an exemplary block diagram of a document export module according to another embodiment of the disclosure.

As shown in FIG. 12, a document export module 750 is used to select a given document and its particular modified version from the system for export. Comprises 3 processing units which are respectively:

the file information query unit 751 may be configured to invoke the interface capability provided by the version library management unit 631, query the file information and the file operation information, and present the file information and the file operation information to the user.

The file history modification unit 752 may be used to invoke the interface capability provided by the version library management unit 631, to perform operations on files in the version library, to reset files to a specified historical version, or to delete a particular historical operation.

A file export unit 753 may be used to export files from the system for use by the user.

Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware, and firmware implementations. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.

For example, any plurality of the document import module 610, the file conversion module 620, the version management module 630, the file transmission module 740, and the document export module 750 may be combined into one module to be implemented, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the document import module 610, the file conversion module 620, the version management module 630, the file transfer module 740, and the document export module 750 may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementations of software, hardware, and firmware, or any suitable combination of any of them. Alternatively, at least one of the document import module 610, the file conversion module 620, the version management module 630, the file transfer module 740, and the document export module 750 may be at least partially implemented as a computer program module that, when executed, may perform corresponding functions.

FIG. 13 schematically illustrates a block diagram of a computer system suitable for implementing the above-described method according to an embodiment of the present disclosure. The computer system illustrated in FIG. 13 is only one example and should not impose any limitations on the scope of use or functionality of embodiments of the disclosure.

As shown in fig. 13, computer system 1300 includes a processor 1310 and a computer-readable storage medium 1320. The computer system 1300 may perform a method according to an embodiment of the disclosure.

In particular, processor 1310 may include, for example, a general purpose microprocessor, an instruction set processor and/or related chip sets and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), and/or the like. The processor 1310 may also include onboard memory for caching purposes. Processor 1310 may be a single processing unit or a plurality of processing units for performing different actions of a method flow according to embodiments of the present disclosure.

Computer-readable storage media 1320, for example, may be non-volatile computer-readable storage media, specific examples including, but not limited to: magnetic storage devices, such as magnetic tape or Hard Disk Drives (HDDs); optical storage devices, such as compact disks (CD-ROMs); a memory, such as a Random Access Memory (RAM) or a flash memory; and so on.

The computer-readable storage medium 1320 may include a computer program 1321, which computer program 1321 may include code/computer-executable instructions that, when executed by the processor 1310, cause the processor 1310 to perform a method according to an embodiment of the present disclosure, or any variation thereof.

The computer program 1321 may be configured with computer program code, for example comprising computer program modules. For example, in an example embodiment, code in computer program 1321 may include one or more program modules, including 1321A, modules 1321B, … …, for example. It should be noted that the division and number of modules are not fixed, and those skilled in the art may use suitable program modules or program module combinations according to actual situations, which when executed by the processor 1310, enable the processor 1310 to perform the method according to the embodiments of the present disclosure or any variation thereof.

According to an embodiment of the present invention, at least one of the document import module 610, the file conversion module 620, the version management module 630, the file transfer module 740, and the document export module 750 may be implemented as a computer program module described with reference to fig. 13, which, when executed by the processor 1310, may implement the corresponding operations described above.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

While the disclosure has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents. Accordingly, the scope of the present disclosure should not be limited to the above-described embodiments, but should be defined not only by the appended claims, but also by equivalents thereof.

Claims (10)

1. A processing method of a document file comprises the following steps:

determining the type of an original document file in response to a first import request comprising the original document file;

converting the original document file into a text file based on a lightweight markup language according to the type of the original document file; and

and storing the text file and generating a version identification corresponding to the text file.

2. The method of claim 1, wherein the determining the type of the original document file comprises:

acquiring a suffix name of the original document file; and

and determining the type of the original document file by analyzing the suffix name of the original document file.

3. The method of claim 1, wherein the converting the original document file into a text file based on a lightweight markup language according to a type of the original document file comprises:

according to the type of the original document file, analyzing the content of the original document file to determine format data and text data of the original document file; and

and converting the format data and the text data of the original document file into the text file.

4. The method of claim 1, further comprising:

in response to an export request comprising a first version identification, determining a first text file corresponding to the first version identification in stored text files according to the first version identification;

converting the first text file into a first document file; and

and sending the first document file to the second client.

5. The method of claim 4, further comprising:

in response to a second import request comprising a second version identification and a second document file, converting the second document file into a second text file;

determining a third text file corresponding to the second version identification in the stored text files;

merging the second text file and the third text file to obtain a fourth text file; and

and storing the fourth text file and generating a version identification corresponding to the fourth text file.

6. The method of claim 5, wherein said merging the second text file with the third text file to obtain a fourth text file comprises:

determining data of the second text file which is modified relative to the third text file as modified data; and

and modifying the third text file according to the modification data to obtain the fourth text file.

7. The method of claim 6, further comprising:

recording the modification data;

presenting the modification data in response to a modification history query request for the fourth text file; and

and in response to a rollback request for the fourth text file, undoing a modification corresponding to the modification data from the fourth text file.

8. A system for processing a document file, comprising:

the file importing method comprises the steps that a file importing module is used for responding to a first importing request comprising an original file and determining the type of the original file;

the file conversion module is used for converting the original document file into a text file based on a lightweight markup language according to the type of the original document file; and

and the version management module is used for storing the text file and generating a version identifier corresponding to the text file.

9. A computing device, comprising:

one or more processors;

a memory for storing one or more computer programs,

wherein the one or more computer programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1 to 7.

10. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 7.

Images