CN116383546A

CN116383546A - File processing method, system, computer device and computer readable storage medium

Info

Publication number: CN116383546A
Application number: CN202310661481.XA
Authority: CN
Inventors: 彭宇; 周超; 吕江波; 沈小勇
Original assignee: Beijing Simou Intelligent Technology Co ltd; Shenzhen Smartmore Technology Co Ltd
Current assignee: Beijing Simou Intelligent Technology Co ltd; Shenzhen Smartmore Technology Co Ltd
Priority date: 2023-06-06
Filing date: 2023-06-06
Publication date: 2023-07-04
Anticipated expiration: 2043-06-06
Also published as: CN116383546B

Abstract

The application relates to a file processing method, a file processing device, computer equipment and a computer readable storage medium. The method comprises the following steps: acquiring node attribute data of rich text nodes in a browser; the rich text node is used for describing rich text content displayed by the browser; acquiring a reference resource referenced by a first node according to a resource storage path in node attribute data of the first node; replacing the resource storage path with a target path to obtain attribute data to be written of the first node; the target path is used for indicating the position of the reference resource to be stored at the server; writing attribute data to be written of the first node into a hypertext document; the hypertext document and the reference resource after the data writing are sent to the server, so that the server stores the reference resource according to the target path; and acquiring corresponding reference resources according to the target path in the hypertext file, and generating a file in a non-editing format based on the acquired reference resources and the hypertext file. By adopting the method and the device, the accuracy of file processing can be improved.

Description

File processing method, system, computer device and computer readable storage medium

Technical Field

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

Background

With the development of internet technology, it has become a common requirement to write rich text on Web browsers. Compared with common texts, the rich text has richer formats, stronger expression capability and more attractive appearance. However, how to export rich text into a non-edited format file, such as a PDF file, remains a big challenge.

In the conventional art, print contents in a non-editing format are directly output using the print function of the Web browser. However, there is often a difference between the print content and the rich text content of the original web page, and the problem that the derived file is inaccurate cannot be avoided.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a file processing method, system, computer device, computer readable storage medium, and computer program product that can improve the accuracy of file processing.

In a first aspect, the present application provides a file processing method, including:

acquiring node attribute data of rich text nodes in a browser; the rich text node is used for describing rich text content displayed in the browser; the rich text node in the browser comprises a first node;

Acquiring a resource referenced in a first node according to a resource storage path in node attribute data of the first node to obtain a referenced resource;

replacing the resource storage path with a target path to obtain attribute data to be written of the first node; the target path is used for indicating the position of the reference resource to be stored at the server;

writing attribute data to be written of the first node into the created hypertext document;

the hypertext document and the reference resource after the data writing are sent to the server to instruct the server to store the reference resource according to the target path;

and acquiring corresponding reference resources according to the target path written in the hypertext document, and generating a document in a non-editing format based on the acquired reference resources and the hypertext document.

In a second aspect, the present application provides a document processing system, comprising:

the browser is used for acquiring node attribute data of the rich text nodes; the rich text node is used for describing rich text content displayed in the browser; the rich text node in the browser comprises a first node; acquiring a resource referenced in a first node according to a resource storage path in node attribute data of the first node to obtain a referenced resource; replacing the resource storage path with a target path to obtain attribute data to be written of the first node; the target path is used for indicating the position of the reference resource to be stored at the server; writing attribute data to be written of the first node into the created hypertext document; sending the hypertext document and the quoted resource after writing the data to a server;

The server side is used for storing the reference resources according to the target path, acquiring the corresponding reference resources according to the target path written in the hypertext document, and generating a document in a non-editing format based on the acquired reference resources and the hypertext document.

In a third aspect, the present application provides a computer device comprising a memory storing a computer program and a processor implementing the steps of the method described above when the processor executes the computer program.

In a fourth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of the method described above.

In a fifth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of the method described above.

The file processing method, the file processing system, the computer equipment, the computer readable storage medium and the computer program product acquire node attribute data of rich text nodes in a browser, acquire resources referenced in a first node of a resource storage path in the node attribute data, acquire referenced resources, and replace the resource storage path in the node attribute data with a target path to acquire attribute data to be written of the first node in order to avoid the condition that a server cannot access the resource storage path. And writing the attribute data to be written of the first node into the created hypertext file, and sending the hypertext file and the reference resource after writing the data to the server to instruct the server to store the reference resource according to the target path, so that the server can acquire the corresponding reference resource according to the target path written in the hypertext file, and generate a file in a non-editing format based on the acquired reference resource and the hypertext file.

Drawings

FIG. 1 is an application environment diagram of a file processing method according to an embodiment of the present application;

FIG. 2 is a schematic flow chart of a document processing method according to an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of a target path replacement according to an embodiment of the present disclosure;

FIG. 4 is a flowchart of generating a resource locator according to an embodiment of the present disclosure;

FIG. 5 is a simplified flowchart of a document processing method according to an embodiment of the present disclosure;

FIG. 6 is a block diagram of a file processing system according to an embodiment of the present disclosure;

FIG. 7 is a block diagram of a document processing apparatus according to an embodiment of the present disclosure;

FIG. 8 is an internal block diagram of a computer device according to an embodiment of the present application;

FIG. 9 is an internal block diagram of another computer device according to an embodiment of the present application;

fig. 10 is an internal structural diagram of a computer-readable storage medium according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.

The file processing method provided by the embodiment of the application can be applied to an application environment shown in fig. 1. Wherein the browser 102 communicates with the server 104 via a communication network. The data storage system may store data that the server 104 needs to process. The data storage system may be integrated on the server 104 or may be located on a cloud or other network server. The browser 102 may obtain node attribute data for the rich text node; the rich text node is used for describing rich text content displayed in the browser; the rich text node in the browser comprises a first node; acquiring a resource referenced in a first node according to a resource storage path in node attribute data of the first node to obtain a referenced resource; replacing the resource storage path with a target path to obtain attribute data to be written of the first node; the target path is used for indicating the position of the reference resource to be stored at the server; writing attribute data to be written of the first node into the created hypertext document; the hypertext document and the referenced resource after writing the data are sent to the server 104.

The server 104 may store the reference resources according to the target path, obtain the corresponding reference resources according to the target path written in the hypertext document, and generate a document in a non-editing format based on the obtained reference resources and the hypertext document.

The browser 102 may be, but not limited to, built in various personal computers, notebook computers, smart phones, tablet computers, internet of things devices and portable wearable devices, and the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart vehicle devices and the like. The portable wearable device may be a smart watch, smart bracelet, headset, or the like. The server 104 may be implemented as a stand-alone server or a server cluster formed by a plurality of servers.

As shown in fig. 2, an embodiment of the present application provides a file processing method, which is described by taking application of the method to the browser 102 in fig. 1 as an example. The method comprises the following steps:

s202, acquiring node attribute data of rich text nodes in a browser; the rich text node is used for describing rich text content displayed in the browser; the rich text node in the browser includes a first node.

The rich text is a cross-platform document format and is a content mode for displaying multimedia features such as characters, pictures, music and the like. Rich text is used as a basis for page generation. It will be appreciated that the rich text editor embedded within the browser maintains a data structure that includes a variety of rich text nodes for describing all of the rich text content. The data structure may be an array comprising a plurality of rich text nodes.

The node attribute data of the rich text node is used to construct content elements of the markup language. The browser is used to present the rich text content on the page according to the constructed content elements of the markup language, i.e. the browser can change the content elements of the markup language into the rich text content visible on the page. The first node refers to a rich text node in which a resource storage path exists in node attribute data.

Illustratively, the rich text editor embedded in the browser is used for editing rich text, and edited rich text data comprises a plurality of rich text nodes. The browser can traverse a plurality of rich text nodes in the rich text data, and obtain node attribute data of the traversed rich text nodes.

In some embodiments, the rich text node may include at least one of a picture node, a title node, a table node, an interface node, a link node, a video node, or the like. The title node is used for describing titles in rich text content displayed in the browser. The form node is used for describing a form in rich text content displayed in the browser. The interface node is used for describing an interface in the rich text content displayed in the browser. The link node is used to describe links in rich text content presented in the browser. The video node is used for describing videos in rich text content displayed in the browser.

In some embodiments, the content in the file in the non-editing format is tiled, and for a third node that does not meet the tiling requirement, the browser may perform tiling on node attribute data of the third node to obtain attribute data to be written of the third node, so as to avoid occurrence of hidden content. For example, for a form node where a landscape scrollbar exists, the browser may add the style "max-width: 100%" to eliminate the landscape scrollbar, restricting the out of form content to the screen range. For interface nodes where tab switching exists, the browser may expand all content corresponding to the tab.

In some embodiments, the browser may tile the node attribute data of the third node and then add a corresponding tag to obtain attribute data to be written of the third node.

In some embodiments, the rich text data may include a picture node. As shown in table 1, node attribute data of the picture node is provided.

TABLE 1

The node attribute data of the picture node may include a node type, a picture link, a picture description, a width, and a height.

S204, acquiring the referenced resources in the first node according to the resource storage path in the node attribute data of the first node, and obtaining the referenced resources.

Where the referenced resource refers to the resource referenced in the rich text node. The resource storage path is used to locate the referenced resource. The browser may retrieve the referenced resource from the location indicated by the resource storage path.

Illustratively, the browser may traverse rich text nodes in the browser. And aiming at the traversed rich text node, determining the rich text node as a first node under the condition that the node attribute data of the rich text node comprises a resource storage path, and acquiring the resource referenced in the first node from the resource storage path to obtain the referenced resource.

It is understood that the browser may determine attribute data to be written for each rich text node and write the attribute data to be written for each rich text node into the created hypertext document. The node attribute data does not necessarily meet the generation requirement of the server for the file in the non-editing format, so that the node attribute data of the rich text node which does not meet the generation requirement needs to be processed to obtain the attribute data to be written which meets the file generation requirement. The file generation requirement is used for representing the requirement that the server generates a file in a non-editing format according to the hypertext file. For example, the server needs to acquire corresponding resources according to the path in the attribute data written in the hypertext document, so that the generated non-editing format document has the resources.

In some embodiments, the reference resource may be at least one of a local resource or an external resource, or the like. It will be appreciated that the hypertext document generated for each rich text node can be used to be read by a browser to expose the rich text content described by each rich text node. Since neither the local nor external resources are directly embodied in the hypertext files generated for each rich text node, the hypertext files need to be retrieved from either local or external when read. The browser has the ability to acquire the referenced resource from the location indicated by the resource storage path, but the server does not necessarily have this ability. After the browser sends the acquired reference resource to the server, the browser is used for supporting the server to acquire the reference resource when the hypertext document is opened. The hypertext file generated for each rich text node may be a hypertext file after writing data.

In some embodiments, the target path may include at least one of a common access path or a relative path. The relative path is used to characterize the positional relationship between the referenced resources stored in the server and the hypertext documents generated for each rich text node. The common access path is used to locate referenced resources stored in the server. It is understood that the common access path may be an absolute path.

S206, replacing the resource storage path with a target path to obtain attribute data to be written of the first node; the target path is used to indicate the location where the referenced resource is to be stored at the server.

For example, the browser may replace the resource storage path in the node attribute data of the first node with the target path and then add a corresponding tag to obtain attribute data to be written of the first node.

It can be appreciated that the browser can access the resource storage path, acquire the reference resource, and the server side has a situation that the resource storage path cannot be accessed. For example, the browser has access rights of the resource storage path, but the server side has access rights of the resource storage path, and the server side cannot acquire the reference resource due to the limit of the rights. At least part of the cascading style sheets (Cascading Style Sheets, CSS) or font files running in the browser are not available to the server, e.g., mathematical formula nodes introduced through the software library (Node Package Manager, NPM). Therefore, the browser designates the target path to store in the server after acquiring the reference resource, and the problem that the generated file in the non-editing format is incomplete due to the fact that the server cannot acquire the reference resource is avoided.

In some embodiments, as shown in FIG. 3, a schematic diagram of a target path replacement is provided. The rich text node may include a picture node. The resource storage path of the picture node is http:// x.com/a.png, the browser acquires picture resources from the http:// x.com/a.png, designates the target path as Image/a.png, replaces the target path, and replaces the http:// x.com/a.png with Image/a.png.

S208, writing the attribute data to be written of the first node into the created hypertext document.

The hypertext document is a descriptive text document composed of markup language commands, and belongs to a static webpage document. The markup language includes a series of markup tags for concatenating the rich text data into a whole. When the hypertext document is opened by the browser, the page is presented in the browser. The hypertext document may include at least one content element composition of pictures, links, text, sound, or video, etc.

For example, the browser may write the attribute data to be written of the first node carrying the corresponding markup tag into the created hypertext document. It will be appreciated that markup tags are the basic units in markup language used to construct the text and layout of a page. The visual data and layout of the page indicated by the hypertext document are related to the non-editing format document content and content layout generated according to the hypertext document, so that the document content and content layout more suitable for the non-editing format document can be obtained by adaptively adding the corresponding mark label after processing the node attribute data.

In some embodiments, the markup language is hypertext markup language (Hyper Text Markup Language, HTML). The markup tags are HTML tags. The content elements are HTML elements. The hypertext file is an HTML file.

S210, sending the hypertext document and the reference resource after writing the data to the server to instruct the server to store the reference resource according to the target path.

Wherein the non-editing format is a document format that cannot be directly edited. It will be appreciated that elements in a file in an editable format may be directly edited, whereas elements in a file in a non-editable format need to be parsed and then converted to editable elements before being edited.

By way of example, the non-editing format file may be a PDF file. Wherein PDF (portable document format) is a portable document file format. The browser can upload the hypertext document, the reference resource and the target path of the reference resource after writing the data to the server. The server may store the referenced resource under the target path.

In some embodiments, in the case where attribute data to be written of each rich text node in the browser is written to a hypertext document, the browser may upload the hypertext document and the reference resource after the data is written to the server. It can be understood that the hypertext file after writing data includes attribute data to be written of all rich text nodes in the browser. The server may store the referenced resources according to the target path written in the hypertext document. It can be understood that the target path ends with the file name, and the server can determine the target path of each reference resource by comparing the file name of the reference resource with the file names in the target path, so that the reference resource is stored according to the target path, and the browser is not required to independently send the target path of the reference resource.

S212, acquiring corresponding reference resources according to the target path written in the hypertext document, and generating a document in a non-editing format based on the acquired reference resources and the hypertext document.

For example, the server may perform a file generation process to generate a file in a non-editing format. When the file generation processing is executed, corresponding reference resources are acquired according to the target path written in the hypertext file. The server may generate a file in a non-editing format based on the acquired referenced resources and the hypertext file through a file conversion tool.

It can be seen that, in this embodiment of the present application, node attribute data of a rich text node in a browser is obtained, for a first node having a resource storage path in the node attribute data, a resource referenced in the first node is obtained, so as to obtain a referenced resource, and in order to avoid a situation that a server cannot access the resource storage path, the resource storage path in the node attribute data is replaced with a target path, so as to obtain attribute data to be written in the first node. And writing the attribute data to be written of the first node into the created hypertext file, and sending the hypertext file and the reference resource after writing the data to the server to instruct the server to store the reference resource according to the target path, so that the server can acquire the corresponding reference resource according to the target path written in the hypertext file, and generate a file in a non-editing format based on the acquired reference resource and the hypertext file.

In some embodiments, the target path comprises a relative path; the method further comprises the steps of: determining a relative path of the reference resource according to a preset relative storage position relation between the reference resource and the created hypertext document; sending the hypertext document and the reference resource after writing the data to the server to instruct the server to store the reference resource according to the target path, comprising: the method comprises the steps of sending a hypertext document and a reference resource after writing data to a server to instruct the server to store the reference resource and the hypertext document under the same folder according to a relative path; wherein, the storage positions of the reference resource and the hypertext document under the same folder satisfy the relative storage position relation.

Illustratively, a preset relative storage location relationship is used to characterize the relative locations of the referenced resources and the created hypertext documents under the same folder. The browser may determine the path of the referenced resource relative to the created hypertext document under the same folder, resulting in a relative path. The browser may upload the hypertext document, the referencing resource, and the target path of the referencing resource to the server. In the case that the target path of the reference resource is a relative path, the server may store the reference resource and the hypertext document under the same folder according to the relative path.

In some embodiments, when executing the file generation process, the server may open the hypertext file, and obtain the reference resource from the folder in which the hypertext file is located according to the relative path written in the hypertext file. The server may generate a file in a non-editing format based on the acquired referenced resources and the hypertext file.

It can be seen that, in this embodiment, according to the preset relative storage position relationship between the reference resource and the created hypertext document, the relative path of the reference resource is determined; the hypertext document and the reference resource after the data writing are sent to the server to instruct the server to store the reference resource and the hypertext document under the same folder according to the relative path, so that the server can acquire the complete reference resource and the hypertext document based on the relative path when executing the document generation processing, thereby generating a more accurate document in a non-editing format.

In some embodiments, the target path includes at least one of a relative path or a common access path. In the case where the target path of the referenced resource is a common access path, the server may store the referenced resource to a storage location indicated by the common access path.

In some embodiments, the target path further comprises a common access path; determining a relative path of the reference resource according to a preset relative storage position relation between the reference resource and the created hypertext document, wherein the relative path comprises the following steps: under the condition that the reference resource accords with the visual display condition of the file in the non-editing format, determining a relative path of the reference resource according to a preset relative storage position relationship between the reference resource and the created hypertext file; the method further comprises the steps of: under the condition that the reference resource does not accord with the visual display condition of the file in the non-editing format, determining a public access path of the reference resource; and the generated file in the non-editing format presents the public access path of the reference resource which does not meet the visual display condition and the reference resource which meets the visual display condition.

Wherein the visual presentation condition is used to indicate the node type supported in the non-editing format. It can be understood that the non-editing format does not support video playing, that is, video resources cannot exist in the file in the non-editing format, so that the server needs to convert the referenced video resources into corresponding public access paths, and further can access the corresponding video resources through the public access paths in the file in the non-editing format, so that the integrity of the file in the non-editing format can be ensured. The non-editing format supports picture exhibition, that is, a picture resource can exist in a file in the non-editing format, so that the service end exists the picture resource in the file in the non-editing format generated based on the acquired picture resource and the hypertext file.

For example, for a referenced resource that meets the visual presentation conditions of a file in a non-editing format, the browser may determine the relative path of the referenced resource. For a referenced resource that does not meet the visual presentation conditions of a file in a non-editing format, the browser may determine a common access path for the referenced resource. After replacing the resource storage path with the public access path, the reference resource is not directly embedded in the hypertext document, but the public access path of the reference resource is embedded.

It will be appreciated that the common access path does not have permission control and that responsive referenced resources can be accessed through the common access path presented therein when the non-editable format file is viewed. It will be appreciated that a reference resource meeting the requirements of a non-editable format is obtained when the hypertext document is opened, whereas a reference resource not meeting the requirements of a non-editable format is obtained when the hypertext document is opened, only the common access path of the reference resource is obtained. It should be noted that, the reference resource at the storage location indicated by the public access path does not meet the requirement of the non-editing format, and when the file generation process is executed, the hypertext file is opened by the server, and the server does not need to obtain the corresponding reference resource according to the public access path.

In some embodiments, the referenced resources that do not conform to the visual presentation conditions of the non-editing formatted file include at least one of a video resource or a file resource, etc. It will be appreciated that PDF formatted files cannot play video or embed additional files, so the common access path of video assets and file assets replaces video assets and file assets.

It can be seen that, in this embodiment, under the condition that the reference resource meets the visual display condition of the file in the non-editing format, the relative path of the reference resource is determined according to the preset relative storage position relationship between the reference resource and the created hypertext file, and then the hypertext file and the reference resource are placed under the same folder according to the relative path, and the folder is deleted after the file in the non-editing format is generated, so that the storage resource of the server can be saved. Under the condition that the reference resource does not accord with the visual display condition of the file in the non-editing format, the public access path of the reference resource is determined, the reference resource which does not accord with the visual display condition can be converted into the public access path, and the integrity of the reference resource included in the file in the non-editing format can be ensured.

In some embodiments, the rich text node in the browser includes a second node to be bookmarked, and the node attribute data written into the hypertext file by the second node carries a corresponding title tag; the title label is used for indicating the server to generate the bookmark in the file in the non-editing format.

Illustratively, the server generates a file in a non-editing format based on the acquired referenced resources and the hypertext file via a file conversion tool. Wherein the file conversion tool generates bookmarks for the node attribute data marked by the title tags in the hypertext document. The level of the title tag is consistent with the level of the bookmark being generated, e.g., a primary title tag corresponds to a primary bookmark being generated.

In some embodiments, in the case of a line feed of linked text in a hypertext document, the line in which the linked text is located in a non-editable format document generated by the document conversion tool can click to jump. The browser may split the entire linked text in the hypertext document into multiple links of a single character. For example, < a > hi > will be converted to < a > h > a < a > i. Where h and i enable hopping to the hi link.

In some embodiments, the second node to generate the bookmark includes a title node and a page title node. The page title node is different from the title nodes of various levels, rich text content described by the page title node is displayed in the title bar of the browser, and rich text content described by the title nodes of various levels is displayed in the page of the browser.

In some embodiments, the rich text node comprises a page title node. The node attribute data written into the hypertext file by the page title node carries a primary title label, namely the attribute data to be written of the page title node is the node attribute data added with the primary title label. And under the condition that the rich text node in the browser comprises the page title node, adding a lower-level title label to the node attribute data of the title node to obtain the attribute data to be written of the title node. It will be appreciated that the hierarchy of page header nodes is highest. It should be noted that, when the user writes rich text, the primary title is used as a large title of the rich text content, but when a file in a non-editing format is generated, we expect the page title to be a primary bookmark, and the primary title in the rich text content to be a secondary bookmark. So the node to be bookmarked in the original rich text content needs to be "downgraded", i.e. h1 becomes h2, h2 becomes h3, and so on.

It can be seen that, in this embodiment, the rich text node includes a node to be bookmarked, and the node to be bookmarked writes to the node attribute data in the hypertext file to carry a corresponding title tag; the title label is used for indicating the server to generate the bookmark in the file in the non-editing format, and the file in the non-editing format carries the bookmark, so that the readability of the file is improved, and the file in the non-editing format is more convenient to read.

In some embodiments, the method further comprises: determining a second node to be bookmarked according to the node type of the rich text node in the browser; determining a hierarchical relationship between the second nodes; adding a title label of a corresponding level to the node attribute data of the second node according to the hierarchical relationship to obtain attribute data to be written of the second node; writing attribute data to be written of a first node into a created hypertext document, comprising: and writing the attribute data to be written of the first node and the attribute data to be written of the second node into the created hypertext file.

Illustratively, the node attribute data includes a node type. The browser may obtain a preset node type. And aiming at the traversed rich text node, taking the rich text node as a second node for generating the bookmark when the node type of the rich text node is a preset node type. The browser may determine a hierarchical relationship between the second nodes. The hierarchical relationship is used to characterize the hierarchy at which each node to be bookmarked is located. The browser can add the title label of the level consistent with the level of the node to be bookmarked to the node attribute data of the node to be bookmarked to obtain attribute data to be written of the second node. The browser may write the attribute data to be written of the first node and the attribute data to be written of the second node to the created hypertext document.

In some embodiments, the browser may determine a hierarchical relationship between the plurality of second nodes based on the node type of the second nodes. It can be understood that the browser is preset with the priority corresponding to each preset node type, and the hierarchy in which each second node is located can be determined by comparing the priorities of the node types of the plurality of second nodes, so as to obtain the hierarchy relationship. For example, the second node includes a page title node, a primary title node, and a secondary title node. The priority order is page title type, primary title type and secondary title type. Accordingly, the page header node is at the highest level, the level of the primary header node is inferior to the page header node, and the level of the secondary header node is inferior to the primary header node.

It can be seen that, in this embodiment, according to the node type of the rich text node in the browser, a second node to be bookmarked is determined; determining a hierarchical relationship between the second nodes; adding a corresponding level of title label to the node attribute data of the second node according to the hierarchical relationship to obtain attribute data to be written of the second node, writing the attribute data to be written of the first node and the attribute data to be written of the second node into the created hypertext file, and further generating a bookmark in a file in a non-editing format aiming at the title label in the hypertext file by a file conversion tool, so that the readability is improved.

In some embodiments, sending the hypertext document and the referenced resource after writing the data to the server to instruct the server to store the referenced resource along the target path includes: determining style configuration data in a browser; style configuration data is set for visual requirements of the non-editing format file and is used for indicating styles of the non-editing format file; style configuration data, a hypertext document, a reference resource and a target path are sent to a server; the server generates a file in a non-editing format based on the style configuration data, the acquired reference resource and the hypertext file.

Illustratively, the style configuration data may include a cascading style sheet and header footer data set for the non-editing format. The cascading style sheet set for the non-editing format is used to adjust the style of the whole, such as at least one of font size or paragraph spacing, etc., to suit the reading of the non-editing format file. The file conversion tool supports custom header footers. The header footer data may be a header footer file. The header footer file is in a hypertext document format, i.e., the header footer file is an HTML file. The browser may upload the cascading style sheet and header footer data, style configuration data, hypertext files, referenced resources, and target paths set for the non-editing format to the server. When executing file generation processing, the file conversion tool in the server may open the hypertext file, acquire corresponding reference resources according to the relative path written in the hypertext file, and generate a file in a non-editing format based on the acquired reference resources, the hypertext file, the cascading style sheet set for the non-editing format, and header footer data.

In some embodiments, header footer data is configured in the server. It can be understood that, the header footer file in the browser is more customized than the header footer data in the server, and the header footer file summarized by the browser is more convenient to modify.

It can be seen that, in the present embodiment, style configuration data in the browser is determined; and sending the style configuration data, the hypertext file, the reference resource and the target path to the server, and supporting the self definition of the style of the file by the style configuration data, so that the file in the non-editing format meets the reading requirement better, and the readability of the file is improved.

In some embodiments, sending the hypertext document and the referenced resource after writing the data to the server to instruct the server to store the referenced resource along the target path includes: and sending the hypertext document and the reference resource after the data writing to the server to instruct the server to store the reference resource to the folder according to the target path, generating a resource positioning address for the folder, and acquiring the reference resource and the hypertext document according to the resource positioning address by a document conversion tool to generate a document in a non-editing format.

Illustratively, the browser may upload the hypertext document, the referenced resource, and the target path of the referenced resource after writing the data to the server. In the case that the target path of the reference resource is a relative path, the server may save the reference resource to the folder according to the relative path. In the case where the target path of the referenced resource is a common access path, the server may save the referenced resource to the location indicated by the common access path. The server side can generate a resource positioning address aiming at the file folder, and acquire the reference resource and the hypertext file according to the resource positioning address through the file conversion tool so as to generate a file in a non-editing format.

In some embodiments, the server deletes the folder in which the hypertext document is located when the generation of the non-edited file is completed. It will be appreciated that the hypertext document and the referenced resources of the target path as relative paths will be deleted, but the referenced resources of the target path as common access paths will not be deleted.

In some embodiments, as shown in FIG. 4, a flow diagram for generating a resource location address is provided. The server may save the referenced resource and the hypertext document to the same folder. Where/img is the target path of the picture resource,/video is the target path of the video resource,/file is the target path of the file resource,/ttf is the target path of the font file resource,/css is the target path of the cascading style sheet and index. The server may host a static file, generating an accessible resource location address.

It can be seen that, in this embodiment, the hypertext file and the reference resource after writing the data are sent to the server, so as to instruct the server to save the reference resource to the folder according to the target path, generate a resource location address for the folder, and obtain the reference resource and the hypertext file according to the resource location address by using the file conversion tool to generate a file in a non-editing format, where the integrity of the reference resource and the hypertext file ensures the consistent export from the rich text data to the file in the non-editing format, and improves the accuracy of file processing.

In some embodiments, as shown in FIG. 5, a simplified flow diagram of a file processing method is provided. The browser may obtain edited rich text data. The rich text data includes a plurality of rich text nodes. The browser can traverse rich text nodes in the rich text data, and acquire node attribute data aiming at the traversed rich text nodes. The browser can perform resource extraction on the rich text data, acquire the reference resource according to the resource storage path and designate a target path of the reference resource under the condition that the node attribute data comprises the resource storage path. The browser can replace the resource storage path in the node attribute data with the target path to update the node attribute data of the rich text node. The browser can add matched marking labels to node attribute data of a plurality of rich text nodes and then write the node attribute data into the created hypertext file, so that conversion from the rich text data to the hypertext file is realized. The browser may determine a cascading style sheet set for the non-editing format and a header footer file set for the non-editing format and upload the quote resources, the hypertext files, the cascading style sheet, and the header footer file together to the server. The server may save the referenced resource, the hypertext document, the cascading style sheet, and the header and footer document under the same folder and generate a resource location address. The file conversion tool may access the resource location address to generate a file in a non-editing format based on the referenced resource, the hypertext document, the cascading style sheet, and the header footer file. Header footer files are used to define the headers and footers of a file in a non-editing format. After the non-editing format file is generated, the server may delete the folder to release the storage resource.

It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the application also provides a file processing system. The implementation of the solution provided by the system is similar to the implementation described in the above method, so the specific limitation in one or more embodiments of the file processing system provided below may refer to the limitation of the file processing method hereinabove, and will not be repeated herein.

As shown in fig. 6, an embodiment of the present application provides a file processing system 600, including:

a browser 602, configured to obtain node attribute data of a rich text node; the rich text node is used for describing rich text content displayed in the browser 602; the rich text nodes in browser 602 include a first node; acquiring a resource referenced in a first node according to a resource storage path in node attribute data of the first node to obtain a referenced resource; replacing the resource storage path with a target path to obtain attribute data to be written of the first node; the target path is used to indicate the location where the referenced resource is to be stored at the server 604; writing attribute data to be written of the first node into the created hypertext document; the hypertext document and the referenced resource after writing the data are sent to the server 604.

The server 604 is configured to store the reference resource according to the target path, obtain the corresponding reference resource according to the target path written in the hypertext document, and generate a document in a non-editing format based on the obtained reference resource and the hypertext document.

In some embodiments, the target path comprises a relative path; the browser 602 is further configured to determine a relative path of the reference resource according to a preset relative storage location relationship between the reference resource and the created hypertext document; sending the hypertext document and the reference resource after the data writing to the server 604; the server 604 is further configured to store the reference resource and the hypertext document under the same folder according to the relative path; wherein, the storage positions of the reference resource and the hypertext document under the same folder satisfy the relative storage position relation.

In some embodiments, the target path further comprises a common access path; a browser 602, configured to determine a relative path of a reference resource according to a preset relative storage location relationship between the reference resource and a created hypertext document under a condition that the reference resource meets a visual display condition of a file in a non-editing format; under the condition that the reference resource does not accord with the visual display condition of the file in the non-editing format, determining a public access path of the reference resource; and the generated file in the non-editing format presents the public access path of the reference resource which does not meet the visual display condition and the reference resource which meets the visual display condition.

In some embodiments, the rich text node in the browser includes a second node to be bookmarked, and the node attribute data written into the hypertext file by the second node carries a corresponding title tag; the title tag is used to instruct the server 604 to generate bookmarks in a file in a non-editing format.

In some embodiments, the browser 602 is further configured to determine a second node to generate a bookmark according to the node type of the rich text node in the browser 602; determining a hierarchical relationship between the second nodes; adding a title label of a corresponding level to the node attribute data of the second node according to the hierarchical relationship to obtain attribute data to be written of the second node; and writing the attribute data to be written of the first node and the attribute data to be written of the second node into the created hypertext file.

In some embodiments, browser 602 is also used to determine style configuration data; style configuration data is set for visual requirements of the non-editing format file and is used for indicating styles of the non-editing format file; sending style configuration data, hypertext documents, referenced resources, and target paths to a server 604; the server 604 is further configured to generate a file in a non-editing format based on the style configuration data, the acquired referencing resources, and the hypertext file.

In some embodiments, browser 602 is further configured to send the hypertext document and the referenced resource after the written data to server 604; the server 604 is further configured to save the reference resource to a folder according to the target path, generate a resource location address for the folder, and obtain, by using a file conversion tool, the reference resource and the hypertext file according to the resource location address to generate a file in a non-editing format.

As shown in fig. 7, an embodiment of the present application provides a document processing apparatus 700, including:

an obtaining module 702, configured to obtain node attribute data of a rich text node in a browser; the rich text node is used for describing rich text content displayed in the browser; the rich text node in the browser includes a first node.

And the determining module 704 is configured to obtain, according to the resource storage path in the node attribute data of the first node, a resource referenced in the first node, and obtain a referenced resource.

An updating module 706, configured to replace the resource storage path with the target path to obtain attribute data to be written of the first node; the target path is used to indicate the location where the referenced resource is to be stored at the server.

A writing module 708, configured to write attribute data to be written of the first node into the created hypertext document;

an uploading module 710, configured to send the hypertext document and the reference resource after writing the data to the server, so as to instruct the server to store the reference resource according to the target path; and acquiring corresponding reference resources according to the target path written in the hypertext document, and generating a document in a non-editing format based on the acquired reference resources and the hypertext document.

In some embodiments, the target path comprises a relative path; the updating module 706 is configured to determine a relative path of the reference resource according to a preset relative storage location relationship between the reference resource and the created hypertext document; the uploading module 710 is configured to send the hypertext document and the reference resource after writing the data to the server, so as to instruct the server to store the reference resource and the hypertext document under the same folder according to the relative path; wherein, the storage positions of the reference resource and the hypertext document under the same folder satisfy the relative storage position relation.

In some embodiments, the target path further comprises a common access path; the updating module 706 is configured to determine, when the reference resource meets a visual display condition of a file in a non-editing format, a relative path of the reference resource according to a preset relative storage location relationship between the reference resource and the created hypertext file; under the condition that the reference resource does not accord with the visual display condition of the file in the non-editing format, determining a public access path of the reference resource; and the generated file in the non-editing format presents the public access path of the reference resource which does not meet the visual display condition and the reference resource which meets the visual display condition.

In some embodiments, the writing module 708 is configured to determine a second node to generate a bookmark according to a node type of the rich text node in the browser; determining a hierarchical relationship between the second nodes; adding a title label of a corresponding level to the node attribute data of the second node according to the hierarchical relationship to obtain attribute data to be written of the second node; and writing the attribute data to be written of the first node and the attribute data to be written of the second node into the created hypertext file.

In some embodiments, the upload module 710 is configured to determine style configuration data in a browser; style configuration data is set for visual requirements of the non-editing format file and is used for indicating styles of the non-editing format file; style configuration data, a hypertext document, a reference resource and a target path are sent to a server; the server generates a file in a non-editing format based on the style configuration data, the acquired reference resource and the hypertext file.

In some embodiments, the upload module 710 is configured to send the hypertext document and the reference resource after writing the data to the server, to instruct the server to save the reference resource to the folder according to the target path, to generate a resource location address for the folder, and to obtain, by the file conversion tool, the reference resource and the hypertext document according to the resource location address to generate a document in a non-editing format.

The respective modules in the above-described file processing apparatus may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In some embodiments, a computer device is provided, which may be a server, and the internal structure of which may be as shown in fig. 8. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is used to store hypertext documents and referenced resources. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement the steps in the file processing method described above.

In some embodiments, a computer device is provided, where the computer device may be a terminal, a browser is built in the terminal, and an internal structure of the terminal may be as shown in fig. 9. The computer device includes a processor, a memory, an input/output interface, a communication interface, a display unit, and an input device. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement the steps in the file processing method described above. The display unit of the computer device is used for forming a visual picture, and can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen; the input device of the computer equipment can be a touch layer covered on a display screen, can also be keys, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.

It will be appreciated by those skilled in the art that the structures shown in fig. 8 or 10 are merely block diagrams of portions of structures related to the aspects of the present application and are not intended to limit the computer devices to which the aspects of the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or may have a different arrangement of components.

In some embodiments, a computer device is provided, comprising a memory storing a computer program and a processor implementing the steps of the method embodiments described above when the computer program is executed.

In some embodiments, an internal structural diagram of a computer-readable storage medium is provided as shown in fig. 10, the computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the method embodiments described above.

In some embodiments, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.

It should be noted that, the user information (including, but not limited to, user equipment information, user personal information, etc.) and the data (including, but not limited to, data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data are required to comply with the related laws and regulations and standards of the related countries and regions.

Those skilled in the art will appreciate that implementing all or part of the above described embodiment methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the various embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as Static Random access memory (Static Random access memory AccessMemory, SRAM) or dynamic Random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the various embodiments provided herein may include at least one of relational databases and non-relational databases. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic units, quantum computing-based data processing logic units, etc., without being limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The above examples only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the present application. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application shall be subject to the appended claims.

Claims

1. A document processing method, comprising:

acquiring the referenced resources in the first node according to the resource storage path in the node attribute data of the first node to obtain referenced resources;

Replacing the resource storage path with a target path to obtain attribute data to be written of the first node; the target path is used for indicating a position of the reference resource to be stored at the server;

sending the hypertext document and the reference resource after writing data to the server to instruct the server to store the reference resource according to the target path;

and acquiring corresponding reference resources according to the target path written in the hypertext file, and generating a file in a non-editing format based on the acquired reference resources and the hypertext file.

2. The method of claim 1, wherein the target path comprises a relative path; the method further comprises the steps of:

determining a relative path of the reference resource according to a preset relative storage position relation between the reference resource and the created hypertext document;

the sending the hypertext document and the reference resource after writing data to the server to instruct the server to store the reference resource according to the target path includes:

Sending the hypertext document and the reference resource after writing data to the server to instruct the server to store the reference resource and the hypertext document under the same folder according to the relative path;

and the storage positions of the reference resource and the hypertext document under the same folder meet the relative storage position relation.

3. The method of claim 2, wherein the target path further comprises a common access path; the determining the relative path of the reference resource according to the preset relative storage position relation between the reference resource and the created hypertext document comprises the following steps:

under the condition that the reference resource accords with the visual display condition of the file in the non-editing format, determining a relative path of the reference resource according to a preset relative storage position relation between the reference resource and the created hypertext file;

the method further comprises the steps of:

under the condition that the reference resource does not accord with the visual display condition of the file in the non-editing format, determining a public access path of the reference resource;

and the generated file in the non-editing format presents the public access path of the reference resource which does not meet the visual display condition and the reference resource which meets the visual display condition.

4. The method according to claim 1, wherein the rich text node in the browser includes a second node to be bookmarked, and the node attribute data written into the hypertext document by the second node carries a corresponding title tag; the title label is used for indicating the server to generate a bookmark in a file in a non-editing format.

5. The method according to claim 4, wherein the method further comprises:

determining a second node to be bookmarked according to the node type of the rich text node in the browser;

determining a hierarchical relationship between the second nodes;

adding a title label of a corresponding level to the node attribute data of the second node according to the hierarchical relationship to obtain attribute data to be written of the second node;

the writing the attribute data to be written of the first node into the created hypertext file comprises the following steps:

and writing the attribute data to be written of the first node and the attribute data to be written of the second node into the created hypertext file.

6. The method of claim 1, wherein the sending the hypertext document and the referenced resource after writing the data to the server to instruct the server to store the referenced resource along the target path comprises:

Determining style configuration data in a browser; the style configuration data is set for the visual requirement of the file in the non-editing format and is used for indicating the style of the file in the non-editing format;

sending the style configuration data, the hypertext document, the referenced resource and the target path to the server; and the server generates a file in a non-editing format based on the style configuration data, the acquired reference resource and the hypertext file.

7. The method according to any one of claims 1 to 6, wherein the sending the hypertext document and the reference resource after writing data to the server to instruct the server to store the reference resource according to the target path includes:

and sending the hypertext document and the reference resource after writing data to the server to instruct the server to store the reference resource to a folder according to the target path, generating a resource positioning address for the folder, and acquiring the reference resource and the hypertext document according to the resource positioning address by a document conversion tool to generate a document in a non-editing format.

8. The file processing system is characterized by comprising a browser and a server;

the browser is used for acquiring node attribute data of the rich text nodes; the rich text node is used for describing rich text content displayed in the browser; the rich text node in the browser comprises a first node; acquiring the referenced resources in the first node according to the resource storage path in the node attribute data of the first node to obtain referenced resources; replacing the resource storage path with a target path to obtain attribute data to be written of the first node; the target path is used for indicating a position of the reference resource to be stored at the server; writing attribute data to be written of the first node into the created hypertext document; sending the hypertext document and the reference resource after writing data to the server;

the server is used for storing the reference resources according to the target path, acquiring the corresponding reference resources according to the target path written in the hypertext document, and generating a document in a non-editing format based on the acquired reference resources and the hypertext document.

9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 7 when the computer program is executed.

10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 7.