Hello,
I just got a report from a MF240 Series scanner that only 300dpi is
possible (allowed) scanning from the document feeder. Please test this
and report your results.
Many thanks for your help in advance.
Cheers,
Rolf
Am 26.04.2017 um 11:51 schrieb Rolf Bensch:
>
> Hello,
>
> I just commit
Are we already in Code Freeze?
I would like to commit a bug fix this weekend.
Rolf
Am 28.04.2017 um 14:04 schrieb m. allan noah:
> Ok folks, it's time to get another sane-backends release out the door.
>
> Olaf has done a good job of cleaning up our contributors list and
> curating the bug trac
Hello,
It's could be out of topic for MF240, but all allowed resolutions
(75/150/300/600dpi) tested give me good results with the new supported
MF230 series (MF232w).
Regards
Le vendredi 19 mai 2017 à 10:36 +0200, Rolf Bensch a écrit :
> Hello,
>
> I just got a report from a MF240 Series scanne
Hi Rolf,
Rolf Bensch writes:
> Are we already in Code Freeze?
Allan wrote:
>> May 14: Code freeze (only update docs after this date)
and since there has been nothing on the mailing list to the contrary,
I'd say, yes, we are in Code Freeze. For a good five days already.
> I would like to comm
What is the nature of the bug fix? Is it going to cause scanners that
worked with the prior release to be broken with this one? How big is
the fix? How likely to cause regressions?
allan
On Fri, May 19, 2017 at 5:13 AM, Rolf Bensch wrote:
> Are we already in Code Freeze?
>
> I would like to comm
I have a clinic where there are about seven scanners networked with
sane.d and xinetd. Right now when users open SimpleScan
and look at the list of available network scanners, they see all seven
named 'fujitsu-fl7160' in the list and have to memorize which order
their scanner is in the list.
Is t
The fujitsu backend includes the serial number of the scanner in the
device name. The users would have to memorize that number. Anything
more would be a code change. The best place to make such a change
would probably be in saned itself, so that all backends could benefit.
Unfortunately, many backe
Hi All(an),
m. allan noah writes:
> The fujitsu backend includes the serial number of the scanner in the
> device name. The users would have to memorize that number. Anything
> more would be a code change. The best place to make such a change
> would probably be in saned itself, so that all backe
Hi All(an),
m. allan noah writes:
> What is the nature of the bug fix? Is it going to cause scanners that
> worked with the prior release to be broken with this one? How big is
> the fix? How likely to cause regressions?
Here's where git branches come in nice. Rolf creates a branch, commits
his
Hi Curtis,
# Cc:ing sane-devel again. No need to leave the rest out, is there?
Curtis Graham writes:
> I may be talking out of turn here but from a simple Noob User
> perspective. I would like to see these 5 Networked scanners in a GUI
> list like Printers in the System Settings.
>
> How nice t
Hi,
Am 19.05.2017 um 15:02 schrieb Olaf Meeuwissen:
> Hi All(an),
>
> m. allan noah writes:
>
>> What is the nature of the bug fix? Is it going to cause scanners that
>> worked with the prior release to be broken with this one? How big is
>> the fix? How likely to cause regressions?
>
> Here's
Hi,
May be a little late, but I hope not too late. In the attachment you'll find
an update to the dutch translation. It completely replaces the current po-
file. B.t.w. the source was taken from git d.d. May 17, 2017
Hope someone can take care of my translation, thanks
Martin Kho
nl.po.gz
Desc
Got it, thanks!
allan
On Fri, May 19, 2017 at 2:34 PM, Martin Kho wrote:
> Hi,
>
> May be a little late, but I hope not too late. In the attachment you'll find
> an update to the dutch translation. It completely replaces the current po-
> file. B.t.w. the source was taken from git d.d. May 17, 2
Hi,
Rolf Bensch writes:
> Hi,
>
>
> Am 19.05.2017 um 15:02 schrieb Olaf Meeuwissen:
>> Hi All(an),
>>
>> m. allan noah writes:
>>
>>> What is the nature of the bug fix? Is it going to cause scanners that
>>> worked with the prior release to be broken with this one? How big is
>>> the fix? How lik
14 matches
Mail list logo
