5 ms·

Hi, I'm the author of emailthreads, mentionned in the article. I believe the library is already able to do something pretty close to what you want. See for exa

Hi, I'm the author of emailthreads, mentionned in the article. I believe the library is already able to do something pretty close to what you want. See for example this output: https://github.com/emersion/python-emailthreads/blob/master/test/data/multiple-replies/output3.txt https://github.com/emersion/python-emailthreads/blob/master/... (you can find source messages in the parent directory) The goal is to eventually build a web UI around this library.

cryptonector 8y ago
Oh, I skipped that paragraph. Oy, sorry. I think the text format for interleaving source and commentary needs its own discussion somewhere, and probably a standalone repository separate from implementation (and some day preferably too, an RFC, or at least a MIME type registration). I've looked at the examples you linked, and... I like that the review format for review authoring is just plain trivial. Not sure how it works with quote trimming... I'm not sure I like the output format, but I'll go think about it.
- Sir_Cmpwn 8y ago
  The output format is just a means of testing the library, not the final user-facing form this will take.
- emersion 8y ago
  >I think the text format for interleaving source and commentary needs its own discussion somewhere, and probably a standalone repository separate from implementation (and some day preferably too, an RFC, or at least a MIME type registration). Yeah, this library just parses email threads and the goal isn't to define a new format. This particular output format is just for debugging and unit testing, it's not meant to e actually used as is. The library user just gets a tree of text fragments with metadata, it's up to him how the output will look like.
Alex3917 8y ago
What's the main difference between the library you're building and mail parser?: https://pypi.org/project/mail-parser/ https://pypi.org/project/mail-parser/ Since there isn't any documentation, I'm just trying to figure out what's it's actually doing (without reading the source).
- Sir_Cmpwn 8y ago
  The library emersion is working on does not parse an email, it parses a thread of emails. It can relate several emails together into a tree of responses to the original email and break down the responses to e.g. particular lines of code in a patch.

cryptonector 8y ago

Oh, I skipped that paragraph. Oy, sorry. I think the text format for interleaving source and commentary needs its own discussion somewhere, and probably a standalone repository separate from implementation (and some day preferably too, an RFC, or at least a MIME type registration). I've looked at the examples you linked, and... I like that the review format for review authoring is just plain trivial. Not sure how it works with quote trimming... I'm not sure I like the output format, but I'll go think about it.

Sir_Cmpwn 8y ago
The output format is just a means of testing the library, not the final user-facing form this will take.
emersion 8y ago
>I think the text format for interleaving source and commentary needs its own discussion somewhere, and probably a standalone repository separate from implementation (and some day preferably too, an RFC, or at least a MIME type registration). Yeah, this library just parses email threads and the goal isn't to define a new format. This particular output format is just for debugging and unit testing, it's not meant to e actually used as is. The library user just gets a tree of text fragments with metadata, it's up to him how the output will look like.

Alex3917 8y ago

What's the main difference between the library you're building and mail parser?: https://pypi.org/project/mail-parser/ https://pypi.org/project/mail-parser/ Since there isn't any documentation, I'm just trying to figure out what's it's actually doing (without reading the source).

Sir_Cmpwn 8y ago
The library emersion is working on does not parse an email, it parses a thread of emails. It can relate several emails together into a tree of responses to the original email and break down the responses to e.g. particular lines of code in a patch.