Version: 251
FC Stegerman wrote:
> I would argue that this is a bug in file(1) as Magdir/communications
> uses a "string" test, which is for binary files. If this is a text
> file, not a binary format, it should be forcing a text file test by
> using "string/t" instead.
>
> That said, this is li
* Chris Lamb [2023-10-11 14:51]:
> Niels Thykier wrote:
>
> > Digging a bit deeper, it turns out that `file -i` correctly classifies
> > the changelog as `text/plain; charset=utf-8`. That is, `file` knows it
> > is text and I suspect `diffoscope` should try `file -i` as well when it
> > gets
Chris Lamb:
Niels Thykier wrote:
Digging a bit deeper, it turns out that `file -i` correctly classifies
the changelog as `text/plain; charset=utf-8`. That is, `file` knows it
is text and I suspect `diffoscope` should try `file -i` as well when it
gets an unknown result from `file`.
By "unkno
Niels Thykier wrote:
> Digging a bit deeper, it turns out that `file -i` correctly classifies
> the changelog as `text/plain; charset=utf-8`. That is, `file` knows it
> is text and I suspect `diffoscope` should try `file -i` as well when it
> gets an unknown result from `file`.
By "unknown re
Package: diffoscope
Version: 250
Severity: wishlist
X-Debbugs-Cc: ni...@thykier.net
Hi,
I noticed that `diffoscope` used `hexdump -C` based diffs for the
debian/changelog in the `mscgen` package.
My first bet was that `file` would produce incorrect output and indeed,
`file` classifies that c
