Electronic book editing and proofreading method, device and system based on git protocol

Abstract

The application discloses an e-book editing and proofreading method, device and system based on a Git protocol, the method comprising: creating an e-book project for editing and proofreading content; creating at least one work branch based on the project as a main trunk, each work branch being configured with corresponding editing and proofreading; under the work branch framework, carrying out content interaction based on the editing and proofreading according to the Git protocol; and updating the interactive content to the main trunk when the editing and proofreading of the interactive content are consistent and confirmed. The editing and proofreading mechanism effectively meets the proofreading requirement of the manuscript, effectively manages the versions of the editing and proofreading, improves work efficiency, improves data security, and reduces the risk of copyright theft.

Description

Technical Field

[0001] This invention belongs to the field of computer technology, specifically, it relates to an e-book editing and proofreading method, apparatus and system based on the Git protocol. Background Technology

[0002] Because the publishing industry predates the development of computers and information technology, a large portion of the vast collection of books owned by publishers worldwide is only available in print, not electronically. To address this issue, the common practice is to scan print books using an electronic image scanner to obtain scanned ebooks. These scanned ebooks are then subjected to OCR (Optical Character Recognition) to obtain the original digital ebook. Further proofreading and content flow reconstruction are then performed on the original digital ebook to obtain a high-quality digital ebook. However, proofreading and content flow reconstruction require processing various elements such as titles, footnotes, endnotes, annotations, figure captions, tables, formulas, and references. In the foreseeable future, artificial intelligence will find it difficult to perform this task while maintaining reasonable commercial interests. Therefore, the proofreading and content reconstruction of digital ebooks after OCR still rely on costly manual labor, typically performed by full-time processing personnel employed by ebook processing companies. This is costly. Furthermore, the same group of processors needs to process various types of books, and if the processors' knowledge level does not match the books they are processing (e.g., engineering and technical books), the processing quality cannot be guaranteed.

[0003] In traditional editing and proofreading work, the process of editing and proofreading manuscripts by editors and authors using word processing tools such as Word is relatively complex and repetitive. Using Git protocols to manage work that requires collaboration among multiple people (authors and editors) can effectively improve processing efficiency.

[0004] In the prior art, for example, the prior art with publication number CN112364632A discloses a book proofreading method and apparatus. The solution adopted is as follows: acquiring and displaying the book to be proofread, which is a book typed from a reference book; acquiring the text content of the book to be proofread and the position of the text content in the book to be proofread; generating a first proofreading annotation at the corresponding position of the text content in the book to be proofread based on the text content, the position of the text content in the book to be proofread, and the reference book, the first proofreading annotation includes suggestions for modification and / or deletion of the text content; receiving a user's instruction to add proofreading annotations, acquiring a second proofreading annotation entered by the user based on the first proofreading annotation on the current page of the book to be proofread based on the instruction, and generating a second proofreading annotation at the corresponding position of the text content on the current page, the second proofreading annotation including the user's suggestions for modification and / or deletion; obtaining the proofreading result of the book to be proofread based on the first proofreading annotation and the second proofreading annotation.

[0005] The aforementioned existing technology has the following problems:

[0006] Traditional text editing tools can meet the proofreading needs of manuscripts to a certain extent with their proofreading functions. However, even existing platforms based on the Git protocol still do not provide effective version management for editing and proofreading, which reduces work efficiency. At the same time, data leakage often occurs during data interaction, resulting in copyright theft. Summary of the Invention

[0007] To address the problems of existing technologies, this invention provides an ebook editing and proofreading method based on the Git protocol. Based on a created ebook project, at least one working branch is created with the project as the main branch. Each working branch is configured with corresponding editors and proofreaders. Within the working branch framework, content interaction between the editors and proofreaders is performed based on the Git protocol. If the editors and proofreaders agree on and confirm the interactive content, the interactive content is updated to the main branch. This editing and proofreading mechanism effectively meets the proofreading needs of the manuscript, effectively manages the versions of the edited and proofreaded documents, and improves work efficiency. Simultaneously, an exchangeable encryption key is generated based on the attribute information of the editors and proofreaders. This exchangeable encryption key is used to encrypt the exchanged content for data interaction. During the exchangeable encryption interaction, different exchangeable encryption keys are used to encrypt the interactive data in each one-way data transmission process, improving data security and reducing the risk of copyright theft.

[0008] The present invention adopts the following technical solution:

[0009] Firstly, an ebook editing and proofreading method based on the Git protocol includes:

[0010] Create an eBook project for editing and proofreading content;

[0011] With the project as the main branch, create at least one working branch, and configure corresponding editing and proofreading for each working branch;

[0012] Within the aforementioned work branch framework, the content interaction for editing and proofreading is performed based on the aforementioned Git protocol;

[0013] If the editing and proofreading processes agree and confirm the content of the interaction, the interactive content will be updated to the main branch.

[0014] An exchangeable encryption key is generated based on the attribute information of the editing and proofreading. The exchanged content is then encrypted using the exchangeable encryption key for data interaction.

[0015] Further sub-branches are created on the working branch.

[0016] The editing includes multiple parts, and the proofreading includes multiple parts; the correspondence between the editing and proofreading is pre-configured.

[0017] Each edit and proofreading modification is assigned a unique identifier for version control management.

[0018] The edited and proofread content uploaded and updated is checked and compared with the content saved on the Git remote server to ensure that there are no discrepancies or conflicts between the uploaded and updated content and the content already saved on the remote server; if discrepancies or conflicts exist, follow the discrepancy and conflict guidance prompts.

[0019] Grant corresponding operation permissions for the editing and proofreading.

[0020] Secondly, an e-book editing and proofreading device based on the Git protocol includes:

[0021] Create modules to create eBook projects for editing and proofreading content;

[0022] The branching module, with the project as the main branch, creates at least one working branch, and each working branch is configured with corresponding editing and proofreading functions.

[0023] The interaction module, within the working branch framework, performs content interaction for editing and proofreading based on the Git protocol;

[0024] The update module updates the interactive content to the main branch if the content of the editing and proofreading interactions is undisputed and confirmed.

[0025] Furthermore, the security module generates an exchangeable encryption key based on the edited and proofread attribute information, and uses the exchangeable encryption key to encrypt the exchanged content for data interaction.

[0026] Thirdly, an e-book editing and proofreading system based on the Git protocol, the system comprising:

[0027] One or more processors;

[0028] Storage device for storing one or more programs;

[0029] When the one or more programs are executed by the one or more processors, the one or more processors implement the above-described Git protocol-based ebook editing and proofreading method.

[0030] Beneficial effects

[0031] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0032] This invention provides an eBook editing and proofreading method, apparatus, system, and computer-readable storage medium based on the Git protocol. Based on a created eBook project, at least one working branch is created with the project as the main branch. Each working branch is configured with corresponding editors and proofreaders. Within the framework of these working branches, content interaction between the editors and proofreaders is performed based on the Git protocol. If the editors and proofreaders agree on and confirm the interactive content, the interactive content is updated to the main branch. This editing and proofreading mechanism effectively meets the proofreading needs of the manuscript, effectively manages the versions edited and proofread, and improves work efficiency. Simultaneously, an exchangeable encryption key is generated based on the attribute information of the editors and proofreaders. This exchangeable encryption key is used to encrypt the exchanged content for data interaction. During the exchangeable encryption interaction, different exchangeable encryption keys are used to encrypt the interactive data in each one-way data transmission process, improving data security and reducing the risk of copyright theft. Attached Figure Description

[0033] Figure 1 This is a flowchart of an e-book editing and proofreading method based on the Git protocol according to the present invention.

[0034] Figure 2 This is a flowchart illustrating the workflow of an e-book editing and proofreading method based on the Git protocol according to the present invention.

[0035] Figure 3 This is a flowchart of an e-book editing and proofreading method based on the Git protocol, as described in this invention.

[0036] Figure 4 This is a flowchart illustrating the ebook version rollback process in an ebook editing and proofreading method based on the Git protocol, as described in this invention.

[0037] Figure 5 This is a structural diagram of an e-book editing and proofreading device based on the Git protocol according to the present invention;

[0038] Figure 6 This is a structural diagram of an electronic device system provided as an embodiment of the operating environment for an e-book editing and proofreading method based on the Git protocol in this invention.

[0039] Figure 7 This is a structural diagram of a computer-readable storage medium provided for an embodiment of the operating environment of an e-book editing and proofreading method based on the Git protocol in this invention. Detailed Implementation

[0040] The present invention will be further described below with reference to specific embodiments.

[0041] The terms “comprising” and “including” as used herein should be understood as inclusive and open-ended, not exclusive. Specifically, when the terms “comprising” and “including” and their synonyms are used in the specification and claims, they mean to include the specified features, steps, or components. These terms should not be construed as excluding the presence of other features, steps, or components.

[0042] The environment created by this invention

[0043] Git is a distributed version control protocol based on the C programming language. The Git protocol is implemented in a collaborative model similar to a team, where version control is particularly important. It meets the following requirements: it can save different historical versions of any file; it records the people who made the changes and the reasons for the changes; it provides testing for the most recent version; it has access control functions to prevent unauthorized changes and viewing; it can compare different source codes for review; it can compare the differences between different versions; it is centrally managed in terms of space and tracked in terms of time; and it is an automatic or semi-automatic auxiliary tool.

[0044] Unlike centralized version control systems such as CVS and SVN, Git enables efficient collaboration among development teams, and team members' work will not be interrupted by conflicts caused by frequent commits. Project administrators also do not need to worry about backing up project data and historical versions. After being tested by large projects like Linux, Git has been proven to be capable of handling teams of any size, even if the team members are located all over the world.

[0045] Distributed version control systems work by first storing the source code in the Git central repository. Then, team members fork the project from the central repository to their own remote repository, clone the project from their remote repository to their local machine (cloning the complete project files), create their own branches, and then work on the source code. During this process, they can also create further branches under their own branches. After finishing their work, they must update their remote repository (to prevent the central repository from being updated while their own repository is not synchronized) to ensure consistency between their remote repository and the central repository. Finally, they resolve conflicts between their modified source code and the source code from pull1, merge them, and then commit them to their own remote repository. The remote repository then commits the changes to the central repository, and after administrator approval, the branches are merged.

[0046] The Git-based deployment system comprises five modules: a Git repository, a work order information database, a target machine cluster, a configuration management backend, and a deployment operation platform. The Git repository stores the source code of all projects; creating a new project requires first creating a new Git repository on GitLab and uploading the corresponding source code files. The work order information database stores the configuration information of all projects and all work order information for each project. The target machine cluster is a collection of Docker containers and physical machines, used by the deployment operation platform to allocate new work orders. The configuration management backend is primarily responsible for managing the configuration information for new projects accessing the deployment system. The deployment operation platform calls the Git repository, the work order information database, and the target machine cluster to complete the functions of each stage of the work order's lifecycle. The specific process is as follows:

[0047] First, the deployment platform reads the configuration table from the work order information database to display all configured projects. When a developer creates a release work order under a project, the deployment platform creates a new feature branch on the repository by calling GitLab's branch creation API. Simultaneously, it randomly selects an idle machine from the target machine cluster and assigns it to the release work order, writing the corresponding machine IP address into the work order database. Next, when the developer clicks the deployment function, the deployment platform sends a deployment command to the target machine via Python's paramiko module. Upon receiving the deployment command, the target machine immediately executes the deployment command, pulling the code of the corresponding branch from the Git remote repository to its local project directory via HTTP or SSH protocol, completing the deployment operation. Finally, after successful work order acceptance, the deployment platform calls GitLab's tagging API to complete the tagging operation. The API returns a tag ID to the deployment platform, which then writes the tag ID into the corresponding work order record in the work order database.

[0048] On the one hand, this invention provides an e-book editing and proofreading method based on the Git protocol, such as... Figure 1 As shown, it includes the following:

[0049] First, create an eBook project for editing and proofreading the content;

[0050] For each ebook project, a corresponding ebook project is created in the editing and proofreading system. Each ebook project includes corresponding attribute information, such as project name, project number, project structure, role settings, and personnel composition. The editing and proofreading system can be either a client-server (CS) architecture or a browser-server (BS) architecture; the server can be a dedicated server, i.e., a cloud server. The specific system architecture is not limited, as long as the system architecture can implement ebook editing and proofreading functions based on the Git protocol, it meets the requirements.

[0051] Second, using the project as the main framework, create at least one working branch, and configure corresponding editing and proofreading for each working branch;

[0052] In one embodiment, using an ebook project as the main framework, one or more working branches are created based on the analyzed project structure. Each working branch corresponds to a project structure branch. For example, the ebook project includes multiple chapters, and each chapter corresponds to a working branch.

[0053] Each work branch is configured with corresponding editing and proofreading roles. In one embodiment, each work branch is configured with one or more editing and proofreading role pairs, and each role corresponds to one or more people.

[0054] In one embodiment, an editor and proofreader role pair is configured, with each role corresponding to a specific person. This setup clarifies responsibilities and improves work efficiency.

[0055] Third, within the aforementioned work branch framework, the content interaction for editing and proofreading is performed based on the aforementioned Git protocol;

[0056] The editing user (i.e. the staff corresponding to the editing role) edits and typesets the corresponding e-book project branch under the set work branch framework, completes and saves a version of the work, and submits it to the proofreading user (i.e. the staff corresponding to the proofreading role) through the system.

[0057] In one embodiment, the system sets up a local Git repository, where each version of the work is stored and has a unique version identifier; a Git remote server is set up, where editing users upload and submit the version of the work to the Git remote server, and proofreading users retrieve the version of the work through the Git remote server for corresponding proofreading, thereby realizing the content interaction.

[0058] Fourth, if the editor and proofreader agree on and confirm the content of the interaction, update the content of the interaction to the main branch.

[0059] In one embodiment, the system sets up an e-book server and updates the final, undisputed version of the work as the published version to the e-book server.

[0060] Furthermore, the method also includes:

[0061] Fifth, generate an exchangeable encryption key based on the edited and proofread attribute information, and use the exchangeable encryption key to encrypt the exchanged content for data interaction.

[0062] The aforementioned commutative encryption is a secret-sharing scheme proposed to prevent the theft of secrets transmitted over public channels. It leverages the difficulty of solving discrete logarithms and the commutativity of modular exponential functions. Users select their own private keys, which avoids fraud by the distributor, reduces the distributor's burden, ensures the reusability of the encryption scheme, and allows trusted participants to join or leave the participant set at any time, ensuring the scheme's dynamism.

[0063] In one embodiment, to enhance security, the function designed in this invention for exchangeable encryption is:

[0064]

[0065] Where t is calculated based on a weighted ratio of user attribute information or profile information.

[0066] In one embodiment, the edited version of the work uploaded by the user is encrypted using an encryption key generated based on the edited user's attribute information, and the encrypted ciphertext data is transmitted interactively; the proofreaded version of the work uploaded by the user is encrypted using an encryption key generated based on the proofreading user's attribute information, and the encrypted ciphertext data is transmitted interactively.

[0067] In one embodiment, an encryption key is generated based on the attribute information of the user who edits or proofreads the user. This attribute information includes an identity identifier, which may include any one or a combination of multiple identity verification identifiers such as the user's mobile communication terminal number, ID card number, and passport number. This step may generate a first hash value based on a message digest algorithm. Message digest algorithms include, but are not limited to, the MD5 algorithm. A corresponding exchangeable encryption key is generated, and the corresponding version of the work is encrypted using the exchangeable encryption key to obtain the encrypted work.

[0068] Data exchange is achieved based on exchangeable encryption algorithms. During the interaction, both parties encrypt their own data and the other party's data, ultimately enabling dynamic key encryption transmission during data exchange and minimizing data leakage.

[0069] In one embodiment, the encryption key is generated based on the user profile of the editing user or proofreading user.

[0070] In one embodiment, the encryption key includes a private key / public key pair, and encryption and decryption are performed using the private key / public key pair.

[0071] In one embodiment, one or more sub-branches are further created on the working branch, and one or more sub-branches are further created on the sub-branches; each sub-branch is configured with corresponding editing and proofreading.

[0072] In one embodiment, the editing includes multiple editing processes, and the proofreading includes multiple proofreading processes; the correspondence between the editing and proofreading processes is pre-configured.

[0073] In one embodiment, each modification made during editing and proofreading is assigned a unique identifier for version control management.

[0074] In one embodiment, the edited and proofread content uploaded and updated is checked and compared with the content saved on the Git remote server to ensure that there are no discrepancies or conflicts between the uploaded and updated content and the content already saved on the remote server; when discrepancies or conflicts exist, the operation is performed according to the discrepancy and conflict guidance prompts.

[0075] Grant corresponding operation permissions for the editing and proofreading.

[0076] The method and process for setting up an ebook editing and proofreading system, including an ebook server, a remote Git server, a local Git repository, and user clients, is as follows: Figure 3 As shown, this includes conflict resolution methods.

[0077] like Figure 3 As shown, the user unit includes multiple users user1, user2, user3, ..., each with different roles, such as editor and proofreader roles, and implements corresponding functions through the user client. For simplicity and to highlight key points, these are not shown in the accompanying drawings.

[0078] See Figure 3 The information flow steps are as follows:

[0079] Step 1: The user unit edits, formats, saves, or provides modification suggestions (proofreading) for the e-book document unit and saves it to the electronic document;

[0080] Step 2: The e-book document unit sends version control management instructions to the local Git repository unit;

[0081] Step 3: The local Git repository unit pushes the first update command, which contains the first update parameters, to the Git remote server unit.

[0082] The first update parameters include: first push number hash, first brief description commit message, first updater information name & email, first push time information date & time, and the modified document;

[0083] Specifically, step 3 includes:

[0084] Step 3.1: The local Git repository unit sends a conflict query for the first update instruction to the Git remote server unit, the query including the first update instruction;

[0085] Step 3.2: Check and compare the content of the pushed update with the content of the Git remote server to ensure that there are no discrepancies or conflicts between the document content pushed and the content already saved on the remote server. If there are discrepancies or conflicts, resolve them.

[0086] Choose to accept the content pushed from this local Git repository, overwriting the content already saved on the remote Git server; or

[0087] Accept content already saved on the remote Git server as the latest content, and overwrite the content that will be pushed to the local Git repository; or

[0088] Both accepted the offer and attempted to update the push notification again.

[0089] further, Figure 4 This demonstrates the process of rolling back an ebook version.

[0090] like Figure 4 As shown, the user unit and the local Git repository unit can view modification records (git log), and the e-book document unit and the local Git repository unit can perform version rollback (git reset).

[0091] Step 3.3: Automatically save the content after the disagreement and conflict is resolved, and generate a new unique number hash2. Then repeat the above push update process to ensure that all modified content is saved.

[0092] Step 4: The local Git repository unit prepares to retrieve the latest committed e-book document content from the Git remote server, including: the document modification content corresponding to several push updates between the local Git project and the Git remote server, the unique number hash corresponding to several push updates, the brief description of the commit message corresponding to several push updates, the updater information name & email corresponding to several push updates, and the time information date & time corresponding to several push updates, etc.

[0093] Step 5: The local Git repository unit checks and compares the content retrieved from the remote Git server with the content in the local Git project. If discrepancies or conflicts exist, the initiator who initiated the push update from the remote Git server will resolve them according to the discrepancy / conflict guidance. The solutions include:

[0094] Accept the option to overwrite the latest content fetched from the remote Git server with local content from the local Git repository; or

[0095] Accept content already saved on the remote Git server as the latest content, and overwrite the content of the local Git repository; or

[0096] Both modifications are accepted and saved.

[0097] The content after the disagreement and conflict is resolved is automatically saved and a unique hash3 number is generated. Then, the user who initiated the push update from the Git remote server can adjust the content locally.

[0098] This ensures that there are no discrepancies or conflicts between the various push updates retrieved from the Git remote server and the entire local content, allowing all work to be committed correctly.

[0099] Step 6: The user views the modification history of the latest commit ebook document obtained from the Git remote server and reviews the modified content of the document in turn.

[0100] The modifications include, but are not limited to: content adjustments, layout adjustments, and suggested content.

[0101] In one embodiment, the method further includes:

[0102] The second user views, modifies, or adjusts the e-book document, generates version control management commands, and sends them to the local Git repository.

[0103] As mentioned above, this step involves any user editing and formatting the content of the e-book, making adjustments according to suggestions, submitting new suggestions for modification, and saving the modified content to an electronic document;

[0104] Perform version control management on the edited e-book documents;

[0105] Repeat the steps described above for pushing updates to and retrieving updates from the Git remote server, and edit and modify the content during this process until the ebook content is confirmed to be complete.

[0106] Furthermore, if the book editor finds no need for adjustments, then no adjustments will be made, and the process will proceed directly to step 7.

[0107] Step 7: The book editor and the book author confirm the content of the working branch. If yes, update to the main branch, complete the proofreading and editing work, and the content is officially published.

[0108] Specifically, this includes the Git remote server confirming the completed ebook content and publishing the ebook to the ebook server.

[0109] In one embodiment, the method may further include,

[0110] Initiate modifications and discussions to the already published ebook content, and repeat the above process until it is confirmed and published again.

[0111] If the editor and proofreader confirm the content of the work branch in step 7 and the result is negative, then a new workflow will be initiated, returning to step 2 and re-entering the work branch.

[0112] You can use Git's version control feature to view any push update history for ebook content, including: details of document modifications included in the push update, a unique number generated by the push update, a brief description of the push update, information about the person who made the update (name and email address), and the time of the push update.

[0113] For any push update, you can use the unique ID of that push update to restore the ebook content to the state it was in at the time of the push update.

[0114] On the other hand, in one embodiment, the present invention provides an e-book editing and proofreading device based on the Git protocol, such as... Figure 5 As shown, the device includes:

[0115] Create modules to create eBook projects for editing and proofreading content;

[0116] For each ebook project, a corresponding ebook project is created in the editing and proofreading system. Each ebook project includes corresponding attribute information, such as project name, project number, project structure, role settings, and personnel composition. The editing and proofreading system can be either a client-server (CS) architecture or a browser-server (BS) architecture; the server can be a dedicated server, i.e., a cloud server. The specific system architecture is not limited, as long as the system architecture can implement ebook editing and proofreading functions based on the Git protocol, it meets the requirements.

[0117] The branch module, with the project as the main branch, creates at least one working branch, and each working branch is configured with corresponding editing and proofreading functions.

[0118] In one embodiment, using an ebook project as the main framework, one or more working branches are created based on the analyzed project structure. Each working branch corresponds to a project structure branch. For example, the ebook project includes multiple chapters, and each chapter corresponds to a working branch.

[0119] Each work branch is configured with corresponding editing and proofreading roles. In one embodiment, each work branch is configured with one or more editing and proofreading role pairs, and each role corresponds to one or more people.

[0120] In one embodiment, an editor and proofreader role pair is configured, with each role corresponding to a specific person. This setup clarifies responsibilities and improves work efficiency.

[0121] The interaction module, within the working branch framework, performs content interaction for editing and proofreading based on the Git protocol;

[0122] The editing user (i.e. the staff corresponding to the editing role) edits and typesets the corresponding e-book project branch under the set work branch framework, completes and saves a version of the work, and submits it to the proofreading user (i.e. the staff corresponding to the proofreading role) through the system.

[0123] In one embodiment, the system sets up a local Git repository, where each version of the work is stored and has a unique version identifier; a Git remote server is set up, where editing users upload and submit the version of the work to the Git remote server, and proofreading users retrieve the version of the work through the Git remote server for corresponding proofreading, thereby realizing the content interaction.

[0124] The update module updates the interactive content to the main branch if the content of the editing and proofreading interactions is undisputed and confirmed.

[0125] In one embodiment, the system sets up an e-book server and updates the final, undisputed version of the work as the published version to the e-book server.

[0126] Furthermore, the security module generates an exchangeable encryption key based on the edited and proofread attribute information, and uses the exchangeable encryption key to encrypt the exchanged content for data interaction.

[0127] In one embodiment, the edited version of the work uploaded by the user is encrypted using an encryption key generated based on the edited user's attribute information, and the encrypted ciphertext data is transmitted interactively; the proofreaded version of the work uploaded by the user is encrypted using an encryption key generated based on the proofreading user's attribute information, and the encrypted ciphertext data is transmitted interactively.

[0128] In one embodiment, an encryption key is generated based on the attribute information of the user who edits or proofreads the user. This attribute information includes an identity identifier, which may include any one or a combination of multiple identity verification identifiers such as the user's mobile communication terminal number, ID card number, and passport number. This step may generate a first hash value based on a message digest algorithm. Message digest algorithms include, but are not limited to, the MD5 algorithm. A corresponding exchangeable encryption key is generated, and the corresponding version of the work is encrypted using the exchangeable encryption key to obtain the encrypted work.

[0129] Data exchange is achieved based on exchangeable encryption algorithms. During the interaction, both parties encrypt their own data and the other party's data, ultimately enabling dynamic key encryption transmission during data exchange and minimizing data leakage.

[0130] In one embodiment, the encryption key is generated based on the user profile of the editing user or proofreading user.

[0131] In one embodiment, the encryption key includes a private key / public key pair, and encryption and decryption are performed using the private key / public key pair.

[0132] In one embodiment, one or more sub-branches are further created on the working branch, and one or more sub-branches are further created on the sub-branches; each sub-branch is configured with corresponding editing and proofreading.

[0133] In one embodiment, the editing includes multiple editing processes, and the proofreading includes multiple proofreading processes; the correspondence between the editing and proofreading processes is pre-configured.

[0134] In one embodiment, each modification made during editing and proofreading is assigned a unique identifier for version control management.

[0135] In one embodiment, the edited and proofread content uploaded and updated is checked and compared with the content saved on the Git remote server to ensure that there are no discrepancies or conflicts between the uploaded and updated content and the content already saved on the remote server; when discrepancies or conflicts exist, the operation is performed according to the discrepancy and conflict guidance prompts.

[0136] Grant corresponding operation permissions for the editing and proofreading.

[0137] Please see Figure 6 , Figure 6 This is a structural diagram of an electronic device provided according to an embodiment of this application. Figure 6 As shown, the electronic device includes a processor, a memory, and a bus.

[0138] The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via a bus. When the machine-readable instructions are executed by the processor, they can perform the operations described above. Figure 1-4 The steps of the Git protocol-based ebook editing and proofreading method in the illustrated method embodiment can be found in the method embodiment for specific implementation, and will not be repeated here.

[0139] This application also provides a computer-readable storage medium, such as... Figure 7 As shown, the computer-readable storage medium stores a computer program that, when executed by a processor, can perform the above-described actions. Figure 1-4 The steps of the Git protocol-based ebook editing and proofreading method in the illustrated method embodiment can be found in the method embodiment for specific implementation, and will not be repeated here.

[0140] Those skilled in the art will readily understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the functional units in the various embodiments of this application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0141] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0142] Finally, it should be noted that the above-described embodiments are merely specific implementations of this application, used to illustrate the technical solutions of this application, and not to limit them. The protection scope of this application is not limited thereto. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the technical scope disclosed in this application. Such modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be covered within the protection scope of this application. Therefore, the protection scope of this application should be determined by the protection scope of the claims.

Claims

1. A method for editing and proofreading ebooks based on the Git protocol, characterized in that, include: Create an eBook project for editing and proofreading content; With the project as the main branch, create at least one working branch, and configure corresponding editing and proofreading for each working branch; Within the aforementioned work branch framework, the content interaction for editing and proofreading is performed based on the aforementioned Git protocol; Further sub-branches are created on the working branch, and each sub-branch is configured with corresponding editing and proofreading functions. If the editors and proofreaders agree on the content of the interaction and confirm it, the content of the interaction will be updated to the main branch. The editing includes multiple processes, and the proofreading includes multiple processes; The correspondence between editing and proofreading is pre-configured; An encryption key is generated based on the edited and proofread attribute information. The interactive content is then encrypted using the encryption key for data interaction. This includes: Editing user-uploaded version data involves encrypting the data using an encryption key generated based on the editor's attribute information, and then transmitting the encrypted ciphertext data interactively. Proofreading user-uploaded proofread version data involves encrypting the data using an encryption key generated based on the proofreader's attribute information, and then transmitting the encrypted ciphertext data interactively. The encryption key is generated based on the attribute information of the user who edits or proofreads the user, the attribute information including the identity identifier; The corresponding version of the work is encrypted using the encryption key to obtain the encrypted work; The encryption key is generated based on the user profile of the user who edits or proofreads the user.

2. The e-book editing and proofreading method based on the Git protocol according to claim 1, characterized in that: Each edit and proofreading modification is assigned a unique identifier for version control management.

3. The e-book editing and proofreading method based on the Git protocol according to claim 2, characterized in that: The edited and proofread content uploaded and updated is checked and compared with the content saved on the Git remote server to ensure that there are no discrepancies or conflicts between the uploaded and updated content and the content already saved on the remote server; if discrepancies or conflicts exist, follow the discrepancy and conflict guidance prompts.

4. The e-book editing and proofreading method based on the Git protocol according to claim 3, characterized in that: Grant corresponding operation permissions for the editing and proofreading.

5. An eBook editing and proofreading system based on the Git protocol, the system comprising: One or more processors; Storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the Git protocol-based ebook editing and proofreading method as described in any one of claims 1-4.

Images