sane(7)

📦
version 1.4.0 · 10 versions
, in fedora 43, fedora 44

💅 NAME 💅

Okay bestie, welcome to sane(7) — the icon itself, SANE Scanner Access Now Easy: the API for accessing scanners. Yes, that's the whole name section. She's short but she's powerful. 🎀

✨ DESCRIPTION ✨

So SANE is an application programming interface (API) that gives you standardized access to any raster image scanner hardware. Literally any. And the whole point of that standardized interface? It means you write just one driver for each scanner device instead of one driver for each scanner and each application. The way that saves everyone's sanity... no cap. 🧚

And yeah, SANE is primarily targeted at a UNIX environment, but the standard was carefully designed so the API can be implemented on virtually any hardware or operating system. She's flexible like that. 💅

This manual page gives you a summary of all the info available about SANE. Think of it as the group chat pinned message. 📌

🌸 If you're having trouble getting your scanner detected, go read the PROBLEMS section. Fr fr, don't skip her.

🦋 TERMINOLOGY 🦋

Let's get our vocabulary right, bestie — iykyk:

  • A SANE frontend — an application that uses the SANE interface. She's the one asking for the scan. 👑
  • A SANE backend — a driver that implements the SANE interface. She's the one doing the actual work. 🔥
  • A meta backend — provides some means to manage one or more other backends. Manager energy. Main character energy, honestly. ⭐

🎀 SOFTWARE PACKAGES 🎀

Okay so here's the package lore:

  • The package sane-backends contains backends, documentation, networking support, and the command line frontend scanimage(1). Everything. She ate. 🍓
  • The frontends xscanimage(1), xcam(1), and scanadf(1) are included in the package sane-frontends. Different package, same vibe. 💖

Both packages can be downloaded from the SANE homepage (http://www.sane-project.org/). And info about other frontends and backends can also be found on the SANE homepage. One stop shop. 🌈

🌸 GENERAL INFORMATION 🌸

The following sections give you short descriptions and links to more info about several aspects of SANE. Housekeeping first, before we get into the fun stuff:

  • A name with a number in parenthesis (like sane-dll(5)) points to a manual page. In this case, man 5 sane-dll will display the page. Magic. ✨
  • Entries like /usr/share/doc/sane-backends/README are references to text files that were copied to the SANE documentation directory (/usr/share/doc/sane-backends/) during installation. 💜
  • Everything else is a URL to a resource on the web.

💻 SANE homepage

Information on all aspects of SANE — including a tutorial and a link to the SANE FAQ — can be found on the SANE homepage: http://www.sane-project.org/. Bookmark her. She's iconic. 🔖

🦋 SANE device lists

The SANE device lists contain info about the status of SANE support for a specific device. If your scanner is not listed there (either supported or unsupported), please contact us — see section HOW CAN YOU HELP SANE for details. We want to know about your scanner, bestie. 🫶

There are lists for specific releases of SANE, for the current development version, and a search engine: http://www.sane-project.org/sane-supported-devices.html.

The lists are also installed on your system at /usr/share/doc/sane-backends/. Offline access, periodt. 💅

📬 SANE mailing list

There is a mailing list for the purpose of discussing the SANE standard and its implementations: sane-devel. And despite its name, the list is not only intended for developers — it's for users too. So don't be shy. 🎀

There are also some more lists for special topics. However, for users, sane-devel is the right list. How to subscribe and unsubscribe: http://www.sane-project.org/mailing-lists.html.

💬 SANE IRC channel

The IRC (Internet Relay Chat) channel #sane can be found on the Freenode network (irc.libera.chat). It's for discussing SANE problems, talking about development, and general SANE related chatting. 🗣️

🙈 Before asking for help, please read the other documentation mentioned in this manual page. Do your reading first, queen.

The channel's topic is also used for announcements of problems with SANE infrastructure (mailing lists, web server, etc.). So like, check the topic, it might already be addressed. ✨

🔨 Compiling and installing SANE

Look at /usr/share/doc/sane-backends/README and the os-dependent README files for info about compiling and installing SANE. Build girlies, this one's for you. 👑

🖥️ SCSI configuration

For info about various systems and SCSI controllers, see sane-scsi(5). 🦋

🔌 USB configuration

For info about USB configuration, see sane-usb(5). Plug her in, bestie. 💜

🌈 FRONTENDS AND MISCELLANEOUS PROGRAMS 🌈

📸 scanimage

Command-line frontend. See scanimage(1). Terminal girlies rise. 💅

🌐 saned

SANE network daemon that allows remote clients to access image acquisition devices available on the local host. See saned(8). Networking slay. 🔥

🔍 sane-find-scanner

Command-line tool to find SCSI and USB scanners and determine their UNIX device files. See sane-find-scanner(1). She finds things. She's a finder. ⭐

Also, have a look at the sane-frontends package (which includes xscanimage(1), xcam(1), and scanadf(1)) and the frontend information page at http://www.sane-project.org/sane-frontends.html. Loads more where that came from. 🎀

🎀 BACKENDS FOR SCANNERS 🎀

Bestie, this is the scanner backend roster, and it’s giving range. No skips, no “oops I forgot that one” — every name is right here. 💅

  • abaton — Handles Abaton flatbed scanners like the Scan 300/GS (8bit, 256 levels of gray) and the Scan 300/S (black and white, untested). Details are in sane-abaton(5).
  • agfafocus — Covers AGFA Focus scanners and the Siemens S9036 (untested). See sane-agfafocus(5).
  • apple — Apple flatbed scanners, including AppleScanner, OneScanner and ColorOneScanner. See sane-apple(5).
  • artec — Several Artec/Ultima SCSI flatbed scanners, plus the BlackWidow BW4800SP and the Plustek 19200S. See sane-artec(5).
  • artec_eplus48u — The Artec E+ 48U scanner and re-badged models like the Tevion MD 9693, Medion MD 9693, Medion MD 9705 and Trust Easy Webscan 19200. See sane-artec_eplus48u(5).
  • as6e — The Artec AS6E parallel port interface scanner. See sane-as6e(5).
  • avision — Several Avision based scanners, including the original Avision scanners (like AV 630, AV 620, ...) plus the HP ScanJet 53xx and 74xx series, Fujitsu ScanPartner, and some Mitsubishi and Minolta film-scanners. See sane-avision(5).
  • bh — Bell+Howell Copiscan II series document scanners. See sane-bh(5).
  • canon — The CanoScan 300, CanoScan 600, and CanoScan 2700F SCSI flatbed scanners. See sane-canon(5).
  • canon630u — The CanoScan 630u and 636u USB scanners. See sane-canon630u(5).
  • canon_dr — Canon DR-Series ADF SCSI and USB scanners. See sane-canon_dr(5).
  • canon_lide70 — The CanoScan LiDE 70 and 600 USB scanners. See sane-canon_lide70(5).
  • canon_pp — The CanoScan FB330P, FB630P, N340P and N640P parallel port scanners. See sane-canon_pp(5).
  • cardscan — Support for Corex Cardscan USB scanners. See sane-cardscan(5).
  • coolscan coolscan2 coolscan3 — Nikon Coolscan film-scanners. See sane-coolscan(5), sane-coolscan2(5) and sane-coolscan3(5).
  • epjitsu — Epson-based Fujitsu USB scanners. See sane-epjitsu(5).
  • epson — Old driver for Epson SCSI, parallel port and USB flatbed scanners. See sane-epson(5) — but try epson2 first, bestie.
  • epson2 — Newer driver for Epson SCSI, parallel port, network and USB flatbed scanners (try this before epson, which is outdated). See sane-epson2(5).
  • escl — Scanners through the eSCL protocol. See sane-escl(5).
  • fujitsu — Most Fujitsu SCSI and USB, flatbed and adf scanners. See sane-fujitsu(5).
  • genesys — Several scanners based on the Genesys Logic GL646, GL841, GL843, GL847 and GL124 chips, like the Medion 6471 and Hewlett-Packard 2300c. See sane-genesys(5).
  • gt68xx — Scanners based on the Grandtech GT-6801 and GT-6816 chips, like the Artec Ultima 2000 and several Mustek BearPaw CU and TA models. Some Genius, Lexmark, Medion, Packard Bell, Plustek, and Trust scanners are also supported. See sane-gt68xx(5).
  • hp — Hewlett-Packard ScanJet scanners that utilize SCL (Scanner Control Language by HP). See sane-hp(5).
  • hpsj5s — The Hewlett-Packard ScanJet 5S scanner. See sane-hpsj5s(5).
  • hp3500 — The Hewlett-Packard ScanJet 3500 series. See sane-hp3500(5).
  • hp3900 — The Hewlett-Packard ScanJet 3900 series. See sane-hp3900(5).
  • hp4200 — The Hewlett-Packard ScanJet 4200 series. See sane-hp4200(5).
  • hp5400 — The Hewlett-Packard ScanJet 54XXC series. See sane-hp5400(5).
  • hpljm1005 — The Hewlett-Packard LaserJet M1005 scanner. See sane-hpljm1005(5).
  • hs2p — The Ricoh IS450 family of SCSI scanners. See sane-hs2p(5).
  • ibm — Some IBM and Ricoh SCSI scanners. See sane-ibm(5).
  • kodak — Some large Kodak scanners. See sane-kodak(5).
  • kodakaio — Kodak AiO printer/scanners. See sane-kodakaio(5).
  • kvs1025 — Panasonic KV-S102xC scanners. See sane-kvs1025(5).
  • leo — The LEO S3 and the Across FS-1130, which is a re-badged LEO FS-1130 scanner. See sane-leo(5).
  • lexmark — The Lexmark X1100 series of USB scanners. See sane-lexmark(5).
  • lexmark_x2600 — The Lexmark X2600 series of USB scanners. See sane-lexmark_x2600(5).
  • ma1509 — The Mustek BearPaw 1200F USB flatbed scanner. See sane-ma1509(5).
  • magicolor — The KONICA MINOLTA magicolor 1690MF multi-function printer/scanner/fax. See sane-magicolor(5).
  • matsushita — Some Panasonic KVSS high speed scanners. See sane-matsushita(5).
  • microtek — “Second generation” Microtek scanners with SCSI-1 command set. See sane-microtek(5).
  • microtek2 — Some Microtek scanners with a SCSI-2 command set. See sane-microtek2(5).
  • mustek — Most Mustek SCSI flatbed scanners, including the Paragon and ScanExpress series and the 600 II N and 600 II EP (non-SCSI). Some Trust scanners are also supported. See sane-mustek(5).
  • mustek_pp — Mustek parallel port flatbed scanners. See sane-mustek_pp(5).
  • mustek_usb — Some Mustek ScanExpress USB flatbed scanners. See sane-mustek_usb(5).
  • mustek_usb2 — Scanners using the SQ113 chipset, like the Mustek BearPaw 2448 TA Pro USB flatbed scanner. See sane-mustek_usb2(5).
  • nec — The NEC PC-IN500/4C SCSI scanner. See sane-nec(5).
  • niash — The Agfa Snapscan Touch and the HP ScanJet 3300c, 3400c, and 4300c USB flatbed scanners. See sane-niash(5).
  • p5 — The Primax PagePartner. See sane-p5(5).
  • pie — Pacific Image Electronics (PIE) and Devcom SCSI flatbed scanners. See sane-pie(5).
  • pixma — Canon PIXMA MP series (multi-function devices), Canon imageCLASS series (laser devices), Canon MAXIFY series and some Canon CanoScan series. See sane-pixma(5).
  • plustek — USB flatbed scanners that use the National Semiconductor LM983[1/2/3] chipset aka Merlin. Scanners using this LM983x chips include some models from Plustek, KYE/Genius, Hewlett-Packard, Mustek, Umax, Epson, and Canon. See sane-plustek(5).
  • plustek_pp — Plustek parallel port flatbed scanners using the Plustek ASIC P96001, P96003, P98001 and P98003, which includes some models from Plustek, KYE/Genius, Primax. See sane-plustek_pp(5).
  • ricoh — The Ricoh flatbed scanners IS50 and IS60. See sane-ricoh(5).
  • ricoh2 — The Ricoh flatbed scanners: SG-3100SNw, SP-100SU, and SP-111SU. See sane-ricoh2(5).
  • s9036 — Siemens 9036 flatbed scanners. See sane-s9036(5).
  • sceptre — The Sceptre S1200 flatbed scanner. See sane-sceptre(5).
  • sharp — Sharp SCSI scanners. See sane-sharp(5).
  • sm3600 — The Microtek ScanMaker 3600 USB scanner. See sane-sm3600(5).
  • sm3840 — The Microtek ScanMaker 3840 USB scanner. See sane-sm3840(5).
  • snapscan — AGFA SnapScan flatbed scanners, including some which are rebadged to other brands. See sane-snapscan(5).
  • sp15c — The Fujitsu FCPA ScanPartner 15C flatbed scanner. See sane-sp15c(5).
  • st400 — The Siemens ST400 and ST800. See sane-st400(5).
  • tamarack — Tamarack Artiscan flatbed scanners. See sane-tamarack(5).
  • teco1 teco2 teco3 — Some TECO scanners, usually sold under the Relisys, Trust, Primax, Piotech, Dextra names. See sane-teco1(5), sane-teco2(5) and sane-teco3(5).
  • u12 — USB flatbed scanners based on Plustek’s ASIC 98003 (parallel-port ASIC) and a GeneSys Logics’ USB-parport bridge chip, like the Plustek OpticPro U(T)12. See sane-u12(5).
  • umax — UMAX-SCSI-scanners and some Linotype Hell SCSI-scanners. See sane-umax(5).
  • umax_pp — Umax parallel port flatbed scanners and the HP 3200C. See sane-umax_pp(5).
  • umax1200u — The UMAX Astra 1220U (USB) flatbed scanner (and also the UMAX Astra 2000U, sort of). See sane-umax1220u(5).
  • xerox_mfp — Multiple Samsung-based Samsung, Xerox, and Dell scanners. See sane-xerox_mfp(5).

Also, have a look at the backend information page at http://www.sane-project.org/sane-supported-devices.html and the list of projects in /usr/share/doc/sane-backends/PROJECTS.

🌈 BACKENDS FOR DIGITAL CAMERAS 🌈

Now the camera girlies get their moment too. 📸✨

  • dc210 — The Kodak DC210 Digital Camera. See sane-dc210(5).
  • dc240 — The Kodak DC240 Digital Camera. See dc240(5).
  • dc25 — Kodak DC20/DC25 Digital Cameras. See dc25(5).
  • dmc — The Polaroid Digital Microscope Camera. See dmc(5).
  • gphoto2 — Digital cameras supported by the gphoto2 library package. (See http://www.gphoto.org for more information and a list of supported cameras.) Gphoto2 supports over 140 different camera models. However, please note that more development and testing is needed before all of these cameras will be supported by SANE backend. See gphoto2(5).
  • qcam — Connectix QuickCam cameras. See qcam(5).
  • stv680 — Webcams with a stv680 chip. See stv680(5) for details.

Also, have a look at the backend information page at http://www.sane-project.org/sane-supported-devices.html and the list of projects in /usr/share/doc/sane-backends/PROJECTS.

🎀 MISCELLANEOUS BACKENDS 🎀

okay so these ones don't fit in the camera or scanner boxes, but they're lowkey iconic in their own way:

  • dll — bestie this is the meta one 👑 it implements a SANE backend that gives you access to an arbitrary number of other SANE backends by dynamic loading. See sane-dll(5).
  • net — the SANE network daemon saned(8) hooks you up with scanners living on completely different computers, working together with the sane-net(5) backend. See saned(8).
  • pnm — a PNM image reader pseudo-backend ✨ its whole purpose is basically to help debug SANE frontends. See sane-pnm(5).
  • pint — supports scanners that use the PINT (Pint Is Not Twain) device driver. The PINT driver is being actively developed on the OpenBSD platform and has been ported to a few other *NIX-like operating systems. See sane-pint(5).
  • test — literally tests frontends and the SANE installation itself 🧪 gives you test pictures and various test options. See sane-test(5).
  • v4l — generic access to video cameras and similar equipment using the V4L (Video for Linux) API. See sane-v4l(5).

alsooo, go peek at the backend information page at http://www.sane-project.org/sane-supported-devices.html and the list of projects in /usr/share/doc/sane-backends/PROJECTS. iykyk 💅

✨ CHANGING THE TOP-LEVEL BACKEND ✨

so by default, literally all SANE backends (drivers) get loaded dynamically by the sane-dll meta backend. if you have any questions about dynamic loading, read sane-dll(5) 🦋

SANE frontends can also be linked to other backends directly — by copying or linking a backend to libsane.so in /usr/lib64/sane.

🌸 DEVELOPER'S DOCUMENTATION 🌸

ngl bestie, it's not hard to write a SANE backend. it can take some time though 😭 you should have basic knowledge of C and enough patience to work through the documentation and find out how your scanner actually works. appended below is a list of some documents that help you write backends and frontends.

The SANE standard defines the application programming interface (API) that's used to communicate between frontends and backends 💖 you can find it at http://sane-project.gitlab.io/standard/ .

There's some more info for programmers in /usr/share/doc/sane-backends/backend-writing.txt. most of the internal SANE routines (sanei) are documented using doxygen: http://www.sane-project.org/sanei/ . and before you start a new backend or frontend project, please have a look at /usr/share/doc/sane-backends/PROJECTS for projects that are planned or not yet included in the SANE distribution, and at our bug-tracking system: http://www.http://www.sane-project.org/bugs.html .

yes, that URL really is written like that in here 🙈 we're keeping it exactly as-is, no cap.

There are some links on how to find out about the protocol of a scanner: http://www.meier-geinitz.de/sane/misc/develop.html .

and if you start writing a backend or frontend or literally any other part of SANE, please contact the sane-devel mailing list for coordination so that work is not duplicated 🫶 teamwork makes the dream work fr fr.

🎀 FILES 🎀

  • /etc/sane.d/*.conf — the backend configuration files.
  • /usr/lib64/sane/libsane-*.a — the static libraries implementing the backends.
  • /usr/lib64/sane/libsane-*.so — the shared libraries implementing the backends (present on systems that support dynamic loading).
  • /usr/share/doc/sane-backends/* — SANE documentation: the READMEs, text files for backends, etc.

😭 PROBLEMS 😭

okay so your device isn't found but you know it's supported? first vibe check: make sure it's actually detected by your operating system. for SCSI and USB scanners, use the sane-find-scanner(1) utility. it prints one line for each scanner it has detected, plus some comments (#).

if sane-find-scanner(1) finds your scanner only as root but not as a normal user, the permissions for the device files aren't adjusted correctly 🔥 if the scanner isn't found at all, the operating system hasn't detected it and may need some help. depending on the type of your scanner, read sane-usb(5) or sane-scsi(5). and if your scanner (or other device) isn't connected over the SCSI bus or USB, read the backend's manual page for details on how to set it up.

So is your scanner detected by the operating system but not by SANE? try scanimage -L. if the scanner isn't found, check that the backend's name is mentioned in /etc/sane.d/dll.conf. some backends are commented out by default — remove the comment sign for your backend in this case 💅

also, some backends aren't compiled at all if one of their prerequisites is missing. examples include dc210, dc240, canon_pp, hpsj5s, gphoto2, pint, qcam, v4l, net, sm3600, snapscan, pnm. if you need one of these backends and it isn't available, read the build instructions in the README file and the individual manual pages of the backends 📖

Another reason for not being detected by scanimage -L may be a missing or incorrect configuration in the backend's configuration file. while SANE tries to automatically find most scanners, some can't be set up correctly without the intervention of the administrator. also on some operating systems auto-detection may just not work. check the backend's manual page for details 🦋

If your scanner is still not found, try setting the various environment variables that are available to assist in debugging. the environment variables are documented in the relevant manual pages. for example, to get the maximum amount of debug information when testing a Mustek SCSI scanner, set environment variables SANE_DEBUG_DLL, SANE_DEBUG_MUSTEK, and SANE_DEBUG_SANEI_SCSI to 128, and then invoke scanimage -L. the SANE_DEBUG_DLL messages tell you if the sane-mustek(5) backend was found and loaded at all. the SANE_DEBUG_MUSTEK messages explain what the backend is doing, while the SANE_DEBUG_SCSI debugging shows the low level handling. if you can't figure out what's going on by checking the messages carefully, contact the sane-devel mailing list for help (see REPORTING BUGS below) 🫶

Now that your scanner is found by scanimage -L, try to do a scan:

scanimage >image.pnm

this command starts a scan for the default scanner with default settings ✨ all the available options are listed by running scanimage --help. if scanning aborts with an error message, turn on debugging as mentioned above. maybe the configuration file needs some tuning, e.g. to set up the path to a firmware that's needed by some scanners — see the backend's manual page for details. if you can't find out what's wrong, contact sane-devel 😭

To check that the SANE libraries are installed correctly you can use the test backend, even if you don't have a scanner or other SANE device:

scanimage -d test -T

you should get a list of PASSed tests 🎉 you can do the same with your backend by changing "test" to your backend's name.

So now scanning with scanimage (1) works and you wanna use one of the graphical frontends like xsane(1), xscanimage(1), or quiteinsane(1), but those frontends don't detect your scanner? hmm. one reason may be that you installed two versions of SANE 💀 e.g. the version that was installed by your distribution in /usr and one you installed from source in /usr/local/. make sure only one version is installed!

Another possible reason is that your system's dynamic loader can't find the SANE libraries. for Linux, make sure that /etc/ld.so.conf contains /usr/local/lib and does not contain /usr/local/lib/sane. see also the documentation of the frontends 👑

💖 HOW CAN YOU HELP SANE 💖

we appreciate any help we can get, fr fr 🫶 please have a look at our web page about contributing to SANE: http://www.sane-project.org/contrib.html

🌈 CONTACT 🌈

for reporting bugs or requesting new features, please use our bug-tracking system: http://www.sane-project.org/bugs.html .

you can also contact the author of your backend directly — usually the email address can be found in the /usr/share/doc/sane-backends/AUTHORS file or the backend's manpage. for general discussion about SANE, please use the SANE mailing list sane-devel (see http://www.sane-project.org/mailing-lists.html for details) 💌

⭐ SEE ALSO ⭐

saned(8), sane-find-scanner(1), scanimage(1), sane-abaton(5), sane-agfafocus(5), sane-apple(5), sane-artec(5), sane-artec_eplus48u(5), sane-as6e(5), sane-avision(5), sane-bh(5), sane-canon(5), sane-canon630u(5), sane-canon_dr(5), sane-canon_pp(5), sane-cardscan(5), sane-coolscan(5), sane-coolscan2(5), sane-coolscan3(5), sane-dc210(5), sane-dc240(5), sane-dc25(5), sane-dll(5), sane-dmc(5), sane-epson(5), sane-epson2(5), sane-escl(5), sane-fujitsu(5), sane-genesys(5), sane-gphoto2(5), sane-gt68xx(5), sane-hp(5), sane-hpsj5s(5), sane-hp3500(5), sane-hp3900(5), sane-hp4200(5), sane-hp5400(5), sane-hpljm1005(5), sane-ibm(5), sane-kodak(5), sane-leo(5), sane-lexmark(5), sane-lexmark_x2600(5), sane-ma1509(5), sane-matsushita(5), sane-microtek2(5), sane-microtek(5), sane-mustek(5), sane-mustek_pp(5), sane-mustek_usb(5), sane-mustek_usb2(5), sane-nec(5), sane-net(5), sane-niash(5), sane-pie(5), sane-pint(5), sane-plustek(5), sane-plustek_pp(5), sane-pnm(5), sane-qcam(5), sane-ricoh(5), sane-ricoh2(5), sane-s9036(5), sane-sceptre(5), sane-scsi(5), sane-sharp(5), sane-sm3600(5), sane-sm3840(5), sane-snapscan(5), sane-sp15c(5), sane-st400(5), sane-stv680(5), sane-tamarack(5), sane-teco1(5), sane-teco2(5), sane-teco3(5), sane-test(5), sane-u12(5), sane-umax1220u(5), sane-umax(5), sane-umax_pp(5), sane-usb(5), sane-v4l(5), sane-xerox_mfp(5)

👑 AUTHOR 👑

David Mosberger-Tang and many many more (see /usr/share/doc/sane-backends/AUTHORS for details). this man page was written by Henning Meier-Geinitz ✨ quite a lot of text was taken from the SANE standard, several man pages, and README files 🫶

and that's a wrap bestie!! 💅✨ this whole glowing masterpiece is from 03 Jan 2020, and it's the sane(7) page itself — slay, go scan something iconic 🎀🦋

📦 where this page comes from
  • fedora 43: sane-backends 1.4.0-4.fc43 · GPL-2.0-or-later WITH SANE-exception AND GPL-2.0-or-later AND GPL-2.0-only AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LicenseRef-Fedora-Public-Domain AND IJG AND MIT
  • fedora 44: sane-backends 1.4.0-6.fc44 · GPL-2.0-or-later WITH SANE-exception AND GPL-2.0-or-later AND GPL-2.0-only AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LicenseRef-Fedora-Public-Domain AND IJG AND MIT
  • 💖 girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms