Original Message
From: Stephen J. Turnbull [mailto:turnbull.stephen...@u.tsukuba.ac.jp]
Sent: Wednesday, April 21, 2021, 18:28 UTC
> In fact, most modern systems will negotiate compressed streams, so if
> you provide a .txt to your webserver, the client will tell the server
>
Mark Sapiro writes:
> In short, the file contains just what it should, but there is a
> Content-Transfer-Encoding issue.
Technical niggle, probably not relevant to the issue itself:
The charset parameter is an attribute of Content-Type.
Content-Transfer-Encoding should be transparent to this
A bit OT, I'm glossing Mark Sapiro's explanation of compressed file
handling in Mailman archive downloads.
Mark Dale via Mailman-Users writes:
> Thank you Mark, that information is appreciated and I've made the change.
I'm glad you find it useful. Note that the story is a little more
subtle
Original Message
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Wednesday, April 21, 2021, 01:53 UTC
> Slightly off topic, but after the cron/nightly_gzip job runs, the
> .txt.gz file will be updated with the contents from the .txt file.
>
> However, the point of this
On 4/20/21 5:20 PM, Mark Dale via Mailman-Users wrote:
>
> Just to clarify: there are two .txt files ...
>
> (A) an archive .txt.gz file before I made the change to the mm_cfg.py file;
> and
> (B) an archive .txt.gz file after I made the change.
Slightly off topic, but after the
Original Message
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Tuesday, April 20, 2021, 18:55 UTC
> On 4/19/21 10:43 PM, Mark Dale via Mailman-Users wrote:
>>
>> François -- as seen in the mm_cfg modified download txt: the cedille
>> replace by odd characters.
>
> How
On 4/19/21 10:43 PM, Mark Dale via Mailman-Users wrote:
>
> François -- as seen in the mm_cfg modified download txt: the cedille replace
> by odd characters.
How are you viewing the .txt file? The two bytes C3 A7 are the utf-8
representation of the c-cedilla character. If you view that file as
Original Message
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Friday, April 9, 2021, 19:07 UTC
> On 4/9/21 5:55 AM, Mark Dale via Mailman-Users wrote:
>>
>> In the archive's downloaded .txt (and also .gz) file, the non-ascii
>> characters are missing and displayed as
On 4/9/21 5:55 AM, Mark Dale via Mailman-Users wrote:
>
> In the archive's downloaded .txt (and also .gz) file, the non-ascii
> characters are missing and displayed as "?".
...
> Any advice on getting the non-ascii characters written into the archive .txt
> file would be gratefully received.
