Re: [Okular-devel] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
John McCabe-Dansted posted on Tue, 17 Jan 2012 19:18:58 +0800 as
> On Tue, Jan 17, 2012 at 8:39 AM, Duncan <1i5t5.duncan@xxxxxxx> wrote:
>> Actually, I wonder if this idea could get a bit more traction in view
>> of the new ksecrets thing? That'd play off the whole fascination with
>> the new and shiny technology thing, instead of being seen as the
>> drudge-work that hooking up to kwallet or just implementing an ordinary
>> don't-save option and clear-saved button.
> I think the real solution is to fix poppler so store the annotations in
> the Document according to the PDF standard (and use one of the adhoc
> tricks to store annotations in PS files). This is what every user
> expects, and would allow them to email the PDF, open the PDF in stardard
> PDF readers and annotation software, etc.
>> That's where I'd try to take it at this point, since ksecrets IS new
>> and shiny and fascinating! =:^)
> In other words, not an existing standard for storing PDF annotations :P.
You're probably right, but AFAIK poppler isn't a kde developed library.
So in that case the bug should be RESOLVED/UPSTREAM. Meanwhile, anything
okular could do without that functionality would remain off-standard, and
poppler's lack of the feature might explain why okular did its own
So I guess that's another out for the okular folks if they want to take
it, simply point to upstream, and say they'll consider support for doing
it the standard way once poppler implements the standard functionality
for them to use. Meanwhile, they can continue to handle it how they do
(no change) or possibly do something with ksecrets or the like. But in
view of the standard, were I an okular dev, I'd be hesitant to develop a
whole ksecrets infrastructure, just to tear it out when poppler grew
support for that bit of the standard, which would favor okular keeping
pretty much what it has as it has it, until then. So RESOLVED/UPSTREAM
would seem to be an appropriate solution to the okular bug, at this
point, telling the filer to reopen when upstream supports the standard.
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
More info: http://www.kde.org/faq.html.
[Red Hat Install]
[GIMP for Windows]
[Red Hat Development]