Records Tab - Tabular Data Converted in Email File Issues

**Describe the bug in current situation**

When email files contain tabular data, and they are converted to PDF via the conversion service, there are various formatting issues with the data based on on the formatting and structure of the tabular data. These are successfully uploaded, deduplicated, and converted, however (no error being thrown).

This occurred on TRA-2023-32239 and TRA-2023-31981 in PROD.

See EDU-2022-00043 in TEST as example, files "Test Tabular Data in Email .msg" and "Test Tabular Data 2.msg"

Example 1

Native file with tabular data

Converted to PDF via Records tab

Example 2

Native file with tabular data


Converted to PDF via Records tab

**Link bug to the User Story**

**Impact of this bug**
Describe the impact, i.e. what the impact is, and number of users impacted.

**Chance of Occurring (high/medium/low/very low)**

**Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?**
PROD

Occurred on TRA-2023-32239 and TRA-2023-31981 in PROD

**Steps to Reproduce**
Steps to reproduce the behavior:
1. Go to a request and upload a email file with tabular data in the message body
2. Click on let the file go through dedupe and conversion
3. Open the converted email file and review message body
4. See error

**Actual/ observed behaviour/ results**
Tabular data formatting is not retained / legible

**Expected behaviour**
A clear and concise description of what you expected to happen. Use the gherking language.
GIVEN an email file has tabular data in the message body
AND it has been uploaded to the Records tab
WHEN the request goes through dedupe and conversion
AND you download the converted file or the redline
THEN the tabular data formatting will show up accurately in the message body (i.e., matching the native file)

Reproduce the issue with the "Test Tabular Data in Email .msg" and "Test Tabular Data 2.msg" examples in the Records tab. Start by tracing the email-to-PDF conversion handling for tabular message-body content and compare the converted output with the native files. Done means the converted file and redline retain legible tabular formatting matching the native file.

Written by the indexing model from the issue text.