Hi,
Yeah, sorry about that.
I'm going to switch to my protonmail account shortly.
Perhaps that will get us less grief.
Cheers,
Ralph
On 2019-09-01 4:38 p.m., m. allan noah wrote:
We just had another round of this, so I flipped a few buttons in our
mailman config. Perhaps the next time Ralph
Hi,
One of the Debian patches currently being looked at
(0110-deb_inhibit_clickthrough), disables the pop-up license agreement
that xsane generates on first invocation.
To continue, you must accept the license.
Is it legal or proper for Debian to be doing this?
Cheers,
Ralph
--
sane-devel
Hi,
I'm almost at the stage where I need to start updating the file
structure of xsane to bring it up-to-date with modern practice.
What is the thinking about the configure script itself?
Many tar packages that I have seen use autotools to generate configure,
but a pre-prepared configure
Hi,
Would it be prudent to contact Oliver Rauch regarding his stance on
future copyright and how he would like attribution to be documented from
now on in subsequent versions?
Has he effectively assigned the code to the SANE project?
As we make updates, I would like some clarification as to
Hi,
I'm trying to figure out what the deal is with sane-config.
The Debian package that I have installs sane-config manpage but does not
install an actual sane-config.
However, there is a pkgconf file which we have in backends/tools.
This is related to my efforts to get xsane building properly.
Hi,
Looking for a bit of advice:
One of the patches for xsane from Debian further restricts the umask
setting for files created by xsane from the current value of 007 to 077.
Quoting one of the bug reports:
"xsane overwrites the user's umask to 0007, and creates ~/.sane and
other files with
Hi,
On 2019-08-23 11:04 p.m., Olaf Meeuwissen wrote:
I got a private email from Oliver saying that his priorities have
changed that it would be good if someone else picks maintenance.
Ralph, are you interested?
I guess so. Sign me up.
Cheers,
Ralph
--
sane-devel mailing list:
Hi,
On 2019-08-10 9:06 p.m., Olaf Meeuwissen wrote:
I kind of liked Boost's UTF :-)
I have used Boost's UTF and I found it pretty handy. I agree that it is
great if you already have Boost dependencies.
It handles the auto generation of boilerplate typically associated with
unit test suites
Hi,
On 2019-08-10 9:56 a.m., Povilas Kanapickas wrote:
The genesys backend on the current master comprises of 42 files. I
propose to move it under `backend/genesys`? The same could eventually be
done to other larger backends (or maybe even all backends) as the
`backend` directory is becoming
that is not too wordy.
Cheers,
Ralph
On 2019-08-10 3:29 a.m., abel deuring wrote:
Am 10.08.19 um 09:31 schrieb Olaf Meeuwissen:
Hi Ralph,
littlesincanada writes:
Hi,
While scanning through the messages to fix up some grammar and spelling
mistakes, I came across this following in the file:
backend
Hi,
While scanning through the messages to fix up some grammar and spelling
mistakes, I came across this following in the file:
backend/kvs40xx_opt.c:405
There is a message that I cannot decipher:
"Long Paper Mode is a mode that the scanner reads the image after it
divides long paper by the
Hi,
On 2019-08-05 6:00 a.m., Olaf Meeuwissen wrote:
I would warn strongly against touching po/*.po files for any language
that you are not intimately familiar with. I know it's tempting to
unfuzzy because you made some minor change, e.g. s/behaviour/behavior/
or some punctuation change, but
Hi Olaf,
On 2019-07-26 10:04 p.m., Olaf Meeuwissen wrote:
Wheezy was the most recent Debian release that I was able to build XSane
on without extra work. I guess someone could take a look at the patches
used to build on Debian Buster (released earlier this month) and see
what can be used to
Hi,
On 2019-07-26 10:04 p.m., Olaf Meeuwissen wrote:
Wheezy was the most recent Debian release that I was able to build XSane
on without extra work. I guess someone could take a look at the patches
used to build on Debian Buster (released earlier this month) and see
what can be used to make
Hi Olaf,
I guess those are marked as fuzzy. The gettext tools will preseed
untranslated message strings based on "similar" translated strings.
Obviously, that sometimes leads to radically wrong translations.
These fuzzy strings will *not* be used at run-time. They are just
there in an attempt
15 matches
Mail list logo
