From: Peter Weilbacher <newsspam@Weilbacher.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Experiences with gtk3-nocsd?
Date: Wed, 30 Sep 2015 23:29:25 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1509302324050.23327@comporellon> (raw)
In-Reply-To: <mufoc4$jvi$1@ger.gmane.org>
On Wed, 30 Sep 2015, Grant Edwards wrote:
> [Actually, I don't recall ever using evince or atril for filling out
> PDF forms -- so that might be another reason I'd have to keep acroread
> around.]
In my experience, at least evince is great with forms! Since that's
provided by the same backend library (I think), atril should be able to
handle them nicely as well. [The only reason to keep acrobat around are
some documents with PDF comments filled out by people on Macs. evince
does not always show all of those.]
Peter.
next prev parent reply other threads:[~2015-09-30 21:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 14:03 [gentoo-user] Experiences with gtk3-nocsd? Grant Edwards
2015-09-29 16:09 ` [gentoo-user] " Grant Edwards
2015-09-30 0:47 ` walt
2015-09-30 1:23 ` Jonathan Callen
2015-09-30 4:27 ` Grant Edwards
2015-09-30 9:45 ` Chris Spackman
2015-09-30 14:08 ` Grant Edwards
2015-09-30 14:21 ` Alan McKinnon
2015-09-30 21:29 ` Peter Weilbacher [this message]
2015-09-30 22:25 ` Grant Edwards
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=alpine.DEB.2.11.1509302324050.23327@comporellon \
--to=newsspam@weilbacher.org \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox