TWAIN SANE Interface for MacOS X

This is a TWAIN datasource for MacOS X that aquires images using the SANE backend libraries. The SANE backend libraries provide access to a large range of scanners connected through SCSI or USB. For a complete list see the documentation on the SANE project homepage. It works with my HP SCSI scanner, and many people have reported success with a large number of different scanners. The feedback from users have helped the SANE developers to fix problems with various backends, so with each release of the SANE backends more of the MacOS X specific problems have been solved.

The TWAIN SANE interface is not a standalone application. It is designed to be used from within other applications. It works with applications supporting the TWAIN specification, which includes most applications on Mac OS X that handles images. However using it with Apple‘s Image Capture application has become increasingly tricky with every version of Mac OS X. You will have an easier experience if you choose any other application.

The TWAIN SANE Interface is provided as a binary package and as source code. To use the interface you only have to install the binary package. Before installing the TWAIN SANE Interface package you should install the libusb and the sane-backends binary packages.

There is also a optional SANE Preference Pane package available, which makes it easier to configure the sane-backends drivers. If you don’t install this package you can still configure the sane-backends using a text editor in the Terminal.

If you have trouble making it work, please consult the list of frequently asked questions.

If you want to compile the sources you also have to install the gettext package. If you are cross-compiling using the MacOS X cross-compilation SDKs you need to install the corresponding SDKs for the used packages.

You are welcome to contact me at mattias.ellert@physics.uu.se if you want to have more information about the TWAIN SANE Interface, or if you want to submit bug reports, localizations errors, suggestions for improvments or patches.

The latest version is 3.6.

Mattias Ellert

Downloads

	Version	Installer	Sources	Project Homepage
TWAIN SANE Interface	3.6			http://www.ellert.se/twain-sane/
SANE Preference Pane	1.6			http://www.ellert.se/twain-sane/
SANE backends	1.0.25			http://www.sane-project.org/
libusb	0.1.13 beta			http://www.libusb.org/
gettext	0.19.8.1			http://www.gnu.org/software/gettext/

Older versions.

Release Notes

TWAIN SANE Interface version 3.6, 2017-05-26

• Compiled for macOS 10.9 or later.

SANE Preference Pane version 1.6, 2017-05-27

• Compiled for macOS 10.6 or later

sane-backends version 1.0.25, 2017-05-22

• Compiled for macOS 10.9 or later
• Stop building SDK packages

libusb version 0.1.13 beta, 2016-11-02

• Compiled for macOS 10.9 or later
• Stop building SDK packages

gettext version 0.19.8.1, 2017-05-21

• Compiled for macOS 10.7 or later
• Stop building SDK packages

Localizations

The TWAIN SANE Interface has been localized to the following languages: English, French, German, Italian, Japanese, Russian and Swedish. For most of the translation it relies on the localization support in the SANE backend libraries.

If you want to provide localization support for a different language you are welcome to do that. What you should do is the following:

• You might want to check with me that I did not already recieve the localization for your language from someone else...
• First check if there exists a file called /usr/local/share/locale/〈langcode〉/LC_MESSAGES/sane-backends.mo containing the localizations for the SANE backend libraries for your language. If there is no such file you must first localize the SANE backend libraries. For more information about this see the SANE project homepage.
• Download the TWAIN SANE Interface source code.
• After unpacking the source tarball you will find in it a directory called src. In this directory there is one language project directory for each language (English.lproj, Swedish.lproj, etc.). In these directories there are two files called InfoPlist.strings and Localizable.strings.
• You should create your own copy of these two files and change the translations. These files contain several lines of the type "key" = "value". Do not change the keys, but translate the values. Note that these files should be in the UTF-8 encoding.
• There is also a set of language project files in the pkg/Resources directory. These contain localization files for the Installer called. If you want you can also provide localized versions of these. These files are also of the "key" = "value" type and should also be in the UTF-8 encoding.
• Send the files to me, and I will include them in my next release.

Mattias Ellert