[okular] [Bug 169847] split view feature

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=169847

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 377487] Find and List all instances of a searched word

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=377487

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/

[Luigi Toscano]

https://bugs.kde.org/show_bug.cgi?id=267350

Luigi Toscano  changed:

   What|Removed |Added

 CC||luigi.tosc...@tiscali.it

--- Comment #57 from Luigi Toscano  ---
I'm not sure that highlighting the fact that someone is a KDE devleoper here is
a good idea.
If I comment in a bug of a component which I never touched, I'm not sure why
that comment should have some sort of special marking.

That said, we are off-topic here; the place to discuss this is the
kde-community@ mailing list.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=267350

--- Comment #56 from Nate Graham  ---
Definitely a good idea. Technically I'm a KDE developer too even though I don't
have or use a @kde.org email address. Can you file a bug to that effect on
https://bugs.kde.org/enter_bug.cgi?product=bugs.kde.org?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/

[sparhawk]

https://bugs.kde.org/show_bug.cgi?id=267350

--- Comment #55 from sparhawk  ---
> we know it needs improvement and we're working in a fix.

To be fair to the other commenters, we hadn't heard anything here for a few
years, so I presumed that the devs were *not* working on a fix. Sometimes KDE
bugs tend to drift around for a few years before being abruptly closed as
"won't fix", so I can understand why people continue to complain.

Also, I was also unaware that you were even a dev until I mouse-overed your
name and saw the @kde.org email address just then. I guess that's a fault of
this website though; a visible dev tag similar to GitHub would be useful.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 385468] "Missing \"Version=5\", file '/usr/share/kconf_update/okular.upd' will be skipped."

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=385468

Albert Astals Cid  changed:

   What|Removed |Added

 CC||fa...@kde.org,
   ||matt...@mjdsystems.ca

--- Comment #3 from Albert Astals Cid  ---
Adding David and Matthew, i wonder why this extra/weird requirement wasn't
communicated to app developers, how are we supposed to know that you decided to
break the files we ship?

Reading the log all i can find is a weird "This patch is necessary because:   
When we use kf5 + kde4 application" which is a situation we've never supported.

Is there any chance you can revert that misfeature?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=267350

--- Comment #54 from Albert Astals Cid  ---
Please, stop complaining, complaining doesn't do anyone any good, we know it
needs improvement and we're working in a fix.

If you want to get it fixed earlier, either volunteer to help with the fix or
hire someone to fix it faster.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/

[Yuri]

https://bugs.kde.org/show_bug.cgi?id=267350

--- Comment #53 from Yuri  ---
(In reply to Ross Boylan from comment #52)
> I don't want my previous response to be taken as a vote for the status quo. 
> The behavior I would expect is:

Saving form data into the file is the behavior prescribed by pdf specification.
Leaving form files in any other place has so many disadvantages that it doesn't
even make sense to list them.


It's amazing this isn't fixed for 6.5 years now.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/

[Ross Boylan]

https://bugs.kde.org/show_bug.cgi?id=267350

--- Comment #52 from Ross Boylan  ---
I don't want my previous response to be taken as a vote for the status quo. 
The behavior I would expect is:

1. If I don't hit save my work disappears.(*)  The current application does not
have a save function (as distinct from save as), and I'm pretty sure that if I
fill in a form, exit, and then open the form my old values will still be there.
 Worse, if someone else using the same account opens the form, they will see my
info.

2. If I do save (not just save as) my work will be saved with the file.

In this case I might not expect, but would be pleased if 
3. there were an option to save the form data to a separate file and restore it
from a separate file.  I'd guess such a facility is consistent with the 1600
page XFA spec, though I can't say I know where :)

Because the current behavior violates these expectations, it is a security
risk.   Someone's personal information may be exposed in ways unanticipated,
and operations that usually assure security, like not saving a file or deleting
it, will not work.  And operations that are expected to reveal info, like
copying/mailing a pdf or operating on it with a different program, may instead
conceal/disappear the information.

(*) Some usability experts argue that "work disappears if I don't save" is not
the expectation of the lay user, and that our current model of "you must save
to keep your work" is aggravating and unintuitive to them.  That may well be
correct.  But unless the surrounding programs all start behaving this way, this
behavior is undesirable.  An application that may be dealing with sensitive
private information is not the place to pioneer new interface models.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 385458] pdf form remain blank in Bulgarian

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=385458

--- Comment #3 from Albert Astals Cid  ---
I don't understand you.

You have "a" in bulgarian right? Do you mean that if you type "a" it doesn't
work?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/

[Ross Boylan]

https://bugs.kde.org/show_bug.cgi?id=267350

Ross Boylan  changed:

   What|Removed |Added

 CC||ross.boy...@ucsf.edu

--- Comment #51 from Ross Boylan  ---
(In reply to lutz.wrage from comment #50)
> Is there any use case that justifies storing form data in
> ~/.kde/share/apps/okular/docdata/ given that the same data can be stored in
> the pdf itself? 
> It seems to me that there isn't.

While I consider the current behavior undesirable, it does have its advantages.
 In fact, it's the reason I decided to use okular for my taxes.  Here's the use
case:

1. Generate some forms automatically (e.g., opentaxsolver computes my taxes and
fills in government  forms).
2. Resulting forms require some manual tweaks (e.g., check boxes, fill in
additional fields).
3. Discover forms need to be regenerated to correct a mistake.  Modify inputs
and return to 1.

In this scenario, the work in 2 is lost if the results have been stored in the
pdf, but is retained if the values are stored elsewhere, as okular currently
does.  Even if the pdf in 2 is saved under a different name, so that the
results are not literally lost, one must manually identify the changed
information and reenter it.

There is another scenario in which the recreation of the information is less
desirable.  If some of the manually entered information in 2 depends on the
values from 1, e.g., you manually enter line 55 as a copy of line 32 but the
automatically generated line 32 changes, then the previous manual data may be
invalid.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 385423] Okular print dialog doesn't offer "landscape" nor "portrait" options for paper rotation

[LordDan]

https://bugs.kde.org/show_bug.cgi?id=385423

--- Comment #2 from LordDan  ---
(In reply to Albert Astals Cid from comment #1)
> Just to make sure i understand what you want you want to print a landscape
> in portrait so as to have a huge whitespace at the bottom?

Yes, that's right. It means paper economy. More space left = space for printing
another picture (or a copy from the first one), space for annotations etc.
It's always better to offer options  :-)

-- 
You are receiving this mail because:
You are the assignee for the bug.