Microsoft Technology Licensing, LLC

Benjamen E Ross

David Charles LeBlanc

Benjamin E Canning

Joshua Michael Pollock

Brian Thomas Carver

Daniel Browne Jump

Vikas Malhotra

James Campbell

Matthew D Wood

Kenneth Lawrence Young

Josh Pollock

Cynthia Dahl Wessling

Zhenjun Zhu

Michael D Schackwitz

Stephen M Blanding

Tara Kraft

George Taniwaki

Nitin Chopra

Matt Wood

Donald Elman

Architecture that provides a secure environment in which data (e.g., code, instructions, files, images, etc.) can be opened and run by a client application. Once opened the data can be viewed (in a 'protected view') by the user without incurring risk to other client processing and systems. Accordingly, the architecture mitigates malicious attacks by enabling users to preview untrusted and potentially harmful data (e.g., files) in a low risk manner. Files opened in the protected view are isolated from accessing key resources on the client computer and provides the user a safer way to read files that can contain dangerous content. The protected view also provides a seamless user experience. The user is unaware that the client is operating on data in a different mode and allows for the reduction of security prompts.

Isolation and presentation of untrusted data

Input data is validated by generating code based on the input data. A schema is generated based on the input data indicating conditions for the input file. The schema may then be customized based on a type of application to consume the input data. A validator executable code is generated based on the schema and checks the input file for compliance with the conditions determined by the schema. Results of validation may be provided to the application in yes or no form, or as number of non-compliances. In the latter case, the application may decide to accept or reject the data based on predetermined non-compliance levels.

Generating code to validate input data

Systems and methods are disclosed for exporting a document in multiple formats. The disclosed systems and methods may include creating a metafile including content associated with the document and injecting comments into the metafile. The comments may comprise semantic information corresponding to the document. Also, the metafile may be parsed to create at least one call. The at least one call may be configured to enable an export engine to render the document. Furthermore, the at least one call may be sent to the export engine configured to render the document in an output format associated with the export engine. In addition, the export engine maybe selected from a plurality of export engines based upon user input indicating the output format associated with the selected export engine.

Exporting a document in multiple formats

Data in a file is read to virtual, autonomous, hierarchically structured object classes that are independent of an application implementation. The object classes are navigable and/or actionable allowing various operations including, but not limited to, validation, integrity testing, 'file open', and file repair at the data level. By rendering a complete picture of the data including relationships before it is actually consumed by an application, security and robustness of applications can be enhanced.

Representing file data using virtual hierarchy

Methods and systems are provided for dynamically generating and displaying previews of documents or templates of interest to a user. As a user provides or selects customized designs or themes, including color themes, font types, images, and the like, previews of one or more documents or templates to which the user selected designs or themes are applied are dynamically generated and are displayed to allow the user to select an actual document or template for use.

Dynamic document and template previews

A publishing program can provide continuous and real-time feedback on possible design problems while a document is being edited or created. The feedback can include displaying a user interface that has a real-time list of any design problems that may be a result of the current edits or creations in a document. The list is updated as the document is being created or edited. A user can toggle between the list and the document as often as desired. The list can identify all current potential publication problems of an electronic document as well as the types of the publication problems that may be present in an electronic document.

Automatic correction, and skipping of document design problems based on document types

A publisher program for automatically changing the layout of content-filled desktop publishing documents. The publisher program allows the author of a document to use a menu-driven utility to define a first layout for the document. A program module known as a Wizard then renders a document in the first layout. The author makes changes to the document while the document is in the first layout, typically by adding content and making author-defined changes to the document rendered by the Wizard. The author may then return to the menu-driven utility to select a second layout for the document. The Wizard renders a document in the second layout and a program module known as a Page Manager automatically applies the author's changes to the document and renders a content-filled document in the second layout.

Desktop publishing software for automatically changing the layout of

A method and system for compressing publication documents in a computer system is provided. In a preferred embodiment, one or more computer documents are initially represented in a data structure. The data structure is made up of a number of constituent data structures connected by links. In order to compress the data structure, two or more constituent data structures that match are identified. All but one of the identified constituent data structures are then deleted. Finally, links to the deleted constituent data structures are replaced with links to the selected constituent data structure.

Growing community of inventors

Seattle, WA, United States of America

Benjamen E Ross