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
This feature will add a converter (an internal one) that can convert the RTF body into HTML should the HTML body not exist. This ignores encapsulated HTML entirely, strictly looking at RTF tags for this. Unfortunately, it is likely that one will have to be created from scratch, as I have not been able to find a working converter that actually follows the standards of RTF, the most important being how to actually process toggles. Every RTF to HTML converter I have looked at so far will blatantly ignore the state listed by the toggle, always switching the state instead of setting it to what the toggle requests.
This feature is necessary for the proper completion of support for custom outlook images. As far as I can tell, these only appear when the body type is set to be RTF and the RTF has no encapsulated HTML. These images are stored in a custom format, and the position to show them is given as a number of rendered characters, making it important to calculate how many characters have been shown on the page. Plain text to HTML conversion is usually not sufficient, as links are often shown using more characters than would be rendered, causing some images to be inserted into the wrong place.
The text was updated successfully, but these errors were encountered:
This feature will add a converter (an internal one) that can convert the RTF body into HTML should the HTML body not exist. This ignores encapsulated HTML entirely, strictly looking at RTF tags for this. Unfortunately, it is likely that one will have to be created from scratch, as I have not been able to find a working converter that actually follows the standards of RTF, the most important being how to actually process toggles. Every RTF to HTML converter I have looked at so far will blatantly ignore the state listed by the toggle, always switching the state instead of setting it to what the toggle requests.
This feature is necessary for the proper completion of support for custom outlook images. As far as I can tell, these only appear when the body type is set to be RTF and the RTF has no encapsulated HTML. These images are stored in a custom format, and the position to show them is given as a number of rendered characters, making it important to calculate how many characters have been shown on the page. Plain text to HTML conversion is usually not sufficient, as links are often shown using more characters than would be rendered, causing some images to be inserted into the wrong place.
The text was updated successfully, but these errors were encountered: