From: Till Kamppeter <till.kamppeter@gmail.com>
To: Michael Sweet <msweet@apple.com>
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>
Subject: [Printing-architecture] What should the "landscape" and "orientation-requested" options exactly do?
Date: Thu, 05 Dec 2013 23:44:36 +0100 [thread overview]
Message-ID: <52A101D4.40107@gmail.com> (raw)
Hi,
I got the following bug report on Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1243484
a user complais that when he sends a job with the "landscape" option it
does not come out correctly.
Now I want to know exactly what "landscape" and "orientation-requested"
should do exactly, to fix cups-filters.
There is some discussion in the bug report and following RFC 2911 I come
to the conclusion that PDF files and also PostScript files which come
from apps as a print job have their layout and page geometry already
determined by the app and so a filter like pdftopdf should ignore
"landscape" and "orientation-requested". For PostScript files (filters
pstopdf and pstops) the given "PageSize", "landscape", and
"orientation-requested" settings should only be used as default for
pages without geometry definition (like the old PostScript CUPS test
page) and be ignored by pages which already come with complete geometry
info (like pages of a usual print job from an app). Filters for text and
image jobs (texttopdf, imagetopdf) should use "landscape" and
"orientation-requested" for the layout of the output.
Am I correct?
Till
next reply other threads:[~2013-12-05 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 22:44 Till Kamppeter [this message]
2013-12-06 23:01 ` [Printing-architecture] What should the "landscape" and "orientation-requested" options exactly do? Tobias Hoffmann
2013-12-09 15:55 ` Michael Sweet
2013-12-09 16:32 ` Till Kamppeter
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=52A101D4.40107@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=msweet@apple.com \
--cc=printing-architecture@lists.linux-foundation.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.