Editing Officeparser.py

<!-- Use the structure provided in this template, do not change it! -->

{{Infobox_tool
|purpose=officerparser.py is a python script that parses the format of OLE compound documents used by Microsoft Office applications.
|image={{PAGENAMEE}}.png
|homepage=https://github.com/unixfreak0037/officeparser
|license=MIT License
|platforms=Cross-platform (Python)
}}
<!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. -->

<!-- Add one or more categories to describe the function of the tool, such as:
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) -->
[[Category:Metadata Extraction]]
[[Category:File Format Identification]]

<!-- Add relevant categories to describe the content type that the tool addresses, such as:
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. -->
[[Category:Document]]

== Description ==
<!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. -->

It can perform:

* macro extraction
* embedded file extraction
* format analysis


== User Experiences ==
<!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. -->

* [http://blog.avira.com/malicious-office-macros-dead/ Malicious Office macros are not dead]

== Development Activity ==
<!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. -->

<!-- Add the OpenHub.com ID for the tool, if known. -->
{{Infobox_tool_details
|ohloh_id=
}}