Correct docstrings and changelog

Author: TheElementalOfDestruction

CHANGELOG.md

@@ -1,8 +1,8 @@
 **v0.52.0**
 * [[TeamMsgExtractor #444](https://github.com/TeamMsgExtractor/msg-extractor/issues/444)] Fix typo in string that prevented HTML body from generating from the plain text body properly.
 * Adjusted the behavior of `MSGFile.areStringsUnicode` to prioritize the property specified by the parent MSG files for MSG files that are embedded. Additionally, added a fallback to rely on whether or not there is a stream using the `001F` type to determine the property value if it is entirely missing.
-* Adjusted `OleWriter.fromMsg()` and `MSGFile.export()` to add the argument `allowBadEmbed` which helps to correct a few different issues that may appear in embedded MSG files. These corrections allow the extracte file to still be extracted and to open properly in Outlook.
-* In addition to the above, the errors that some of those corrections will surpress are now significantly more informative about what went wrong.
+* Adjusted `OleWriter.fromMsg()` and `MSGFile.export()` to add the argument `allowBadEmbed` which helps to correct a few different issues that may appear in embedded MSG files. These corrections allow the embedded file to still be extracted and to open properly in Outlook.
+* In addition to the above, the errors that some of those corrections will suppress are now significantly more informative about what went wrong.
 
 **v0.51.1**
 * Add class type added in last version to known class types.

extract_msg/msg_classes/msg.py

@@ -492,6 +492,8 @@ def export(self, path, allowBadEmbed: bool = False) -> None:
 
         :param path: A path-like object (including strings and ``pathlib.Path``
             objects) or an IO device with a write method which accepts bytes.
+        :param allowBadEmbed: If True, attempts to skip steps that will fail if 
+            the embedded MSG file violates standards. It will also attempt to repair the data to try to ensure it can open in Outlook.
         """
         from ..ole_writer import OleWriter
 
@@ -504,9 +506,12 @@ def export(self, path, allowBadEmbed: bool = False) -> None:
     def exportBytes(self, allowBadEmbed: bool = False) -> bytes:
         """
         Saves a new copy of the MSG file, returning the bytes.
+
+        :param allowBadEmbed: If True, attempts to skip steps that will fail if 
+            the embedded MSG file violates standards. It will also attempt to repair the data to try to ensure it can open in Outlook.
         """
         out = io.BytesIO()
-        self.export(out)
+        self.export(out, allowBadEmbed)
         return out.getvalue()
 
     def fixPath(self, inp: MSG_PATH, prefix: bool = True) -> str:

extract_msg/ole_writer.py

@@ -808,8 +808,11 @@ def fromMsg(self, msg: MSGFile, allowBadEmbed: bool = False) -> None:
         """
         Copies the streams and stream information necessary from the MSG file.
 
-        :param allowBadEmbed: If true, attempts to skip steps that will fail if 
-            the embedded msg file violates standards. It will also attempt to repair the data to try to ensure it can open in Outlook.
+        :param allowBadEmbed: If True, attempts to skip steps that will fail if 
+            the embedded MSG file violates standards. It will also attempt to repair the data to try to ensure it can open in Outlook.
+
+        :raises StandardViolationError: Something about the embedded data has a
+            fundemental issue that violates the standard.
         """
         # Get the root OLE entry's CLSID.
         self.__rootEntry.clsid = _unClsid(msg._getOleEntry('/').clsid)