[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ChangeLog encoding; testsuite file/s

From: Antonio Diaz Diaz
Subject: Re: ChangeLog encoding; testsuite file/s
Date: Thu, 13 Jan 2022 16:07:05 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv: Gecko/20110420 SeaMonkey/2.0.14

Hi Adam,

Adam Tuja wrote:
Hello, In latest lzlib Changlelog there is a name encoded in ISO (iso-8859-15 in
this case). If there will be some other name, form other part of the world then
it will be encoded differently, therefore displayed differently. You may want to
use UTF-8 in this case to unify it (diff attached).

Thank you, but I very much prefer the ISO-8859 encoding.

The is a testsuite in every package which, in my opinion is unnecessarily so
big. I refer here to `test*(.lz)' files. They don't have to be this big to show
and test features they represent.

Yes, they have to be that big, or even bigger. In lziprecover 1.16 a bug in --split was not detected by 'make check' because the test file was too small. In general a file needs to be larger than the input buffer to test that there are no problems when reaching the end of the buffer.

Shipping large test files in a separate package won't work; nobody will download it to run the additional tests.

BTW, the development version of gzip generates and compresses a file of 4 GiB of uncompressed size to test the new functionality of --list because it is the smallest file able to test it.

Best regards,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]