All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Samuel Thibault <sthibault@debian.org>,
	Debian-printing@lists.debian.org,
	printing-architecture@lists.linux-foundation.org,
	Adam Chester <adam.chester@pentest.co.uk>,
	Yann Soubeyrand <yann-externe.soubeyrand@edf.fr>
Subject: Re: [Printing-architecture] documents and braille [Was: cups-filters 1.4.0 released!]
Date: Mon, 21 Dec 2015 10:47:27 -0200	[thread overview]
Message-ID: <5677F4DF.6080601@gmail.com> (raw)
In-Reply-To: <20151220235820.GU4287@var.home>

On 12/20/2015 09:58 PM, Samuel Thibault wrote:
> Hello,
>
> Till Kamppeter, on Mon 14 Dec 2015 23:02:48 -0200, wrote:
>> Applications usually send only PDF when printing, CUPS usually
>> accepts also images and plain text which is also covered by these.
>
> I'm wondering about this.  Ideally the scenario that should work is:
>
> - user opens a libreoffice document
> - user prints to an ink printer
>    - that sends a PDF to cups, which prints it
> - user prints to an embosser with "ink" formatting option enabled
>    - that sends the .pdf file to cups, which uses filters to turn each of
>      its page into braille.
> - user prints to an embosser with "braille" formatting option enabled
>    - that sends the .odt file to cups, which uses filters to turn that
>      into nicely-formatted braille.
>
> This would be really useful to happen this way, notably because since
> braille takes a lot of room, page numbers are completely different
> between ink document and embossed document.
>
> In some cases the user may want to get an exact equivalent to what would
> be printed on an "ink" printer so as to be able to discuss about it
> with other people, i.e. the page references are the same, etc. So going
> through the PDF is what is expected here.
>
> In other cases the user wants his own document, with page numbers which
> follow the braille formatting, footnotes printed on the same braille
> page, etc. In that case, we really want the odt to be sent to CUPS for
> processing by filters.
>
> Is it possible to have such option between libreoffice and CUPS?

First, I would not call the two modes "ink" and "braille", but something 
like "Original layout" and "Braille-optimized layout".

Second, LibreOffice does not send .odt files when clicking "Print" in 
the print dialog. By default it sends PDF, and in the settings you can 
switch it to PostScript, but there is always one of these two formats 
selected for all printers.

At least the PDF sent by LibreOffice is not a bitmap of each page, but 
it contains the (searchable) text and instructions for formatting and 
layout (high-level/vector graphics), similar to what the .odt file 
contains. So it should be possible to extract the text and formatting 
and re-arrange it for the Braille output (as e-book readers can do it 
with PDFs or the "reflow" mode of the Adobe Reader on Android).

I also doubt whether the LibreOffice developers would implement a 
feature request of sending print data in .odt format, but I would rather 
believe in that they would implement a feature request in giving 
optimizing options for the PDF of the print output, for example for 
e-book reader/braille embosser text-reflow-friendliness.

    Till


       reply	other threads:[~2015-12-21 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <566F564D.9040000@gmail.com>
     [not found] ` <20151215000648.GK2967@var.home>
     [not found]   ` <566F66B8.4060106@gmail.com>
     [not found]     ` <20151220235820.GU4287@var.home>
2015-12-21 12:47       ` Till Kamppeter [this message]
2015-12-21 14:25         ` [Printing-architecture] documents and braille [Was: cups-filters 1.4.0 released!] 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=5677F4DF.6080601@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=Debian-printing@lists.debian.org \
    --cc=adam.chester@pentest.co.uk \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=sthibault@debian.org \
    --cc=yann-externe.soubeyrand@edf.fr \
    /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.