You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, injecting into the RTF body when it has encapsulated HTML uses the following process:
Use a simple detector that only works on very clean encapsulated HTML and use that to inject (very reliable).
If the encapsulated HTML is "dirty" (generally because huge numbers of tags are all shoved together into a destination and making it so it's impossible to just use generic detection to insert successfully right after the body tag), ignore the fact that is has encapsulated HTML and just treat it as standard RTF, using the code added in 0.40.0.
This is not to be considered urgent, just noting that it is (hopefully) planned for a future version to have code that can clean up the data a bit more to make it so that even some of the worst encapsulated HTML can be fixed up for RTF injection so it can be successfully deencapsulated at some other point.
Some things it will need to be able to do:
Recognize encapsulated HTML and it's relevant RTF tags.
Understand how to module \*\htmltag destinations to clean them up.
Be able to correctly adjust the order of tags in the event that HTML tags appear before the end of the RTF header, where putting text could cause corruption.
Add HTML tags for extemly poor quality RTF documents (some encapsulated HTML is completely missing tags like <html>, <body>, etc.).
The text was updated successfully, but these errors were encountered:
If you wish to temporarily silence this issue until a patch can be made for RTFDE, you can pass errorBehavior = extract_msg.enums.ErrorBehavior.RTFDE_UNKNOWN_ERROR as a keyword argument to openMsg.
Currently, injecting into the RTF body when it has encapsulated HTML uses the following process:
This is not to be considered urgent, just noting that it is (hopefully) planned for a future version to have code that can clean up the data a bit more to make it so that even some of the worst encapsulated HTML can be fixed up for RTF injection so it can be successfully deencapsulated at some other point.
Some things it will need to be able to do:
\*\htmltag
destinations to clean them up.<html>
,<body>
, etc.).The text was updated successfully, but these errors were encountered: