Hello, I added advanced mailto: support to trojita and its IPC (for delivering mailto from other applications/command line to GUI).
Current trojita mailto: implementation in master support only parsing one email address which is specified after scheme. I tried to add advanced support as described in RFC 6068. Code is in my pali-gsoc branch and needs more testing, because I used QUrl and still do not know if I used QUrl correctly for parsing. I tested some examples from RFC 6068: mailto:%22%5C%5C%5C%22it's%5c%20ugly%5c%5c%5c%[email protected] mailto:[email protected]?subject=caf%C3%A9 mailto:gorby%[email protected] mailto:[email protected],[email protected] mailto:[email protected][email protected] And it is correctly decoded in trojita compose new mail window. What my implementation does not support is custom email headers (only to, cc, bcc, subject, body, in-reply-to and references are supported by trojita invokeComposeDialog()) and decoding quote printable strings. So for example this mailto: url mailto:[email protected]?subject=%3D%3Futf-8%3FQ%3Fcaf%3DC3%3DA9%3F%3D is badly decoded, and trojita new mail window show subject as: =?utf-8?Q?caf=C3=A9?= I do not know if other email clients are able to decode above mailto:, but it is not easy. It is needed to support this? Is this widely used on internet? Or utf8 escaping (mailto:?subject=caf%C3%A9) is enough? -- Pali Rohár [email protected]
signature.asc
Description: This is a digitally signed message part.
