From: Michael Sweet <msweet@apple.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: "printing-architecture@lists.linux-foundation.org"
<printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] Contributing braille embosser support
Date: Wed, 09 Dec 2015 11:04:38 -0500 [thread overview]
Message-ID: <2532643D-680A-493C-8A77-9C0CEF5D283E@apple.com> (raw)
In-Reply-To: <20151209102736.GC16751@var.bordeaux.inria.fr>
Samuel,
This is very cool, thank you!
> On Dec 9, 2015, at 5:27 AM, Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:
>
> Hello,
>
> I have been working on braille embosser support for CUPS, so that
> embossing a document can be as easy as printing it. I have attached the
> result.
>
> The principle I have followed is to use the cups architecture to
> separate on one hand frontends which turn documents into braille text
> (text/vnd.cups-brf) or braille graphics (image/vnd.cups-brf), notably
> based on liblouis, and on the other hand backends which emboss braille
> text or braille graphics (I have implemented a generic driver which
> should work on all embossers, and a driver for the Index embosser which
> I can actually test).
>
> For now, I have made a separate package, so it is easy to test it
> already, but ideally, I would like to see this work integrated into CUPS
> filters, so that blind people don't need to install a separate package,
> but just configure CUPS for their embosser. How should we proceed?
> Perhaps first iterate over the packaged version, until the code is fine
> for integration, and then I'll submit a patch against cups-filters?
>
> Samuel
> <cups-braille_0.1.tar.gz>_______________________________________________
> Printing-architecture mailing list
> Printing-architecture@lists.linux-foundation.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.linuxfoundation.org_mailman_listinfo_printing-2Darchitecture&d=BQICAg&c=Hw-EJUFt2_D9PK5csBJ29kRV40HqSDXWTLPyZ6W8u84&r=celVg12QtW5bvoWXWyIdeQ&m=jeSlmoaZFovntwF_U0gp292XY4VsyoMEUfKz0PUGsAg&s=3XIbVXdJdTkphd6bQFfESaGPKGkmo-h4RVOy2MW_slQ&e=
_________________________________________________________
Michael Sweet, Senior Printing System Engineer
next prev parent reply other threads:[~2015-12-09 16:04 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 [this message]
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
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=2532643D-680A-493C-8A77-9C0CEF5D283E@apple.com \
--to=msweet@apple.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=samuel.thibault@ens-lyon.org \
/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.