Here's an example where the parser does not properly identify all quotes (based on a real email we have to handle).
Hi S.,
Thanks for reaching out with availability, and good to meet you too!
Wednesday at 4:30 pm or Friday at 2:30 pm both look like they would work for me and R.
Thanks,
T.
----------- Original Message -----------
From: "S."
Date: Monday, July 24th 2023 at 3:59 pm
Subject: Sync
To: "R." ,
Cc: "K."
> Hey R. and T.,
>
> Nice to meet you T.! Opening up another thread to coordinate time for a chat this week about the integration. Here\'s some availability this week for myself and one of our sales engineers:
>
> Tuesday: 3: 30 - 6pm
>
> Wednesday: 4 - 5pm
>
> Friday: 2: 30 - 3pm, 3: 30 - 4: 30
>
> Do any of these work for you ? Let me know and I\'ll send out the invite for a 45 min call.
>
> Looking forward to it,
>
> S.
>
> (image)
Will determine the following lines as unquoted text:
"Hi S.,
Thanks for reaching out with availability, and good to meet you too!
Wednesday at 4:30 pm or Friday at 2:30 pm both look like they would work for me and R.
Thanks,
T.
>
> Tuesday: 3: 30 - 6pm
>
> Wednesday: 4 - 5pm
>
> Friday: 2: 30 - 3pm, 3: 30 - 4: 30
>
> Do any of these work for you ? Let me know and I'll send out the invite for a 45 min call."
Not sure if that is easy to handle by extending the regular expression that looks for the quote character by allowing white-space before it.
Here's an example where the parser does not properly identify all quotes (based on a real email we have to handle).
Will determine the following lines as unquoted text:
Not sure if that is easy to handle by extending the regular expression that looks for the quote character by allowing white-space before it.