Am 17.02.2013 13:05, schrieb (Nuno Silva):
> On 2013-02-17, Nilesh Govindrajan wrote:
>> On Feb 17, 2013 3:04 PM, "Yohan Pereira" <[email protected]> wrote:
>>
>>> On 17/02/13 at 02:44pm, Nilesh Govindrajan wrote:
>>>> That's what I did. But I tend to switch browsers too often (chromium and
>>>> Firefox).
>>>> Firefox has a pdf.js addon, doesn't work reliably many times.
>>> If you use KDE try this. You can then use okular(among other things)
>>> in your browsers.
>>>
>>> www-plugins/kpartsplugin
>>> http://www.unix-ag.uni-kl.de/~fischer/kpartsplugin/
>>> Description: Plugin using KDE's KParts technology to embed file
>>> viewers into non-KDE browsers
>> That sounds interesting. Will try it out. Thanks.
>>
>> But nobody replied if Adobe still supports acroread?
> AFAIK there was no annoucement regarding end of life for acroread, so I
> don't see any reason to expect otherwise.
>
> Flash is a separate thing.
>
> But keep in mind that Adobe Acrobat Reader is one of the worst, most
> bloated and most heavy PDF viewers out there. The only thing it may be
> worthy for is some kind of bleeding edge PDF feature libpoppler and the
> like don't have yet.
>
> Also, I actually had to try running it recently. I was trying to print a
> document with annotations -- spoiler: it didn't work, not even with
> acroread, closest I got was generating a postscript file using acroread
> in the commandline after manually hacking the acroread settings to
> enable annotation printing, and even then part of the annotations don't
> show up or are covered, and there's no mapping between annotations and
> their icons. But the interface was *really* slow, almost unusable. I
> wonder why. I possibly overlooked something.
>
biddings need digitally signed pdfs. Easy to create with acroread. Not
so easy with anything else.
And that 'feature' is not arcane nor seldomly used.
