Hi, OK, I will draft something up for the standard. If there is anything else to update the standard with, perhaps people could let me know. Just to be clear, I am not changing the interface with this update, just adding come clarification, so if anybody feels that there is anything else unclear in the standard, they should possibly raise it now.
I will add address this on the weekend. Cheers, Ralph On Wed, Jun 4, 2025 at 8:57 AM m. allan noah <[email protected]> wrote: > Makes sense to me. > > On Wed, Jun 4, 2025 at 10:12 AM Ralph Little <[email protected]> wrote: > >> Hi, >> >> On Tue, Jun 3, 2025 at 11:36 PM <[email protected]> wrote: >> >>> On Tue, Jun 03, 2025 at 10:00:45PM -0700, Ralph Little wrote: >>> > On Tue, Jun 3, 2025 at 9:54 PM James Ring <[email protected]> wrote: >>> > > On Tue, Jun 3, 2025 at 9:46 PM Ralph Little <[email protected]> >>> wrote: >>> > >> Someone has asked the question about byte order in multi-byte image >>> data >>> > >> that we might get from a SANE backend. >>> >>> Hi, it's me, I had the question. >>> >>> > >> It is not enough to assume the local machine byte order since we >>> may get >>> > >> data through the net backend from a remote machine with a different >>> byte >>> > >> order. >>> >>> The `net` backend explicitly swaps to local machine byte order: >>> >>> https://gitlab.com/sane-project/backends/-/blob/master/backend/net.c?ref_type=heads#L2356-2362 >>> >>> So, it does seem like the de facto standard is that backends produce >>> data in local machine byte order. >>> >>> (The protocol documentation reinforces this as a standard: >>> >> >> Agreed. Perhaps this is something we should add to the SANE API >> specification? >> Allan, do you concur? >> >> Cheers, >> Ralph >> > > > -- > "well, I stand up next to a mountain- and I chop it down with the edge of > my hand" >
