DE202015009309U1 - Systems for processing a file in a non-native application using an application engine - Google Patents

Abstract

A system for processing documents in a native format, with a processor, configured for: receiving, while executing a first application, a request from a user to open a file created with a second application in a first format ; determining the first format of the file; selecting an engine of the plurality of engines associated with the first application, wherein the selected engine is configured to process the first format; opening the file using the selected engine in the first application without converting the format of the file into a second format associated with the first application; rendering, using the engine selected in the first application, the content of the file for display on a user device to the user; processing, using the engine selected in the first application, processing of the file in the first format; and saving, in a database, the edited file using the first application in the first format.

Description

Field of the invention

In general, this disclosure relates to accessing a file using an application that is different from the application with which the file was created.

background

An application generally has its own native file format that specifies the encoding of the features that the application supports. Applications typically load only those features that are supported by the native format of the application. Any features that are not supported by the native format of the application create problems when loaded or are loaded incorrectly. Because of this, using a software application to edit and save a file created with another software application often causes data loss if the file and file format have features that the application does not support. One way to compensate for this is to have the application convert the file to another format - its native format. When the application saves the file, only the loaded features are saved, so the unsupported features are not saved. This data loss can cause problems when a file is being edited by multiple users or by a user with multiple applications.

Summary

Accordingly, this document describes systems and methods that provide access to the file and use a non-native multi-engine application. In certain respects, the systems and methods described in this document relate to the processing of a document in a native format using a non-native application. A processor executing a first application receives a request from a user to open a file using a second application in a first format. The processor can determine the first format of the file. The processor may select an engine of multiple engines associated with the first application, wherein the selected engine is configured to process the first format. The processor can open the file using the selected engine in the first application without converting the format of the file to a second format associated with the first application. The processor may cause the engine selected in the first application to render the contents of the file for display to the user on a user device. The processor may cause the engine selected in the first application to process a processing of the file in the first format. Then the processor can save the edited file in a database using the first application in the first format. In some implementations, the processor may display to the user a user interface that includes tools for editing features of the selected engine.

In some implementations, the processor may determine that the selected engine is configured to process a feature of the file. The processor may then cause the engine selected in the first application to render the feature for display on a user interface for the user. The processor may then cause the selected engine in the first application to process processing of the rendered feature in the first format. The processor can then store the feature edited in the file in a database using the first application in the first format.

In some implementations, the processor may determine that the selected engine is not configured to process a first feature of the file. The processor may then cause the engine selected in the first application to render the first feature for display to the user on a user device. The processor can then prevent the user from changing the first feature. The processor may determine that the selected engine is configured to process a second feature of the file. The processor may then cause the engine selected in the first application to render the second feature for display to the user on a user device. The processor may then cause the selected engine in the first application to process processing of the second feature in the first format. Thereafter, the processor may store the second feature processed in the file using the first application in the first format in the database.

In some implementations, the processor may cause the selected engine to place data corresponding to the first feature in a node of a document object model and associate the node with the property for which the selected engine is not configured to process the first feature. Subsequently, the processor can store in the database the data stored in the file using the first application in the first format.

In some implementations, the processor may determine that the selected engine is not configured to render a feature of the file. The processor may then place the data corresponding to the first feature in a node of a document object model and associate the node with the property for which the selected engine is not configured to render the first feature. Subsequently, the processor can store in the database the data stored in the file using the first application in the first format.

In some implementations, the file may be stored on a server remote from the user. In some implementations, the engine selection engine may determine the first format in a database, determine if an engine is associated with the first format, and select the appropriate engine. In some implementations, to determine the first format of the file, the processor may read a portion of the file, extract a file type from the portion read, and determine the first format of the file based on the extracted file type.

In some implementations, the processor may determine that the file format has multiple engines associated with it. The processor may then display multiple names to the user, each name corresponding to one of the multiple engines. The processor may then receive from the user a name selected from the multiple names. The processor can then select the engine associated with the selected name. In some implementations, the processor may store the file in a third format.

Brief description of the drawings

The foregoing and other features of the present disclosure, including its nature and various advantages, will become more apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings:

1 FIG. 10 is a block diagram of a user device shown by way of an example implementation; FIG.

2 FIG. 12 illustrates a user interface of an application executing an engine configured to process a word processing document, shown by way of an example implementation; FIG.

3 10 depicts a user interface of an application executing an engine configured to process a spreadsheet document, shown by way of an example implementation;

4 Figure 10 is a block diagram of a user device communicating over a network with a server, shown by way of an example implementation;

5 Figure 10 is a block diagram of a database containing engine-to-file mappings shown by way of an example implementation;

6 FIG. 10 is a block diagram of a document object model shown by way of an example implementation; FIG.

7 FIG. 10 is a flow chart of a method by which an application launches an engine configured to process the format of a requested file, shown by way of an example implementation;

8A - 8B 12 show a flow chart of a method by which an engine reads data from a file, stores data in nodes of a document object model, and processes edits made to the document, shown by way of an example implementation;

9 FIG. 10 is a flow chart of a method by which an engine generates a file in a user-specified format, shown by way of an example implementation; FIG.

10 Figure 10 is a block diagram of a cloud computing service, shown by way of an example implementation; and

11 FIG. 10 is a block diagram of a computing device for any of the processes described in this document, shown by way of example implementation.

Detailed description

For a general understanding of the disclosure, some exemplary implementations are described below, including a system for manipulating files in a native format. In particular, a system is described in which files can be edited with a non-native application in a native format, or in an application other than the application with which the file was created. However, it will be understood by one of skill in the art that the systems and methods described herein may be adapted and modified as necessary for the particular application and as described in this document described systems and methods can be used in other suitable applications, and that such other additions and modifications do not deviate from the scope described here. In general, the computerized systems described in this document may consist of one or more components including one or more processing devices, such as a computer, microprocessor, logic device, or other device or processor, using Hardware, firmware, and software are configured to perform one or more of the computer-aided procedures described in this document.

1 shows a user device 100 , which can be used to edit a document in a native format. The user device 100 can be a processor 105 , a display 110 , a user input device 115 and one or more databases 120 with one or more files 125 such as files 125a - 125n , include. The user device 100 can be one or more applications 130 included, for example, applications 130a - 130n , A processor may include one or more computers, microprocessors, logic devices, servers, or other devices configured with hardware, firmware, and software to perform one or more of the computer-assisted techniques described in this document. Processors and processing devices may also include one or more storage devices for storing inputs, outputs, and data that is currently being processed. Each user device 100 may include a device such as a personal computer, a laptop computer, a tablet, a smartphone, an organizer or other computer, or another communication device of a suitable type.

An example file 125a may have a file format that determines how the file information is encoded into bits in memory, as well as how that information is decoded from memory and presented to a user. Generally speaking, a file has a file format based on the application with which the file was created, such as the native file format of the application. File formats can be simple or complex. A simple file format is American Standard Code for Information Interchange (ASCII) that encodes plain text and a few simple characters. An example of a complex file is the format for encoding information in a word processing document. A word processing format may include, for example, the encoding method for fonts, font sizes, fonts, font colors, tabs, paragraphs, bulleted lists, numbered lists, tables, text wrapping, text alignment, text highlighting, line spacing, page breaks, page size, margins, columns, headers, footers, footnotes, endnotes, Specify cross-references, tables of contents, indexes, and embedded content such as images and video. A spreadsheet format is also complex and can specify the encoding method for cell contents, formula operations, fonts, font sizes, fonts, font colors, cell borders, cell colors, and charts. A presentation format is also complex and can specify methods for fonts, font sizes, fonts, font colors, text boxes, shapes, slide size, position and placement of elements on a slide, slide order, slide transitions, animations, and embedded content such as images, videos, and spreadsheets. File formats may include other formats. For example, word processing, spreadsheet, and presentation formats may all include the ASCII format for encoding text, but may use additional format specific coding techniques to encode features other than text. A file containing a document may be encoded in a format appropriate to the document. A file may be a word processing document, a spreadsheet document, a presentation document, a drawing document, a database document, a HyperText Markup Language (HTML) document, Extensible Markup Language (XML) document, an image document, a text document, or any other user data document contain. When opening and editing a file, an application uses the format of the file to decode the bits stored in memory and present the decoded information to a user.

For example, the application 130 be a browser extension, namely an application that is designed to complement the functionality of a browser application. The application 130 contains several engines 135 , each configured to handle one or more file formats. A user of the user device 100 can input via the input device of the user 115 for the application 130 to open a file 125a provide. For example, the input may be for the user to drag and drop a file icon into a browser window. In In another example, the user may open a file attached to an e-mail that is accessed via a browser to communicate with a web-based e-mail service. In another example, the user may open a file attached to an e-mail that is accessed via an e-mail application on the desktop computer. In another example, the user may use a browser to navigate to a web-based document collaboration hosting service and open a file hosted by the service. In another example, the user may work with the user interface of an application to open a file using the application. These examples are exemplary and a user may use a different input method to open a file without departing from the scope of the invention. The application 130 regardless of the form of input when receiving the input the format of the file 125a using one of several methods. For example, the application 130 the file format depends on the filename extension of the file 125a determine. In another example, the application 130 the header information of the file 125a use to determine the format. In this example, the application 130 a part of the header information of the file 125a read. The application 130 can then read the read part of the header of the file 125a interpret to the format of the file 125a to determine. The application 130 can perform the determination based on a string contained in the header indicating the file type. An example of a file type is MIME (Multipurpose Internet Mail Extensions). Based on the determination of the file format, the application can 130 an engine 135a which is configured to do this for the file 125a edited certain format. An engine configured to handle a format is configured to read data from memory and write data to memory, the data being encoded in accordance with the format. An engine that is configured to handle a format does not need to fully support the format. The engine can be configured to read only a subset of a file encoded in accordance with the format. In addition, an engine configured to process a format may be configured to write data using only a subset of the encoding methods of the format. The application 130 can then select the selected engine 135a start the file 125a opens, displays and allows editing.

If an engine 135a one in a file 125a contained document opens, decodes the engine 135a the data of the file 125a in accordance with the native format of the file and renders the document contained in the decoded data to display to a user. The rendering of the document may be the conversion of data from the file 125a in a two-dimensional image for display on a user device 100 via a display 110 include. The user can view the rendered document and make user input to the document via the user input device 115 to change. The modification of the document may include one or more text inputs or deletions, changes to the text style, the insertion of images and other media, or other editing operations of the document. For example, the user can view the rendered document in the file 125a save, and the engine 135a can the document in the file 125a in accordance with the native format of the file 125a to save. Saving in native format prevents the engine 135a a data loss due to the format conversion. The engine 135a The document can be automatically added to the file at predefined intervals without any input from the user 125a to save. Such automatic saving reduces data loss due to user device malfunction 100 or the application 130 , When the user device 100 or the application 130 behave incorrectly, the application can 130 the user via the display 110 Display a dialog for recovery in case of error. Such an error recovery dialog may include an overview of the malfunction, a view of the last edited document at the page position immediately before the malfunction, and status information including the most recently opened menus and dialogues, so that the user can specify a course of action to resolve conflicts that result from the malfunction. By using the appropriate engine 135a for editing a file 125a represents the application 130 Provide a user with editing capability for a document without loss of data due to conversion between formats.

The application 130 can provide a user with file management features. If an engine 135a Started and edited a document, the engine can 135a receive a user input to the document in another file in the database 120 save. For example, the engine 135a the file in the same format as the original file 125a save, but at a different file location, such as in the file 125b , In another example, the engine 135a received a user input to the file 125a rename. In this example, the engine changes 135a the file name of the file 125a , In this example, the contents of the file 125a remain unchanged, or it can be updated to updates in the file 125a to reflect the associated document. In some examples, the application receives 130 a user input to the file 125a rename and change the filename of the file 125 a. In another example, the engine 135a received a user input to the modified file 125a to add an e-mail as an attachment. In this example, the e-mail containing the changed file 125a Attached as attachment is a reply to another user who originally created the document. In this way, a receiving user can view the application 130 to open a document received from a sending user in an e-mail, modify the received document, and send the changed document back to the sending user, even if the receiving user does not have the application that the sending user uses Originally created the document. Alternatively, the e-mail containing the changed file 125a added as an attachment, also not be a reply email, but may be a new email to another user. In this example, the modified file 125a locally on the user device 100 and also on a server device 420 be stored in the cache. This file management function can be combined with other functions described in this document. The application allows you to rename files and save new files 130 a user, files on a user device 100 manage.

The application 130 can provide a user with file format conversion capabilities. If an engine 135a Started and edited a document, the engine can 135a receive a user input to the document in a different format in the database 120 save. For example, the engine 135a the file in a different format than the original file 125a save and in a different file location, such as the file 125b , This file format conversion feature may be combined with other functions described in this document. By providing functions to save in a different format, the application allows 130 a user to convert a file from one format to another.

In some examples, multiple engines may be linked in tandem to convert a file from one format to another. In these examples, the application causes 130 two or more of the engines 135 To convert files one by one to finally reach the desired format. For example, the engine 135a the file from the format 125a in the format of 125b convert, and then another engine, such as 135b , start the file 125b open and the data it contains in another file 125c save in a different format. This chaining can be repeated as often as desired to finally obtain a file in the desired format.

The application 130 can provide a user with functions for creating files. For example, the application 130 receive a user input to create a file and, upon receiving the input, display to the user one or more file formats. The displayed file formats can be formats that correspond to the engines 135 the application 130 assigned. The application 130 For example, a user selection may receive one of the displayed file formats and an engine associated with the selected file format 135a start. After the appropriate engine 135a started, the user can change the document and save the document in a file 125a to save. A user may choose to create a file in a particular format when generating a document to send to other users. In this situation, the user can select a format that is compatible with applications that the recipients may use to open and edit the file. This function for creating files can be combined with other features described in this document. In this way, the application offers the user the ability to create a file in a specific format.

The application 130 can receive a request, a file 125a open, which is marked as read-only. Such labeling as read-only may dictate that the file 125a can be opened and viewed, but that the file 125a can not be changed. For example, the application 130 the appropriate engine 135a select as described in this document and the application 130 can the selected engine 135a start in read-only mode. In read-only mode, the engine 135a the file 125a open and display their contents for display 110 render, but changes to the file 125a prevent. The engine 135a may allow a user to edit the rendered document as described here, but may save the updated document in a different file 125b to save. The application 130 can create, open, natively edit and save documents to other file locations and other formats. This function for read-only editing can be combined with other functions described in this document. By providing multiple engines 135 , where each engine is configured to handle one or more file formats, the application can 130 natively edit multiple file formats as described in this document.

2 shows an example of a user interface 200 the application 130 , This example contains the file 125a a word processing document 205 and the engine 135a is configured to match the format of the file 125a processed. The user interface 200 can in a browser 210 to be provided. The browser 210 can one or more tabs 215 have the selection of a document to be displayed 205 from several open documents or web pages. The surface 200 can symbols 220 which indicate the currently used engine. The text 225 of the document 205 will be in the middle of the user interface 200 displayed. In some examples, the text is located 225 not in the middle, but in another area of the user interface 200 , For example, it may be that some or all of the text 225 Attributes not assigned by the engine 135a get supported. In this example, the unsupported features may not be displayed correctly or may not be displayed at all. The engine 135a however, it retains the unsupported features when viewing the file 125a stores the features to other applications or engines that support the features. In this example, the engine allows 135a No editing of unsupported features to ensure that such features are preserved.

The user interface 200 contains tools 230 for editing the characteristics of the document 205 , For example, the font in which the text 225 is displayed with the tool 230a to be selected. The font size can be with tool 230b to be selected. The font can be used with the tools 230c -E are selected. The font color can be with tool 230f to be selected. The text alignment can be done with the tools 230g -I are selected. Numbered lists can be used with the list tool 230j be created and edited. Stichpunktlisten can with the list tool 230k be created and edited. The document can be used with the printing tool 235 be printed out. The last changes made by the user to the document can be made using the undo tool 240 be undone. These and other tools can also be found in menus 245 to be provided. The name of the document can be found in the document title 250 are displayed. The editing tools 230 for features by the application 130 be displayed when the engine 135a can only be those tools that match the file format characteristics that the engine uses 135a supported. Thus, the application can 130 editing less than all in the file 125a support contained features. Another engine 135b can be configured to handle a different file format for a similar document type. The application 130 can use a different set of UI tools 210 show when the engine 135b is used as the application 130 indicates when the engine 135a is used. The user interface 200 is shown for exemplary purposes, but other surface configurations may provide comparable functionality. By providing the editing tools 230 for features for the user that match the characteristics of the file format that the engine processes for 135a configured, allows the application 130 just editing features that the engine used supports.

3 shows an example of a user interface 300 the application 130 , This example contains the file 125a a spreadsheet document 305 and the engine 135a is configured to match the format of the file 125a processed. The user interface 300 can in a browser 310 to be provided. The browser 310 can have one or more tabs 315 have the selection of a spread sheet to display 305 from several open documents or web pages. The user interface 300 can symbols 320 include to display the currently used engine. The cells 325 the spreadsheet 305 be in the middle of the user interface 300 displayed. Data can be in certain cells 355 be included. The formula bar 360 can display a formula contained in a cell. For example, the selected cell contains 365 the formula "= B9-C9". The data in the spreadsheet 305 can with a diagram 370 are displayed. The diagram 370 can references in cells 355 contained data included. The diagram 370 can be automatically updated using the references when the data is in the cells 355 to be updated. For example, it may be that some or all of the diagram 370 Attributes not assigned by the engine 135a get supported. In this example, the unsupported features may not be displayed correctly or may not be displayed at all. The engine 135a however, it retains the unsupported features when viewing the file 125a stores the features to other applications or engines that support the features. In this example, the engine allows 135a No editing of unsupported features to ensure that such features are preserved.

The user interface 300 contains tools 330 for editing the features of the spreadsheet 305 , For example, the font in which the cell text 355a is displayed with the tool 330a to be selected. The font size can be with tool 330b to be selected. The font can be used with the tools 330c -E are selected. The font color can be with tool 330f to be selected. The cell background color can with tool 330g to be selected. The text alignment can be done with the tool 330h to be selected. The last changes made by the user to the spreadsheet can be made using the undo tool 340 be undone. These and other tools can also be in menus 345 to be provided. The editing tools 330 for features by the application 130 be displayed when the engine 135a can only be those tools that match the file format characteristics that the engine uses 135a supported. Thus, the application can 130 editing less than all in the file 125a support features. Another engine 135b can be configured to handle a different file format for a similar document type. The application 130 can use a different set of UI tools 310 show when the engine 135b is used as the application 130 indicates when the engine 135a is used. The user interface 300 is shown for exemplary purposes, but other surface configurations may provide comparable functionality. By providing the editing tools 330 for features for the user that match the characteristics of the file format that the engine processes for 135a configured, allows the application 130 just editing features that the engine used supports.

The application 130 can support editing of document types other than word processing documents, as in 3 shown, or spreadsheets, as in 4 shown. The application 130 May support the editing of presentation documents, drawing documents, database documents, HTML documents, XML documents, image documents, text documents or other documents containing user data. The application 130 can Engines 135 configured to work on some or all of the file formats associated with these document types.

In an offline arrangement, an engine 135a a document 125a without using devices other than the user device 100 to communicate. In an online arrangement, an engine 135a a document 125a edit while the user device 100 communicates with other devices or a server. The application 130 and the engines 135 can work both offline and online. For example, the application can do this 130 work offline when no network connection is available, and switch to the online arrangement when the network connection is available again. The ability to switch between online and offline placement provides improved access to documents for users, for example, from mobile devices.

4 shows a system 400 that is a user device 401 can enable over a network 415 with a server 420 to communicate. The user device 401 can be a network interface 410 that is configured to act as an intermediary between the network 415 and the user device 401 acts. The server 420 can be a network interface 430 that is configured to act as an intermediary between the network 415 and the server 420 acts. Several 401 Similar user devices can be connected to the server 420 communicate the same way as a user device 401 with the server 420 communicated. For the sake of clarity is in the 4 only one user device 401 shown. user devices 100 and 401 can perform similar functions and have similar features. For example, the features 406 . 41 . 416 . 421 . 426a -n, 431 and 436a -N of a user device 401 perform similar functions as the features 105 . 110 . 115 . 120 . 125a -n, 130 and 135a -N of a user device 100 ,

In one implementation, the server can 420 serve as a web-based storage system by acting as a host to files, allowing users to store, retrieve, and modify data. The user can do that on the server 420 saved file 440 to edit. The application 431 can the file 440 read and access it by contacting the server 420 over the network 415 and the network interfaces 410 and 430 communicates with the network. The application 431 can be on the server 420 saved file 440 in a database 435 to save. To improve performance, such as a slow or intermittent network connection 415 , the application can 431 optionally a file 125a on the user device 401 as a local copy of the file 440 maintained. So is the network connection 415 interrupted, causing the user device 401 goes into an offline status, the application can 431 continue to receive input from the user and the file 125a update accordingly, and the application 431 can do such updates to the server 420 transmit when the network connection 415 is restored and the user device 401 returns to an online status. The system 400 can allow a user the application 431 to use one on the server 420 located file 440 to edit.

In another implementations, the server may 420 act as an e-mail server by transmitting e-mails and saving files added to the e-mails being sent. In another implementation, the server may act as both a web-based storage system and an e-mail server, as described in this document.

In one arrangement, the system can 400 enable one on a user device 401 saved file 426a over a network 415 with another on a server 420 saved file 440 to synchronize. The user device 401 can be a sync client 405 contain. The file 440 on the server 420 can be edited by another user or by the same user on a different user device. In this situation, the external file 440 be changed, such as by another user. The server can make changes to the changed file 440 correspond to the user device 401 transfer. The sync client can save the file 426a update based on the transferred changes. That way the file can be 426a on the user device 401 with the external file 440 on the server 420 be synchronized. In this arrangement, the application 431 the file 426a read and access it by using the database 421 communicated. The application 431 can make changes to the file 426a in the database 421 to save. The sync client 405 can detect changes to the file 426a on the user device 401 have been made and the changes made over the network 415 to the server 420 transfer. The sync client 405 Can be run while the application 431 the file 426a processed. This operation can transfer local changes to the file 426a to the server 420 include, receiving changes from the server 420 and updating a local file 426a , or both. This arrangement may be combined with other arrangements and implementations described in this document. By synchronizing the file 426a on the user device 401 with the file 440 on the server 420 The user can edit a document on multiple devices and collaborate with other users.

In some examples, the application may 431 on the server 420 are located and over the network 415 communicate with the user device. The application 431 can the file 426 open on the local device 401 is saved, or a file 440 on the server 420 is stored. The application 431 can the processor 425 the server use the contents of the file 426a or the file 440 for display on the user device 401 over the display 411 render and render over the network 415 to the user device 401 transfer. By using the network 415 for communication between the server 420 and the user device 401 The system allows a user to edit a document, regardless of whether the application 431 on the user device 401 is installed or not.

It can be an access control to the file 426a , the file 440 or both. The server 420 or an application running on it may have an access control for one on the server 420 saved file 440 Offer. An application running on the user device 401 is running, such as the sync client 405 , can be an access control for a file 426a deploy on the user device 401 is stored. Alternatively, the server 420 or an application running on it has an access control for one on the local device 401 saved file 426a offer by going over the network 415 communicate. The access control for a file may include a request that a user must authenticate to open, edit, or save the file. The access control for the file 426a or the file 440 Can continue to communicate over the network 415 with a server or another server 420 , such as an authentication server. A user can authenticate by entering a user name and password (or other identifying information) through a user interface so that the same user device can be used by different users at different times. Users can get different levels of access to a file. For example, a user may have read-only access to a file so that it can open and view the file, but not edit or save it. Alternatively, a user may have read and write access to a file so that the user is able to open, edit, and save the file. A user can be designated as the owner of a file and give other users access to the file. Users may be granted access on an individual basis, or access may be granted to user groups. An access control list associated with the file may determine the access rights of the users attempting to access the file. By providing file access control, the system provides increased security.

5 shows a database 500 , the entries 505 contains the names of file formats 510 Names of Engines 515 assign that are configured to edit the formats. Database 500 can be on the user device 100 or on the server 420 are located. An entry 505 can also have one or more file types 515 contain the format name 510 assigned. An example of a file type is MIME. An entry 505 can be a format name 510 and several associated engine names 520 contain. Alternatively, an entry 505 several format names 510 and an associated engine name 520 contain. Alternatively, an entry 505 several format names 510 and several associated engine names 520 contain. For example, the database 500 queried for the format name. In this example, the results of a query can all the entries containing the queried format name. In another example, the database 500 be queried for the file type. In this example, the results of a query may include all entries that contain the queried file type. In a third example, the database 500 queried for the engine name. In this example, the results of a query may include all entries that contain the queried engine name. In this way, the entries provide 505 Associations of file formats for editing engines. By mapping file formats to editing engines, the database allows 500 the selection of an engine 135a which is configured to match the format of a file 125a processed.

6 schematically shows a document object model (DOM) 600 that of an engine 135a is used when viewing or editing a document file. A document file may refer to a file containing a word processing document, a spreadsheet document, a presentation document, a drawing document, a database document, an HTML document, an XML document, an image document, a text document, or any other user data document. In the DOM are objects of the document 605 arranged as a node in a hierarchy. An object can be a feature of the file. A node may have one or more underlying nodes in the hierarchy, and a node may have one or more parent nodes in the hierarchy. For example, there is node 615 over knots 620 and under nodes 610 , Similar nodes can be at the same level in the hierarchy. For example, the nodes can become 630 . 640 and 650 at the same hierarchy level. In one example, the MVC implementation (Model View Controller) is used to construct the DOM 600 to create and edit a user and the contents of the DOM 600 display. In this example, the model part of the MVC searches a file and places sections of the file, the objects of the document 605 correspond, in nodes of the DOM 600 , For example, in the node 650 of the DOM be placed a paragraph, and in the node 655 a sentence can be placed from the paragraph. A word of the sentence may be in knots 660 can be placed, another word can be in nodes 665 to be placed. Another sentence of the paragraph may be in node 670 be placed while his words in the knot 675 and 680 to be placed. For clarity of illustration, only two sentence nodes and four word nodes are top and bottom 6 but a paragraph may have any number of sentences and corresponding sentence nodes, and a sentence may have any number of words and corresponding word nodes. In another example, a table may be in the node 650 of the DOM 600 be placed, with the row elements of the table in the nodes 655 and 670 are placed. The contents of each cell in the table rows may be in the node 660 . 665 . 675 respectively. 680 to be placed. Tables may have any number of rows and row nodes, and rows may have any number of cell nodes, but two row nodes and four cell nodes are described here for clarity of illustration. In another example, tables can use columns as the primary index in the DOM 660 to be placed. In this example, the nodes match 655 and 670 the columns of the table, and the nodes 660 . 665 . 675 and 680 correspond to the content of each cell in the table columns. For example, node 610 Contain header information of the document. node 615 can contain a sentence from the header, and node 620 can contain a word from the header record. For clarity, has nodes 610 only one child node 615 which itself is a subordinate node 620 Has. In addition, the DOM has 600 as shown, four hierarchical levels. However, each node in a DOM can have any number of child nodes, and a DOM can have any number of hierarchy levels.

After the model share the DOM 600 and has distributed content to the nodes, the presentation portion of an MVC may then be the nodes of the DOM 600 go through individually and some or all of the nodes in the DOM 600 render contained objects. The presentation portion may be a rendering engine and a component of an engine 135a , If the presentation share all nodes of the DOM 600 it renders the contents of a node if it is configured accordingly. The view part may use hard-coded logic to decode or analyze the contents of each node as it encounters the node as it passes through. If the hard-coded logic is configured to decode or analyze the contents of the node, the view portion presents the contents of the node to a user for display. If the hard-coded logic is not configured to decode or parse the contents of the node , the view part will not play the contents of the node and move to another node. For example, the presentation share may be the DOM 600 go through while at the same time the model share the DOM 600 created or updated.

The control portion of an MVC may interact with the presentation portion and the model portion of the MVC in order to process that from the DOM 600 presented document 605 to simplify. The control portion may be a component of the engine 135a be. When a user makes an editing input, the controller receives the Input, determines the node of the DOM 600 for which the input is intended and updates the corresponding node. The controller then instructs the view portion of the MVC to render the updated node. The update of the DOM 600 must be checked for correctness. This validation may occur before or after the view part renders the updated node. For example, the controller may be optimistic about updating the DOM 600 carry out. In this example, the controller portion sends the update directly to the presentation portion for immediate rendering and updates and asynchronously checks the DOM 600 , If the validation is successful, no further action will be taken in relation to the update. If the check results in a negative result, the update of the DOM 600 Undo the presentation part and render the DOM 600 as it was before the upgrade. Such an optimistic update allows faster viewing of user edits.

For example, the engine 135a may not be configured to use all nodes of the DOM 600 can edit. In this example, a user may provide input to a feature of the document 605 to work on that one node of the DOM 600 corresponds to the engine for its processing 135a is configured. This can occur even if the presentation portion of the MVC is configured to render the node. The controller portion of the MVC may receive the user input. After determining that the control portion was not configured to handle the node, the node can not be changed. The engine 135a Optionally, inform the user that the desired feature can not be edited. In some examples, the presentation portion may render the contents of the node incorrectly if the presentation portion is configured to render the node, but the engine 135a not configured to handle the node. However, because the control portion does not handle such nodes, the original content of these nodes is retained. In this way, it is ensured that a subsequent application or engine that fully supports the feature contained in this node can render and manipulate the original unmodified contents of the nodes without data loss.

If the document 605 stored, the engine can 135a the DOM hierarchy 600 use to save in accordance with the format of document 605 perform. For example, the nodes of the DOM 600 Contain data that is already encoded in the format of the file that originally contained the document 605 contained. In this example, those in the nodes of the DOM 600 data that has been saved before saving or converted into another format. In another example, the engine 135a supported features and their corresponding nodes of the DOM 600 in accordance with the format of the document 605 encode. This example contains nodes of the DOM 600 that contain features for rendering or editing the engine 135a is not configured, data that is encoded in accordance with the original format of the file, and they are not further encoded before saving. If node, for rendering or editing the engine 135a not configured to be reformatted, all data in the node went lost because of the engine 135a is not configured to properly decode the format of the nodes. Moreover, if these nodes were simply dropped on storage, the data of the nodes would also be lost. By preserving the format of the nodes with features for rendering or editing the engine 135a is not configured, unsupported features of the original file are preserved while other features are being edited.

7 shows a flowchart 700 a method for selecting an engine to start when a requested file is opened. A user can enter a request on a client device to open a file that has a particular file type. The request is received by an application, such as application 130 What, for example, in step 705 takes place. The request may contain a file ID associated with the file to be opened. In step 710 determines a processor that the application 130 executes the location of the requested file depending on the information contained in the request. The requested file may be on the user device 100 are located on a server 420 or at another location. The location can be determined by examining a file index in a database or in memory. In step 715 the application determines the format of the requested file. The application may determine the format based on a file name extension, header information, or other information associated with the file. If the file name extension is used to determine the format, the application may use the file name extension of the requested file, the found file, or both. If header information is used to determine the format, the application can read part of the header of the found file and extract a string indicating the file type from the header. The string for the file type can be a MIME string. In some examples Both the header information and the file name extension information can be used to determine the format of a file. If both clauses give similar clues to the file format, there is an increased likelihood that the clauses will be correct. However, if the clauses give different clues to the format, there is a conflict. Such a conflict can occur if a file name extension has been changed from one user to another file name extension.

In decision block 720 asks the application 130 a database 500 to determine if an engine is configured to open and edit the file associated with the application. The application 130 determines whether entries in the database 500 contain the format of the found file. If no entries in the database contain the format of the found file, the procedure goes to step 725 and displays a message to the user that the requested file can not be opened. In addition, if there is a conflict between multiple determinations of the format, as described above, the method can be used with step 725 continue, and as part of step 725 inform the user about the conflict in determining the format. Alternatively, in the case of such a conflict, the process may step directly 740 continue and prompt the user to select an engine directly. The prompt can be a listing of some or all engines 135 contain. After step 725 becomes the procedure 700 completed. If one or more entries in the database 500 If the format of the found file is included, the procedure continues with decision block 730 ,

In decision block 730 determines the application 130 whether the format of the found file is assigned to multiple engines. Database 500 contains one or more entries 505 that contain engine-to-file mappings. An entry 505 can be a format name 510 and several associated engine names 520 contain. Alternatively, an entry 505 several format names 510 and an associated engine name 520 contain. Alternatively, an entry 505 several format names 510 and several associated engine names 520 contain. Represents the application 130 by querying the database that only one engine is associated with the format of the found file, the method goes to step 735 in which an engine is selected which is associated with the format of the found file. If the application determines by querying the database that there are multiple engines associated with the format of the found file, then the method continues with step 740 ,

In step 740 presents the application 130 the user via a display device 110 on the user device 100 a list of all associated engines. In step 745 receives the application 130 from the user via the user input device 115 a selection of one of several dedicated engines. In step 750 starts the application 130 The selected engine that can be used to edit the requested file.

8A - 8B show a flowchart 800 a method for using an engine 135a to a feature of a file 125a to load and edit. When a user requests to open a file and, for example, using the steps in the flowchart 700 If an engine has been identified, the data of the file can be retrieved using the steps in Flowchart 800 are processed. The application 130 can the selected engine 135a after receiving a user input from a browser, such as the browser 210 , The engine 135a can the document through the browser 210 on a UI, such as the UI 200 , Starting in 8A in step 805 reads the engine 135a Data from the file 125a in accordance with the format of the file. In step 810 the processor that determines the engine determines 135a performs, such as the processor 105 whether the read data contains a characteristic. In step 815 places the engine 135a the feature in a node of the DOM, such as DOM 600 of the file 125a assigned. In step 820 determines the engine 135a whether the end of the file 125a is reached. Became the end of file 125a not reached, the process returns to step 805 to get more data from the file 125a to read. Is the end of file 125a reached, the method goes to step 825 continued. The model part of the engine 135a can take one or more steps 805 . 810 . 815 and 820 To run.

In step 825 reads the engine 135a a node of the DOM 600 while she's the DOM 600 passes. In decision block 830 determines the engine 135a whether it is configured to render the node or the file feature contained in the node. An engine configured to render a feature of a file is configured to read data from the memory associated with the feature in which the data is encoded in accordance with the format of the file. In some examples, the engine performs 135a This determination is based on information provided explicitly in the engine 135a are hard coded. Represents the engine 135a determines that it is not configured to render the feature, the method continues with step 835 away, where the engine 135a does not render the feature, and then moves to decision block 845 continued. Represents the engine 135a that they are the feature the procedure moves to step 840 continued. At step 840 renders engine 135a the feature contained in the node. Then the procedure moves with decision block 845 away, where the engine 135a determines if the end of the DOM 600 is reached. The engine 135a can make this determination by determining if all nodes of the DOM have been traversed. If the end of the DOM has not been reached, the procedure returns to step 825 where the engine 135a so that continues the DOM 600 to go through. When the end of the DOM is reached, the procedure goes to step 855 continued. The presentation share of the engine 135a can take one or more steps 825 . 830 . 835 . 840 and 845 To run.

In 8B in step 855 receives the engine 135a a user input to a feature of the DOM 600 changed document. The user can make this input via a graphical user interface, such as the interfaces 200 and 300 , For example, if the feature is a paragraph, the input may include a supplement to the text of the paragraph. As another example, the input may include instructions for changing the style of presentation, such as changing the font of the paragraph to a bold. These examples are not exhaustive and the user input may be any user input that changes the feature. In decision block 860 determines the engine 135a whether it is configured to process the feature. An engine configured to handle a feature of a file is configured to read data from memory and write data to memory wherein the data is associated with the feature and encoded in accordance with the format of the file are. For example, the engine provides 135a This is determined by decoding the contents of the node of the DOM corresponding to the feature to be processed. If the engine 135a In this example, the engine can successfully decode the contents of the node 135a that she can edit the feature; she finds that she can not handle the feature if she can not decode the contents of the node. Represents the engine 135a If it is determined that it is not configured to process the feature, then the method goes to step 865 away, where the engine 135a the feature does not change, and then moves directly to step 880 continued. Represents the engine 135a If it is determined that it is configured for processing the feature, the method moves to step 870 continued. In step 870 changes the engine 135a the node in DOM 600 that corresponds to the characteristic. The engine 135a can the DOM 600 after changing the node. In step 875 renders engine 135a the characteristic based on the content of the changed node. In an example of an optimistic update, the steps 870 and 875 running concurrently or asynchronously. In this example, the control share of the engine 135a Send updates directly to the presentation portion, and later the DOM 600 update and check.

In decision block 880 determines the engine 135a whether storage is required. Saving is required when the user makes an entry to save the document, or when an elapsed time has exceeded a predefined threshold. Represents the engine 135a determines that a save is required, the method goes to step 885 away, where the engine 135a those in the DOM 600 contained data in a file in accordance with the format of the found file 125a stores. For the nodes of the DOM 600 , for the processing of which the engine 135a is not configured, stores the engine 135a the data contained in these nodes is unchanged with respect to the original state of the data. Data in the nodes of the DOM 600 are included for their editing the engine 135a configured, can be changed from their original state, and the engine 135a stores this data in accordance with the original format of the found file 125a , In step 880 can the engine 135a all nodes in the DOM 600 save to a file, or store only a portion of the nodes, such as the updated nodes. In step 880 can the engine 135a alternatively in the DOM 600 save data in a different format than the original format of the file 125a , The selection of the format may be based on the selection of a user via the user input device 115 be determined. If the engine 135a in decision block 880 determines that no saving is required, the procedure continues 800 with step 855 away, where the engine 135a receives another user input. After saving in step 885 the procedure returns to step 855 back to where the engine 135a receives another user input. The procedure 800 can continue this loop until it is interrupted by the user. The user can do the procedure 800 by closing the document through a UI, or by simply closing a UI. For example, the control share of the engine 135a the steps 855 . 860 . 865 . 870 . 880 and 885 To run. In this example, the presentation share of the engine 135a step 875 To run. By keeping unsupported features in the nodes of the DOM 600 and preventing changes to these nodes will be the unsupported features of the file from the engine 135a maintained when the DOM 600 is stored.

9 shows a flowchart 900 a procedure that comes from an application 130 is used to create a file. A user can provide input through a user interface, such as the user interface 200 to create a file with a specific file format. In step 905 receives a processor, the application 130 executes a request from a user to create a file. In step 910 the processor determines that one or more of the engines 135 are configured to create a file. This determination can be made by querying a database, such as database 500 , In step 915 shows the application 130 provides the user with a list of formats associated with one or more of the engines configured to create a file. In step 920 receives the application 130 the user selects a format from the displayed list. In decision block 925 determines the application 130 Whether multiple engines are configured to create documents in the selected format. The application 130 can be a database 500 to determine if one or more engines are configured to create files in the selected format and associated with the application. If only one engine is configured to create documents in the selected format, the method goes to step 935 where this one engine is selected. If multiple engines are configured to create documents in the selected format, the procedure goes to step 930 away, where the application 130 Displays to the user a list of engines associated with the selected format. In step 940 receives the application 130 a selection of an engine 135a from the displayed list of engines. In step 945 starts the application 130 the selected engine 135a , In step 950 generates the started engine 135a a document in the selected format and renders the document for display to the user via the display 110 , In step 955 receives the started engine 135a User edits to the rendered document. These edits can be made in accordance with the steps of the procedure 800 be received. In step 960 saves the started engine 135a the document in a file 125a in accordance with the selected format. In some implementations, the method may 900 be simplified. In these implementations, the application can 130 the user in step 915 View a list of Engines, in step 920 Received a selection of an engine and go directly to step 945 continue where the application 130 the selected engine opens. In some implementations, the engine may 135a open or copy an empty template file instead of creating a new instance of a file.

10 shows a client / server system 1000 that has a cloud computing service 1002 and several client computers 1004a to 1004d includes. The cloud computing service 1002 may include one or more servers that together provide cloud computing services to multiple client computers. The cloud computing service 1002 stores multiple files on the client computer 1004a - 1004d including a sample spreadsheet 1006 that can be edited together. Users can use the cloud computing service 1002 create, edit, copy, share and delete stored data. For example, the client computers 1004a - 1004d using a web browser at the same time on the spreadsheet 1006 on the cloud computing service 1002 access. The cloud computing service 1002 makes each client computer a local copy of the spreadsheet 1006 that users can view and edit on the client computers. Edits, also referred to as mutations, by client computers 1004a are performed automatically to the cloud computing service 1002 sent and sent to the other client computer 1004b - 1004d transfer. Thus, changes by an employee are seen directly by other employees.

At the client computers 1004a - 1004d These can be desktop computers, laptops, tablets, smartphones, mobile electronic devices, or any other device that uses an external network with the cloud computing service 1002 can be connected. The system 1000 Can include many client computers that use the cloud computing service 1002 are connected. The cloud computing service 1002 and the client computer 1004a - 1004d from system 1000 are connected via an external network, such as the Internet. The network connection can be over a LAN, WAN, Ethernet, fiber optic network, wireless network, cellular telephone network, interactive TV network, telephone network, wireless data transmission system, two-way cable system, special private or public computer network, interactive kiosk network, a direct link, a satellite network and / or any other wired or wireless connection.

11 is a block diagram of a computing device, such as each of the components of the systems 1 - 10 to carry out any of the processes described in this document. Each of the components of these systems may be in one or more computing devices 1100 be implemented. In certain situations, several of the components of these systems can be used in a computing device 1100 be recorded. In certain implementations, a component and a storage device may have multiple computing devices 1100 be implemented.

The computing device 1100 includes at least one communication interface unit, an input / output controller 1110 , System memory and one or more data storage devices. The system memory includes at least one random access memory (RAM 1102 ) and at least one read-only memory (ROM 1104 ). All these elements communicate with the central processing unit (CPU 1106 ) to the operation of the computing device 1100 to simplify. The computing device 1100 can be configured in many different ways. This may be the case with the computing device, for example 1100 to handle a conventional stand-alone computer, or alternatively, the functions of the computing device 1100 distributed across multiple computer systems and architectures. Alternatively, a computer system can be virtualized to feature multiple computing devices 1100 provide. In 11 , the computing device 1100 is connected to other servers or systems via the network or local network.

The computing device 1100 can be configured in a distributed architecture where databases and processors can be distributed to separate units or locations. Some units perform primary processing functions and contain at least one common controller or processor and system memory. In distributed architecture implementations, each of these units can communicate over the communication interface unit 1108 can be connected to a communication hub or port (not shown) that serves as the primary communication link to other servers, client or user computers, or other associated devices. The communication hub or port may itself have minimal processing capacity and serves primarily as a communications router. A number of communication protocols may form part of the system, including, but not limited to, Ethernet, SAP, SAS ^™ , ATP, BLUETOOTH ^™ , GSM and TCP / IP.

The CPU 1106 includes a processor, such as one or more conventional microprocessors, and one or more ancillary co-processors, such as mathematical co-processors for relieving the CPU 1106 , The CPU 1106 communicates with the communication interface unit 1108 and the input / output controller 1110 about which the CPU 1106 communicates with other devices, such as other servers, user terminals, or devices. The communication interface unit 1108 and the input / output controller 1110 may include multiple communication channels for simultaneous communication with, for example, other processors, servers, or client terminals.

The CPU 1106 also communicates with the data storage device. The data storage device may include a suitable combination of magnetic, optical or semiconductor memory, and for example RAM 1102 , ROME 1104 , Flash drive, an optical disk, such as a compact disk or a hard disk or a drive. The CPU 1106 and the data storage device may each be completely contained in a single computer or other computing device, for example, or may be interconnected via a communication medium such as a USB port, a serial port cable, a coaxial cable, an Ethernet cable, a telephone line, a Radio frequency transceiver or similar wireless or wired medium or a combination of the above. For example, the CPU 1106 via the communication interface unit 1108 be connected to the data storage device. The CPU 1106 can be configured to perform one or more special processing functions.

The data storage device may, for example, store (i) an operating system 1112 for the computing device 1100 ; (ii) one or more applications 1114 (eg computer program code or a product of a computer program), adapted to the CPU 1106 can be controlled in accordance with the systems and methods described herein, and in particular in accordance with those with regard to the CPU 1106 detailed processes; or (iii) database (s) 1116 , which are adapted to store information that can be used to store information needed by the program.

The operating system 1112 and applications 1114 For example, they may be stored in a compressed, an uncompiled, and an encrypted format and may contain computer program code. The instructions of the program may be from a computer-readable medium other than the data storage device, such as the ROM 1104 or from the RAM 1102 , are read into a main memory of the processor. While executing command sequences in the program, the CPU 1106 to perform the process steps described herein, hardwired circuits may be used in place of or in combination with software instructions for the implementations of the processes of the present invention. Therefore, the systems and methods described herein are not limited to a specific combination of hardware and software.

Suitable computer program code may be provided for the performance of one or more functions with respect to the processes described in this document. The program may also contain program elements, such as an operating system 1112 , a database management system, and "device drivers" that allow the processor through the input / output controller 1110 to work with computer peripheral devices (such as a graphic display, keyboard, mouse, etc.).

The term "computer-readable medium" as used in this document refers to all non-volatile media containing instructions for the processor of the computing device 1100 (or another processor of a device described in this document) for execution or involved in this deployment. This medium can take many forms, including nonvolatile and volatile media, among others. Non-volatile media include, for example, optical, magnetic or opto-magnetic media or integrated memory circuitry, such as flash memory. The volatile media include dynamic RAM (DRAM), which usually serves as main memory. Common forms of computer-readable media include, for example, floppy disks, floppy disks, hard disks, magnetic tape, any other magnetic media, CD-ROMs, DVDs or any other optical media, punched cards, paper tape and other physical media with hole patterns, RAM, PROM, EPROM or EEPROM ("Electronically Erasable Programmable Read Only Memory"), FLASH EEPROM or other memory chip or cassettes, or any other non-volatile medium that a computer can read from.

Various forms of computer-readable media may be involved in one or more sequences having one or more instructions for the CPU 1106 (or any other processor of a device described in this document) for execution. For example, the instructions may first be carried on a magnetic disk of a remote computer (not shown). The remote computer can load these instructions into its dynamic memory and then send the instructions over an Ethernet connection, a cable, or even over a telephone line with a modem. A local communication device for a computing device 1100 (eg, a server) may receive the data on the associated communication line and place the data for the processor on a system bus. The system bus then transports the data to main memory, from which the processor subsequently retrieves and executes the instructions. The instructions received from main memory may optionally be stored either before or after execution by the processor. In addition, instructions may be received over a communication port as electrical, electromagnetic or optical signals; these are examples of wireless communication or data streams that carry a variety of different types of information.

 It will be understood that aspects of the systems and methods described herein may be implemented in many different forms of software, firmware and hardware in the implementations depicted in the drawings. The actual software code or actual specialized control hardware for implementing aspects in accordance with the principles of the systems and methods described herein is not limiting. Thus, the operation and behavior of the aspects of the systems and methods have been described without reference to the specific software code - it should be understood that one of ordinary skill in the art would be able to design software and control hardware based on the aspects to implement the descriptions here.

Similarly, while the operations on the drawings are presented in a particular order, it should not be construed that such operations must be performed in the particular order shown or in a sequential order, or that all operations shown must be performed to get the desired results. Under certain circumstances, multitasking and parallel processing can be beneficial.

Claims (12)

A system for processing documents in a native format, with a processor, configured for: receiving, while executing a first application, a request from a user to open a file created with a second application in a first format ; determining the first format of the file; selecting an engine of the plurality of engines associated with the first application, wherein the selected engine is configured to process the first format; opening the file using the selected engine in the first application without converting the format of the file into a second format associated with the first application; rendering, using the engine selected in the first application, the content of the file for display on a user device to the user; processing, using the engine selected in the first application, processing of the file in the first format; and saving, in a database, the edited file using the first application in the first format.  The system of claim 1, wherein the processor is further configured to display to the user a user interface containing tools for editing features of the selected engine.  The system of claim 1, wherein the processor is further configured to: determining if the selected engine is configured to handle a feature of the file; rendering, using the engine selected in the first application, the feature for display on a user device to the user; processing, using the engine selected in the first application, a processing of the rendered feature in the first format; and saving, in a database, the edited feature using the first application in the first format in the file.  The system of claim 1, wherein the processor is further configured to: determining if the selected engine is not configured to handle a feature of the file; rendering, using the engine selected in the first application, the content of the file for display on a user device to the user; preventing the user from changing the first feature; determining if the selected engine is configured to process a second feature of the file; rendering, using the engine selected in the first application, the second feature for display on a user device to the user; processing, using the engine selected in the first application, a processing of the second feature in the first format; and saving, in the database, the edited second feature using the first application in the first format in the file.  The system of claim 4, wherein the processor is further configured to: placing the data, using the selected engine, according to the first feature in a node of a document object model; assigning, the node, the property that the selected engine is not configured to handle the first feature; and saving, in the database, the placed data in the file using the first application in the first format.  The system of claim 1, wherein the processor is further configured to: determining if the selected engine is not configured to render a feature of the file; placing data corresponding to the feature in a node of a document object model; and assigning, the node, the property that the selected engine is not configured to render the first feature; saving, in the database, the placed data in the file using the first application in the first format.  The system of claim 1, wherein the file is stored on a server remote from the user.  The system of claim 1, wherein the processor is further configured to: finding the first format in a database; determining if an engine is associated with the first format; and selecting the associated engine;  The system of claim 1, wherein the processor is further configured to: reading a part of the file; extracting a file type from the read part; and determining the first format of the file based on the extracted file type.  The system of claim 8, wherein the processor is further configured to: determining that multiple engines are associated with the file format; displaying a plurality of names to the user, each name corresponding to one of the plurality of engines; receiving, from the user, a selected name from the plurality of names; and selecting the engine assigned to the selected name.  The system of claim 1, wherein the processor is further configured to store the file in a third format. A system for creating documents in a format, with a processor, configured for: receiving, at a processor executing an application, a request from a user to create a file; determining if one or more engines associated with the application are configured to create a file; displaying, the user, a list of formats associated with the one or more engines; receiving, by the user, a selection of a format from the displayed list; creating a document using an engine associated with the application associated with the selected format; and storing, in a database, the created document using the first application in the selected format.

Images