Removing style corruption from extensible markup language documents

• US 8,281,236 B2
• Filed: 09/08/2010
• Issued: 10/02/2012
• Est. Priority Date: 09/08/2010
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Gundorov, Sergei
• Primary Examiner(s): Ries, Laurie
• Application Number:
  US12/877,860
• Publication Number:
  US 20120060086A1
• Time in Patent Office: 755 Days
• Field of Search: 715/235, 715/236, 715/237
• US Class Current: 715/236
• CPC Class Codes: G06F 40/117 Tagging; Marking up details of markup languages G06F40/143; Designating a block; Setting of attributes style sheets, e.g. eXtensible Stylesheet Language Transformation [XSLT], G06F40/154
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 40/221 Parsing markup language streams streaming G06F40/149

Abstract

Unused, duplicate, or corrupted styles are removed from XML based document files through a styles definition part of a document using system input output. The removal is based on the analysis of the information contained in a compressible package of a respective document file. Other incorrect file content may also be removed such as corrupted name ranges or unused value format definitions using the same approach.

Claims

1. A method executed at least in part in a computing device for removing style corruption from extensible markup language (XML) based documents, the method comprising:

reading style information associated with an XML based document;

determining at least one from a set of unused, corrupted, and duplicate styles by matching style definitions for the document with style parts in a document package;

removing at least one from the set of the unused, corrupted, and duplicate styles without opening the XML based document in a rich application associated with the XML based document;

determining corrupted name ranges; and

removing the corrupted name ranges from the XML based document.

2. The method of claim 1, further comprising:

determining whether the document package is a valid XML package.

3. The method of claim 1, further comprising:

presenting an option to revert the XML based document to a default format; and

in response to an affirmative selection, reverting the XML based document to the default format by removing all custom styles.

4. The method of claim 1, wherein the XML based document is one of a spreadsheet, a chart, a word processor, and a presentation document.

5. The method of claim 1, further comprising:

determining whether the XML based document has more than a predetermined number of custom styles.

6. The method of claim 5, reverting the XML based document to a default format by removing all custom styles if the XML based document has more than the predetermined number of custom styles.

7. The method of claim 1, further comprising:

presenting the style information of the XML based document to a user; and

removing the unused, corrupted, and duplicate styles upon user affirmation.

8. The method of claim 1, further comprising:

removing the unused, corrupted, and duplicate styles automatically.

9. The method of claim 8, wherein the unused, corrupted, and duplicate styles are removed during an automated XML based document recovery.

10. A computing device for removing style corruption from extensible markup language (XML) documents, the computing device comprising:

a memory

a processor coupled to the memory, the processor executing a module in conjunction with instructions stored in the memory, wherein the module is configured to;

determine whether a document package including an XML based document to be examined is a valid XML based package;

read a style information associated with the XML based document;

determine at least one from a set of unused, corrupted, and duplicate styles by matching style definitions for the XML based document with style parts in a document package;

remove at least one from the set of the unused, corrupted, and duplicate styles without opening the XML based document in a rich application associated with the XML based document;

determine corrupted name ranges; and

remove the corrupted name ranges from the XML based document.

11. The computing device of claim 10, wherein the module is further configured to:

determine whether the XML based document has more than a predetermined number of custom styles;

present an option to revert the XML based document to a default format; and

in response to an affirmative selection, revert the XML based document to the default format by removing all custom styles.

12. The computing device of claim 10, wherein the module is one of a command line executable program, a program library, and a server tool set.

13. The computing device of claim 10, wherein the module employs a system input output component to directly access the XML based document.

14. The computing device of claim 10, wherein the module is implemented in a document sharing service automatically removing style corruption from shared documents at the service.

15. The computing device of claim 10, wherein the module is implemented as a style tool on a client device and further configured to present a graphical user interface providing options with configuration of removal of corrupted styles.

16. The computing device of claim 10, wherein the module is further configured to determine the validity of the document package based on evaluating whether all parts defined by a standard packaging protocol exist in the document package.

17. A computer-readable storage medium with instructions stored thereon for removing style corruption from extensible markup language (XML) documents, the instructions comprising:

determining whether a document package including an XML based document to be examined is a valid XML based package;

reading a style information associated with the XML based document;

determining whether the XML based document has more than a predetermined number of custom styles;

reverting the XML based document to a default format by removing all custom styles if the XML based document has more than the predetermined number of custom styles;

else

determining at least one from a set of unused, corrupted, and duplicate styles by matching style definitions for the XML based document with style parts in a document package;

removing at least one from the set of the unused, corrupted, and duplicate styles without opening the XML based document in a rich application associated with the XML based document;

determining corrupted name ranges; and

removing the corrupted name ranges from the XML based document.

18. The computer-readable storage medium of claim 17, wherein the rich application associated with the XML based document includes one of:

a word processing application, a spreadsheet application, a presentation application, a diagramming application, and a browsing application.

19. The computer-readable storage medium of claim 17, wherein an incorrect value in the XML based document is replaced by setting the incorrect value to a predetermined default value.