All of lore.kernel.org
 help / color / mirror / Atom feed
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 19:02:03 -0200	[thread overview]
Message-ID: <5669E84B.2090400@gmail.com> (raw)
In-Reply-To: <20151210204505.GJ2905@var.home>

On 12/10/2015 06:45 PM, Samuel Thibault wrote:
> Hello,
>
> Till Kamppeter, on Thu 10 Dec 2015 18:29:40 -0200, wrote:
>> I am looking into integrating it into cups-filters,
>
> Cool :)
>
>> 1. PPD files: If there are different options, like LibLouis2, libLouis3, ...
>> their name translations/long names should also be different,
>
> Sure, easy :)
>
>> 2. Cluttering of /usr/lib/cups/filter/: This directory should only contain
>> the actual CUPS filters
>
>> The auxiliary files should go into a separate directory, like
>> /usr/share/cups/braille/
>
> Sure, easy :)
>
>> 3. Binary bytes in shell scripts: Some scripts, like
>> drivers/index/textbrftoindexv3 contain binary bytes.
>
> Right. I'll use bash's $'\015' then.
>
>> Or do everything in C (this is even better),
>
> I had been wondering about turning these into C indeed, but the shell
> version seems to me easier to read and maintain actually.
>

OK, thanks. So please go ahead with the fixes.

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.

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?

    Till



  reply	other threads:[~2015-12-10 21:02 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 [this message]
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=5669E84B.2090400@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.