From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] Contributing braille embosser support
Date: Thu, 10 Dec 2015 22:31:47 +0100 [thread overview]
Message-ID: <20151210213147.GK2905@var.home> (raw)
In-Reply-To: <5669E84B.2090400@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
Till Kamppeter, on Thu 10 Dec 2015 19:02:03 -0200, wrote:
> OK, thanks. So please go ahead with the fixes.
Here is an updated tarball.
BTW, which licence would it be better to release this code under? I'm
fine with most free software licences.
> And I am also grateful if you do the maintenance of your code when it is in
> cups-filters as I do not know much about Braille embossers and also do not
> have such a device available to me.
Sure! That's what I planned. I'll probably try to contact other
braille embossers manufacturers to get protocol or even devices. Index
is very common in Europe, so it is good enough for a start.
> How are Braille embossers connected and how do they appear for the computer?
> Do they work with the standard usb/parallel/socket/ipp backends of CUPS?
Yes, they really look like usual printers. Just configuring them as
generic text printers would work for instance. In the case of Index
embossers, they have serial, USB (line-printer interface), and network
(HP JetDirect) support.
Samuel
[-- Attachment #2: cups-braille_0.1.tar.gz --]
[-- Type: application/x-tar-gz, Size: 14272 bytes --]
next prev parent reply other threads:[~2015-12-10 21:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 10:27 [Printing-architecture] Contributing braille embosser support Samuel Thibault
2015-12-09 16:04 ` Michael Sweet
2015-12-10 20:29 ` Till Kamppeter
2015-12-10 20:45 ` Samuel Thibault
2015-12-10 21:02 ` Till Kamppeter
2015-12-10 21:31 ` Samuel Thibault [this message]
2015-12-11 0:19 ` Till Kamppeter
2015-12-11 0:31 ` Samuel Thibault
2015-12-11 1:17 ` Till Kamppeter
2015-12-12 2:28 ` Till Kamppeter
2015-12-12 3:53 ` Till Kamppeter
2015-12-12 8:36 ` Samuel Thibault
2015-12-12 9:50 ` Samuel Thibault
2015-12-12 11:53 ` Till Kamppeter
2015-12-12 12:04 ` Till Kamppeter
2015-12-13 2:40 ` Samuel Thibault
2015-12-13 11:07 ` Till Kamppeter
2015-12-21 0:11 ` Samuel Thibault
2015-12-21 0:12 ` Samuel Thibault
2015-12-21 13:56 ` Till Kamppeter
2015-12-13 18:59 ` Samuel Thibault
2015-12-13 19:42 ` Till Kamppeter
2015-12-12 15:00 ` Till Kamppeter
2016-11-27 18:54 ` Samuel Thibault
2016-11-27 19:22 ` Till Kamppeter
2016-11-29 19:30 ` Samuel Thibault
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151210213147.GK2905@var.home \
--to=samuel.thibault@ens-lyon.org \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=till.kamppeter@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.