CN112925747A

CN112925747A - File format conversion method and device and computer storage medium

Info

Publication number: CN112925747A
Application number: CN202110347570.8A
Authority: CN
Inventors: 杨涛; 刘丁源
Original assignee: Zhejiang Taimei Medical Technology Co Ltd
Current assignee: Zhejiang Taimei Medical Technology Co Ltd
Priority date: 2021-03-31
Filing date: 2021-03-31
Publication date: 2021-06-08

Abstract

The invention provides a file format conversion method, a file format conversion device and a computer storage medium. The method comprises the following steps: respectively acquiring a first conversion efficiency curve of a first conversion engine and a second conversion efficiency curve of a second conversion engine, wherein the first conversion efficiency curve and the first conversion efficiency curve respectively comprise the relation between the file size and the conversion time; determining an intersection of the first conversion efficiency curve and the second conversion efficiency curve; detecting the size of a file to be converted; comparing the file size at the intersection with the file size to be converted; and determining the conversion engine selected by the file to be converted according to the comparison result.

Description

File format conversion method and device and computer storage medium

Technical Field

The present invention relates to the field of file processing, and in particular, to a method and an apparatus for converting a file format.

Background

In the present day when network technology is commonly applied, various office software such as MS office, Adobe Acrobat and the like have become indispensable application tools. People often need to convert various files into each other based on the needs of some exhibition, network transmission and the like. PDF (Portable Document Format) is a file Format developed by a file exchange in a manner independent of an application program, an operating system, and hardware. The PDF file can guarantee accurate colors and accurate printing effect regardless of the printer on which the PDF file is mounted, that is, the PDF can faithfully reproduce each character, color, and image of the original. These features make it an ideal document format for electronic document distribution and digital information dissemination over the Internet. More and more electronic books, product descriptions, company literature, web materials, and electronic mail are beginning to use PDF formatted files.

Many Office toolkits, such as the aforementioned MS Office, have the function of converting its format into a PDF file by its own conversion engine. For example, WORD, EXCEL and PowerPoint can convert the format of the file into a PDF file. When many files need to be converted into PDF files in bulk, the conversion efficiency of the conversion engine has a very large influence on the conversion time.

Disclosure of Invention

The technical problem to be solved by the invention is to provide a file format conversion method and device, which can improve the efficiency of file format conversion.

In order to solve the above technical problem, the present invention provides a file format conversion method, which comprises the following steps: respectively acquiring a first conversion efficiency curve of a first conversion engine and a second conversion efficiency curve of a second conversion engine, wherein the first conversion efficiency curve and the first conversion efficiency curve respectively comprise the relation between the file size and the conversion time; determining an intersection of the first conversion efficiency curve and the second conversion efficiency curve; detecting the size of a file to be converted; comparing the file size at the intersection with the file size to be converted; and determining the conversion engine selected by the file to be converted according to the comparison result.

In an embodiment of the present application, on the left side of the intersection, the conversion time of the first conversion engine is less than the conversion time of the second conversion engine, on the right side of the intersection, the conversion time of the first conversion engine is greater than the conversion time of the second conversion engine, and the step of determining the conversion engine selected by the file to be converted according to the comparison result includes: when the size of the file to be converted is smaller than the size of the file at the intersection point, selecting the first conversion engine; and when the size of the file to be converted is larger than the size of the file at the intersection, selecting the second conversion engine.

In an embodiment of the present application, the method further includes: and receiving the selection of a user on the fidelity and/or the security, and determining the conversion engine selected by the file to be converted according to the fidelity and/or the security and the comparison result.

In an embodiment of the present application, the target format of the file to be converted includes a PDF format.

In an embodiment of the present application, the formats of the file to be converted include a Word format, an Excel format, and a PPT format.

In an embodiment of the application, the first conversion engine comprises Libra Office and the second conversion engine comprises MS Office.

In an embodiment of the application, the first transformation engine comprises Libra Office, the second transformation engine comprises MS Office, and the second transformation engine is selected for use when the user selects high fidelity or high security.

In an embodiment of the application, the file size at the intersection is 5 Mb.

The present application further provides a file format conversion apparatus, including: a memory for storing instructions executable by the processor; and a processor for executing the instructions to implement the method as described above.

The present application also proposes a computer storage medium having stored computer program code which, when executed by a processor, implements the method as described above.

Compared with the prior art, the method and the device have the advantages that the conversion efficiency curves of the two conversion engines are obtained, the intersection point of the two conversion engines is determined, and the conversion engine selected by the file to be converted is determined according to the comparison result of the file size at the intersection point and the file size to be converted, so that the advantageous intervals of the conversion efficiency of the conversion engines are utilized, and the file conversion efficiency is improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the principle of the invention. In the drawings:

FIG. 1 is an implementation environment of an embodiment of the present application.

FIG. 2 is a block diagram of an exemplary computer system of the present application.

Fig. 3 is a flowchart of a file conversion method according to an embodiment of the present application.

Fig. 4 is a flowchart of a file conversion method according to an embodiment of the present application.

FIG. 5 is a graph illustrating conversion efficiency curves according to an embodiment of the present application.

Detailed Description

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the description of the embodiments will be briefly introduced below. It is obvious that the drawings in the following description are only examples or embodiments of the application, from which the application can also be applied to other similar scenarios without inventive effort for a person skilled in the art. Unless otherwise apparent from the context, or otherwise indicated, like reference numbers in the figures refer to the same structure or operation.

As used in this application and the appended claims, the terms "a," "an," "the," and/or "the" are not intended to be inclusive in the singular, but rather are intended to be inclusive in the plural unless the context clearly dictates otherwise. In general, the terms "comprises" and "comprising" merely indicate that steps and elements are included which are explicitly identified, that the steps and elements do not form an exclusive list, and that a method or apparatus may include other steps or elements.

The relative arrangement of the components and steps, the numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present application unless specifically stated otherwise. Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description. Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate. In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.

In the description of the present application, it is to be understood that the orientation or positional relationship indicated by the directional terms such as "front, rear, upper, lower, left, right", "lateral, vertical, horizontal" and "top, bottom", etc., are generally based on the orientation or positional relationship shown in the drawings, and are used for convenience of description and simplicity of description only, and in the case of not making a reverse description, these directional terms do not indicate and imply that the device or element being referred to must have a particular orientation or be constructed and operated in a particular orientation, and therefore, should not be considered as limiting the scope of the present application; the terms "inner and outer" refer to the inner and outer relative to the profile of the respective component itself.

Spatially relative terms, such as "above … …," "above … …," "above … …," "above," and the like, may be used herein for ease of description to describe one device or feature's spatial relationship to another device or feature as illustrated in the figures. It will be understood that the spatially relative terms are intended to encompass different orientations of the device in use or operation in addition to the orientation depicted in the figures. For example, if a device in the figures is turned over, devices described as "above" or "on" other devices or configurations would then be oriented "below" or "under" the other devices or configurations. Thus, the exemplary term "above … …" can include both an orientation of "above … …" and "below … …". The device may be otherwise variously oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors used herein interpreted accordingly.

It should be noted that the terms "first", "second", and the like are used to define the components, and are only used for convenience of distinguishing the corresponding components, and the terms have no special meanings unless otherwise stated, and therefore, the scope of protection of the present application is not to be construed as being limited. Further, although the terms used in the present application are selected from publicly known and used terms, some of the terms mentioned in the specification of the present application may be selected by the applicant at his or her discretion, the detailed meanings of which are described in relevant parts of the description herein. Further, it is required that the present application is understood not only by the actual terms used but also by the meaning of each term lying within.

It will be understood that when an element is referred to as being "on," "connected to," "coupled to" or "contacting" another element, it can be directly on, connected or coupled to, or contacting the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly on," "directly connected to," "directly coupled to" or "directly contacting" another element, there are no intervening elements present. Similarly, when a first component is said to be "in electrical contact with" or "electrically coupled to" a second component, there is an electrical path between the first component and the second component that allows current to flow. The electrical path may include capacitors, coupled inductors, and/or other components that allow current to flow even without direct contact between the conductive components.

FIG. 1 is an implementation environment of an embodiment of the present application. The environment in FIG. 1 includes network 101, client 110,

servers

120 and 130. Each client 110 may take any of a variety of forms, such as a desktop computer or a mobile terminal (e.g., a laptop computer, a tablet computer, a smart phone, or a wearable device (e.g., a smart watch or smart glasses)). Each client 110 is configured to connect to network 101 via a suitable wired or, more generally, wireless access technology, e.g., a local wireless router or access point via a Wireless Local Area Network (WLAN); or via a mobile cellular network, such as a 3GPP network (e.g., a 3G, LTE, 4G, or 5G network); or via a local wired network, such as ethernet; or via a cable modem connected to network 101 via a PSTN or cable network. Those skilled in the art will be familiar with various other approaches. It should also be noted that different user terminals do not necessarily have to take the same form as each other, nor do they necessarily have to be connected to the network 101 via the same means.

The environment also includes

servers

120 and 130, server 120 also being connected to network 101. Note that a server as referred to in this application refers to any server device that may include one or more physical server units located in one or more geographical locations. In the case of multiple units (so-called "cloud" computing or cloud storage arrangements), those skilled in the art will be familiar with suitable techniques for distributed storage and distributed computing per se. Moreover, various suitable wired or wireless means for connecting the server units to the network 101 and, in the case of a distributed system, to each other have been described previously and are also known to those skilled in the art.

Servers

120, 130 are configured to host

service software

122 and 132, respectively, by any means physically implemented. The service software 122 and/or 132 is in the form of code stored on the storage means of the server and arranged to run on the processing means of the server. Service software 122 and/or 132 is configured to, when run, provide services to clients and their users via network 101. Service software 122 and/or 132 is also configured to perform server-side functions according to any of the methods disclosed herein. In an embodiment of the application, the service software includes a file conversion engine for converting files from one format to another. The service software 122 may include, for example, a first file conversion engine, such as Libra Office, and the service software 122 may include a second file conversion engine, such as MS Office.

The storage 121 and/or 131 (memory) storing the service software 122 and/or 132 may take the form of one or more memory units implemented on one or more memory units implemented in any one or more server units, employing any suitable one or more memory media, for example, magnetic media such as hard disk drives, electronic media such as EEPROMs, flash memory or Solid State Drives (SSDs), or even optical media. The processing device (not shown) of the server 120 and/or 130 running the service software 122 and/or 132 may include one or more single-core or multi-core processing units implemented in any one or more server units. Such processing units may include, for example, a CPU and/or a work accelerator processor, such as a GPU or the like. Various suitable physical processor means will be familiar per se to those skilled in the art.

Each client 110 has a respective instance of a client application 112 installed. The client applications 112 are in the form of software stored on a storage device of the respective user terminal 110 and arranged to run on a processing device of the respective client 110. Client application 112 is configured to access

service software

122 or 132 on

server

120 or 130 via any suitable wired or wireless network interface of network 101 and corresponding client 110 when running. The client application 112 is also configured to perform client-side functions according to any of the methods described herein.

The storage 111 (memory) storing each respective instance of the client application 112 may take the form of one or more memory units of the respective client 110, taking the form of any suitable one or more memory media, e.g., magnetic media such as a hard disk drive, electronic media such as an EEPROM, flash memory, or Solid State Drive (SSD), or optical media such as a CD ROM or DVD drive. The processing device of the respective client 110 running the respective instance of the client application 112 may include one or more single-core or multi-core processing units. Such processing units may also include a CPU and/or a work accelerator processor, such as a GPU or the like. Various suitable physical processor devices will also be familiar per se to those skilled in the art.

The clients 110 and

servers

120, 130 of FIG. 1 may be of any architecture. FIG. 2 is a block diagram of an exemplary computer system of the present application. The computer system of FIG. 2 is only one example of a suitable environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. System 200 may include internal communication bus 201, Processor (Processor)202, Read Only Memory (ROM)203, Random Access Memory (RAM)204, and communication ports 205. When implemented on a personal computer, system 200 may also include a hard disk 207. Internal communication bus 201 may enable data communication among the components of system 200. Processor 202 may make the determination and issue the prompt. In some embodiments, processor 202 may be comprised of one or more processors. The communication port 205 may enable data communication of the system 200 with the outside. In some embodiments, the system 200 may send and receive information and data from a network through the communication port 205. The system 200 may also include various forms of program storage units and data storage units, such as a hard disk 207, Read Only Memory (ROM)203 and Random Access Memory (RAM)204, capable of storing various data files for computer processing and/or communication, as well as possible program instructions for execution by the processor 202. The processor executes these instructions to implement the main parts of the method. The result processed by the processor is transmitted to the terminal equipment through the communication port and displayed on the user interface.

When a user converts a file format on a client 110 or sends a file to be converted to a

server

120 or 130 for conversion, the same conversion engine (e.g., MS Office) is typically used for all files in the same format (e.g., Word). The inventors of the present application have discovered through analysis of large-scale file conversions that the efficiency of the same conversion engine is not always ideal. For example, efficiency is related to the size of the file to be converted. Different conversion engines behave differently in conversion efficiency at different file sizes. At one file size, one conversion engine is more efficient than the other conversion engines, and at another file size, the other conversion engine is more efficient than the other conversion engines. FIG. 5 is a graph illustrating conversion efficiency curves according to an embodiment of the present application. Referring to fig. 5, MS Office and library Office are taken as examples. When the file size is less than 5Mb, the time taken for converting MS Office into a PDF file is more than 6 seconds, and the time is gradually increased along with the increase of the file size; the time taken for MS Office to convert to PDF files is 1 second or more, and increases rapidly as the file size increases. When the file size is more than 5Mb, the time consumption for converting the MS Office into the PDF file is increased slightly quickly; the time consumption for converting the MS Office into the PDF file is rapidly increased, exceeding the time consumption for converting the MS Office into the PDF file. Thus, the two curves cross at 5 Mb. For other Office, there is also a difference in the trend of conversion efficiency varying with file size. Therefore, different conversion engines are selected according to different file sizes, and the conversion efficiency is improved.

Fig. 3 is a flowchart of a file conversion method according to an embodiment of the present application. Referring now to FIG. 3, a method flow of an embodiment of the present application is described.

In step 301, a first conversion efficiency curve of a first conversion engine and a second conversion efficiency curve of a second conversion engine are obtained, respectively, where the first conversion efficiency curve and the first conversion efficiency curve include a relationship between a file size and a conversion time.

Here, the first conversion engine is, for example, Libra Office, and the second file conversion engine is, for example, MS Office. In other embodiments, the first and second conversion engines may be of other types, such as WPS, and the like. In one embodiment, the target format of the conversion engine is the PDF format. Examples of the first conversion efficiency curve and the second conversion efficiency curve of the second conversion engine are shown in fig. 5, which reflect the relationship between time and file size. In one embodiment, the conversion efficiency curve is obtained by a large batch of file conversion tests of different sizes.

In step 302, an intersection of the first conversion efficiency curve and the second conversion efficiency curve is determined.

Here, the intersection of the first conversion efficiency curve and the second conversion efficiency curve is determined by calculation. On the left side of the intersection, the transition time of the first transition engine (e.g., Libra Office) is less than the transition time of the second transition engine (MS Office), and on the right side of the intersection, the transition time of the first transition engine is greater than the transition time of the second transition engine.

In step 303, the size of the file to be converted is detected.

Here, the size of each file to be converted is detected. The file size information is obtained, for example, by file attributes. Here, the type of the file to be converted may include a text file, a spreadsheet, a presentation file, or other files. The file to be converted can be in Word format, Excel format, PPT format or other formats.

At step 304, the file size at the intersection is compared to the file size to be converted.

For example, the file size to be converted is compared with 5Mb shown in fig. 5, and a comparison result is obtained. In one embodiment, the files to be converted in batches can be divided into two types according to the comparison result. Further, labels can be added to the files to be converted in batches to represent comparison results.

In step 305, the conversion engine selected by the file to be converted is determined according to the comparison result.

For the conversion curves of the two conversion engines shown in fig. 5, when the size of the file to be converted is smaller than the size of the file at the intersection, the first conversion engine, such as Libra Office, is selected; and when the size of the file to be converted is larger than that of the file at the intersection, selecting a second conversion engine, such as MS Office. At the intersection, either of the two conversion engines may be selected.

In some scenarios, users have requirements on the fidelity and security of the conversion. Fidelity refers to the degree to which a file retains original data when converted from one format to another. The safety measures whether the conversion process can be successfully completed without being accidentally ended. To this end, in some embodiments, a file conversion method of another embodiment is presented.

Fig. 4 is a flowchart of a file conversion method according to another embodiment of the present application. Referring to FIG. 4, at step 401, a user selection of fidelity and/or security is received. A process similar to

steps

301 and 304 is performed at

steps

402 and 405. In step 406, the conversion engine selected by the file to be converted is determined according to the fidelity and/or security and according to the comparison result.

For example, where the first conversion engine comprises Libra Office, the second conversion engine comprises MS Office, and when the user selects high fidelity or high security, the second conversion engine, i.e., MS Office, is chosen for use. Because the fidelity and the security of the MS Office conversion are higher than those of the library Office, when the user has the requirement, the MS Office is still selected even if the library Office has advantages in converting small files.

Flow charts are used herein to illustrate operations performed by systems according to embodiments of the present application. It should be understood that the preceding or following operations are not necessarily performed in the exact order in which they are performed. Rather, various steps may be processed in reverse order or simultaneously. Meanwhile, other operations are added to or removed from these processes.

The method described above may be implemented as a computer program, stored in the hard disk 207 or the ROM 203 shown in fig. 2, and recorded in the processor 202 to be executed to implement the file conversion method of the present application. The computer program may be local to client 110 or may be on

server

120 or 130.

Having thus described the basic concept, it will be apparent to those skilled in the art that the foregoing disclosure is by way of example only, and is not intended to limit the present application. Various modifications, improvements and adaptations to the present application may occur to those skilled in the art, although not explicitly described herein. Such modifications, improvements and adaptations are proposed in the present application and thus fall within the spirit and scope of the exemplary embodiments of the present application.

Also, this application uses specific language to describe embodiments of the application. Reference throughout this specification to "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic described in connection with at least one embodiment of the present application is included in at least one embodiment of the present application. Therefore, it is emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, some features, structures, or characteristics of one or more embodiments of the present application may be combined as appropriate.

Aspects of the present application may be embodied entirely in hardware, entirely in software (including firmware, resident software, micro-code, etc.) or in a combination of hardware and software. The above hardware or software may be referred to as "data block," module, "" engine, "" unit, "" component, "or" system. The processor may be one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), digital signal processing devices (DAPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or a combination thereof. Furthermore, aspects of the present application may be represented as a computer product, including computer readable program code, embodied in one or more computer readable media. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips … …), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD) … …), smart cards, and flash memory devices (e.g., card, stick, key drive … …).

The computer readable medium may comprise a propagated data signal with the computer program code embodied therein, for example, on a baseband or as part of a carrier wave. The propagated signal may take any of a variety of forms, including electromagnetic, optical, and the like, or any suitable combination. The computer readable medium can be any computer readable medium that can communicate, propagate, or transport the program for use by or in connection with an instruction execution system, apparatus, or device. Program code on a computer readable medium may be propagated over any suitable medium, including radio, electrical cable, fiber optic cable, radio frequency signals, or the like, or any combination of the preceding.

Similarly, it should be noted that in the preceding description of embodiments of the application, various features are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of one or more of the embodiments. This method of disclosure, however, is not intended to require more features than are expressly recited in the claims. Indeed, the embodiments may be characterized as having less than all of the features of a single embodiment disclosed above.

Numerals describing the number of components, attributes, etc. are used in some embodiments, it being understood that such numerals used in the description of the embodiments are modified in some instances by the use of the modifier "about", "approximately" or "substantially". Unless otherwise indicated, "about", "approximately" or "substantially" indicates that the number allows a variation of ± 20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximations that may vary depending upon the desired properties of the individual embodiments. In some embodiments, the numerical parameter should take into account the specified significant digits and employ a general digit preserving approach. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the range are approximations, in the specific examples, such numerical values are set forth as precisely as possible within the scope of the application.

Although the present application has been described with reference to the present specific embodiments, it will be recognized by those skilled in the art that the foregoing embodiments are merely illustrative of the present application and that various changes and substitutions of equivalents may be made without departing from the spirit of the application, and therefore, it is intended that all changes and modifications to the above-described embodiments that come within the spirit of the application fall within the scope of the claims of the application.

Claims

1. A file format conversion method, the method comprising the steps of:

respectively acquiring a first conversion efficiency curve of a first conversion engine and a second conversion efficiency curve of a second conversion engine, wherein the first conversion efficiency curve and the first conversion efficiency curve respectively comprise the relation between the file size and the conversion time;

determining an intersection of the first conversion efficiency curve and the second conversion efficiency curve;

detecting the size of a file to be converted;

comparing the file size at the intersection with the file size to be converted; and

and determining the conversion engine selected by the file to be converted according to the comparison result.

2. The method of claim 1, wherein the transition time of the first transition engine is less than the transition time of the second transition engine to the left of the intersection, the transition time of the first transition engine is greater than the transition time of the second transition engine to the right of the intersection, and determining the transition engine selected for the file to be transitioned based on the comparison comprises:

when the size of the file to be converted is smaller than the size of the file at the intersection point, selecting the first conversion engine;

and when the size of the file to be converted is larger than the size of the file at the intersection, selecting the second conversion engine.

3. The method of claim 1, further comprising: and receiving the selection of a user on the fidelity and/or the security, and determining the conversion engine selected by the file to be converted according to the fidelity and/or the security and the comparison result.

4. The method of claim 1, wherein the target format of the file to be converted comprises a PDF format.

5. The method as recited in claim 1, wherein the format of the file to be converted comprises a WORD format, an Excel format, and a PPT format.

6. The method of claim 4, wherein the first conversion engine comprises Libra Office and the second conversion engine comprises MS Office.

7. The method of claim 3, wherein the first conversion engine comprises Libra Office, the second conversion engine comprises MS Office, and the second conversion engine is chosen for use when the user selects high fidelity or high security.

8. The method of claim 1, wherein a file size at the intersection is 5 Mb.

9. A file format conversion apparatus comprising:

a memory for storing instructions executable by the processor; and

a processor for executing the instructions to implement the method of any one of claims 1-8.

10. A computer storage medium having computer program code stored thereon, which when executed by a processor implements the method of any of claims 1-8.