From: Till Kamppeter <till.kamppeter@gmail.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] Contributing braille embosser support
Date: Thu, 10 Dec 2015 18:29:40 -0200 [thread overview]
Message-ID: <5669E0B4.9040009@gmail.com> (raw)
In-Reply-To: <20151209102736.GC16751@var.bordeaux.inria.fr>
Hi,
Thank you very much for this great effort. This is really missing in the
Linux operating system.
I am looking into integrating it into cups-filters, but I would like to
have the following improvements on it:
1. PPD files: If there are different options, like LibLouis2, libLouis3,
... their name translations/long names should also be different, not
having "Additional Braille transcription" for all of them, but rather
"Additional Braille transcription (2)" for LibLouis2, "Additional
Braille transcription (3)" for LibLouis3, ... Otherwise it is rather
confusing having several options showing with the same name in a print
dialog.
2. Cluttering of /usr/lib/cups/filter/: This directory should only
contain the actual CUPS filters (executables called by CUPS in the
filter chain for a job. The auxiliary files should go into a separate
directory, like /usr/share/cups/braille/ (if there are no
architecture-dependent executables or libraries) or
/usr/lib/cups/braille (if there are architecture-dependent executables
or libraries).
3. Binary bytes in shell scripts: Some scripts, like
drivers/index/textbrftoindexv3 contain binary bytes. This leads to
problems with version control systems like GIT or BZR. Please avoid any
binary bytes in scripts or source files, generally in any file contained
in the source tarball. There are ways to express this with pure text. Or
do everything in C (this is even better), there are for sure ways to
avoid binary bytes.
I am grateful if you could fix that.
Till
On 12/09/2015 08:27 AM, Samuel Thibault 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
>
>
>
> _______________________________________________
> Printing-architecture mailing list
> Printing-architecture@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/printing-architecture
>
next prev parent reply other threads:[~2015-12-10 20:29 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 [this message]
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=5669E0B4.9040009@gmail.com \
--to=till.kamppeter@gmail.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.