Hi,
On 2022-07-18 03:19, Povilas Kanapickas wrote:
Hi John,
On 2022-07-18 05:25, John Scott wrote:
The SANE spec says that all strings are encoded in ISO-8859-1 ("Latin-
1"). However, from inspecting the code for sane_strstatus(), it appears
that it just returns ordinary string literals,
On 07/19/22 18:04, Ralph Little wrote:
Hi,
On 2022-07-18 03:19, Povilas Kanapickas wrote:
Hi John,
On 2022-07-18 05:25, John Scott wrote:
The SANE spec says that all strings are encoded in ISO-8859-1 ("Latin-
1"). However, from inspecting the code for sane_strstatus(), it appears
that it
Hi,
On 2022-07-18 03:19, Povilas Kanapickas wrote:
Hi John,
On 2022-07-18 05:25, John Scott wrote:
The SANE spec says that all strings are encoded in ISO-8859-1 ("Latin-
1"). However, from inspecting the code for sane_strstatus(), it appears
that it just returns ordinary string literals,
For Linux systems, C11 is a bit of the default as the Linux kernel now
requires C11. So that would get all the major Linux distros.
On Mon, Jul 18, 2022 at 10:48 AM John Scott wrote:
>
> On Mon, 2022-07-18 at 13:19 +0300, Povilas Kanapickas wrote:
> > By the way, does the current assumption
On Mon, 2022-07-18 at 13:19 +0300, Povilas Kanapickas wrote:
> By the way, does the current assumption actually break in practice, that
> is, are there compilers for which ASCII text will not encode to a subset
> of ISO-8859-1?
I assume you mean "Are there compilers for which narrow/multibyte
Hi John,
On 2022-07-18 05:25, John Scott wrote:
> The SANE spec says that all strings are encoded in ISO-8859-1 ("Latin-
> 1"). However, from inspecting the code for sane_strstatus(), it appears
> that it just returns ordinary string literals, which use whatever
> encoding the compiler prescribes