Re: [fossil-users] Email notifications content transfer encoding

2018-06-26 Thread Rafal Bisingier
Hi, On 2018-06-26 at 09:35 -0400 Richard Hipp wrote: >Since Rafal's original inquiry, I have modified the email notification >logic to use quoted-printable instead of base64. Quoted-printable is >not as clean as plain-old 8bit, but it is much more readable than >base64. Acceptable compromise?

Re: [fossil-users] Email notifications content transfer encoding

2018-06-26 Thread Richard Hipp
Since Rafal's original inquiry, I have modified the email notification logic to use quoted-printable instead of base64. Quoted-printable is not as clean as plain-old 8bit, but it is much more readable than base64. Acceptable compromise? On 6/26/18, Rafal Bisingier wrote: > Hi > > Richard asked

Re: [fossil-users] Email notifications content transfer encoding

2018-06-26 Thread John P. Rouillard
Hi all: In message <20180626110936.3524bd1f@puter>, Rafal Bisingier writes: >Richard asked me to post it on the list for discussion, so here it is: >The new email notification functionality in fossil use base64 as >Content-Transfer-Encoding. I personally prefer use of 8bit encoding, >which have a

[fossil-users] Email notifications content transfer encoding

2018-06-26 Thread Rafal Bisingier
Hi Richard asked me to post it on the list for discussion, so here it is: The new email notification functionality in fossil use base64 as Content-Transfer-Encoding. I personally prefer use of 8bit encoding, which have a side-effect of human-readable source of message. I admit that it does not mat