Improve incoming email transformation of HTML tables to pure text
to be more like "text in columns" or create CSV as attachment to issue (issue creation/commenting) with respect to (have info plain text version).
Other possible option if "JEdit" is not there and content is recognized as advance create e.g. PDF rendition and place that as attachment to issue with respect to (have info plain text version)
we have already scheduled the task of converting html emails to wiki markup keeping as much formatting as is possible.
What we will not do is to attach the original email in CSV/PDF to the issue.
It is question so it is expect that it is not need any extra plugin and that e.g. some text will not be transform to "smiles". But I guess that using wiki means also changing comment types so it is possible that that smiles transformation and so on is no so good in case when you have code suggestion parts or something like that.
Maybe if it is not needed a extra plugin and this is applied by option just on email tab that could be solution of course if original problem will be solved it means broken tables, lists.
We have mails with tables where each row of the table is transformed to a block of rows, followed by an empty row, then the next block of rows for the next table row and so on. Is this the actual handling?
1 2 3
4 5 6