Re: [sane-devel] canon dr-2580c invalid argument

2014-05-10 Thread gobo
you are correct, it is SLE customer support.

i tend to agree with you about sled, and perhaps the kubuntu 12.04lts
i have on my laptop, but i need the stability those releases provide.
so compared to the opensuse i run at home, i guess they are
positively ancient.

i have a case open with sle support.  they want the details on how i
came up with the debug info i sent them.  they made it sound like if
this was a known issue, then addressing it with a community package
release might not be out of the question.

it will be monday before i can get the rest of the info requested by
support.  at that time, i'll pass on what you have suggested.  i'll
let you know what they (sle support) says.  it might be interesting.

thanks for the assistance.




On 5/9/14, Johannes Meixner jsm...@suse.de wrote:

 Hello,

 On May 8 12:15 gobo wrote (excerpt):
 this is under SLED 11 sp3.  they tend to be behind.  i'll have to see
 if they have anything newer.

 On 5/8/14, m. allan noah kitno...@gmail.com wrote:
 Suggestions- yes. sane-backends 1.0.20 is positively ancient. upgrade.

 It depends on who they is ;-)

 If they is the official SUSE Enterprise Customer Support,
 then they do not have a newer sane-backends RPM package.

 If they is openSUSE, then I provide in my openSUSE home project
 sane-backends-1.0.22 RPM packages built for SLE_11_SP3
 (i.e.  SLES 11 SP3 and SLED 11 SP3) for 32-bit i586
 and 64-bit x86_64 architecture.

 Why no current sane-backends-1.0.24 for SLE11?
 Because it does no longer build (with reasonable effort for me)
 in the positively ancient SLE11 environment.

 For direct RPM download go to
 http://download.opensuse.org/repositories/home:/jsmeix/SLE_11_SP3/

 Before you install such RPM packages, carefully read
 https://build.opensuse.org/project/show?project=home%3Ajsmeix
 --
 Home Project of Johannes Meixner
 http://en.opensuse.org/User:Jsmeix

 This is my personal playground where
 packages could be severely incompatible
 with official openSUSE packages.

 Do not somehow add the whole home:jsmeix
 repository to be used by your package
 installer (e.g. via YaST).
 Using the whole home:jsmeix repository
 could be a perfect way to mess up your
 system.
 Instead only download the packages
 of your particular interest which match
 your excat system from the appropriate
 sub-directory in
 http://download.opensuse.org/repositories/home:/jsmeix/
 and install them manually
 (e.g. using plain rpm).
 If you are unexperienced with manual
 installation, do not install any package
 from home:jsmeix.

 Packages in the home:jsmeix project might
 neither be in usable state nor fit into
 currently installed systems.
 Have this in mind if you think about to
 install packages from home:jsmeix into
 your currently running system.
 Do not use Factory if your system is
 not Factory.
 Use the matching packages for your
 particular system.
 The packages in the home:jsmeix project
 are only for testing, without any guarantee
 or warranty, and without any support.
 As an extreme example, this means if your
 complete computer center crashes because
 of those packages, it is only your problem.
 On the other hand this does not mean that
 all those packages are known to be terrible
 broken (but some of those packages could
 be really broken) and none of those packages
 are thoroughly tested so that any unexpected
 issue can happen.
 --

 Personally - without any guarantee or warranty - I assume
 sane-backends-1.0.22 from the home:jsmeix project should
 just work for SLE 11 SP3 - but I have not verified it.

 When you have a support contract with our official SUSE Enterprise
 Customer Support, then check with them whether or not installing
 sane-backends-1.0.22 from the home:jsmeix project might
 somehow invalidate your support contract.


 Kind Regards
 Johannes Meixner
 --
 SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
 HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject unsubscribe your_password
 to sane-devel-requ...@lists.alioth.debian.org


Re: [sane-devel] scanimage / tesseract interoperability

2014-05-10 Thread Jeff Breidenbach
Thank you Simon, the --batch-script feature looks very flexible.
It almost does the trick:

   scanimage --batch --batch-script (echo) | tesseract - -

Unfortunately, it runs just a little too early. The script executes
just before the temporary image file is renamed. Tesseract
wants to know about the final filename after it exists.

My very first implementation attempt didn't work; the emitted
filename somehow ended up in the image data. Is there a problem
with scanimage writing to standard output?

  if (new_interoperability_feature) fprintf(stdout, %s\n, path);

I ultimately hope to make scanimage and tesseract work
together nicely for everyone. So any suggestions or advice
are appreciated.

Cheers,
Jeff
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject unsubscribe your_password
 to sane-devel-requ...@lists.alioth.debian.org