<div dir="ltr"><div dir="ltr">> As Laura described yes, as you described it no.<br>><br>> Okular is not a file management system, you use git or whatever other tool for<br>> that, keeping N old copies of the same file makes no sense.<br>><br>> Cheers,<br>> Albert<br></div><p>I agree with your decision and can implement Laura's idea. </p><p>Could you please let me know how to contribute to this feature? </p><p>I am not familiar with KDE policies.</p><p>Thank you.</p><div><br></div><div>Best,</div><div>Wen<br><div class="gmail_quote"><div dir="ltr" class="gmail_attr"><<a href="mailto:okular-devel-request@kde.org">okular-devel-request@kde.org</a>> 於 2024年7月24日 週三 下午5:07寫道：<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send Okular-devel mailing list submissions to<br>
<a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://mail.kde.org/mailman/listinfo/okular-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/okular-devel</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:okular-devel-request@kde.org" target="_blank">okular-devel-request@kde.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:okular-devel-owner@kde.org" target="_blank">okular-devel-owner@kde.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Okular-devel digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Add autosave function to Okular (Albert Astals Cid)<br>
2. Re: Add possibility to adjust the font size for PDF form<br>
filling (Albert Astals Cid)<br>
3. [okular] [Bug 490714] The program is not restored from a<br>
saved session after another update. (Albert Astals Cid)<br>
4. Re: Add possibility to adjust the font size for PDF form<br>
filling (Andy Sardina)<br>
5. [okular] [Bug 490714] The program is not restored from a<br>
saved session after another update. (Adrian Carver)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 23 Jul 2024 23:50:13 +0200<br>
From: Albert Astals Cid <<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>><br>
To: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
Subject: Re: Add autosave function to Okular<br>
Message-ID: <15943638.68RGZT8oEa@xps15><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
El dilluns, 22 de juliol del 2024, a les 7:28:12 (CEST), Wen Chang va <br>
escriure:<br>
> > Exactly, auto save is just not how desktop software generally works.<br>
> > <br>
> > Cheers,<br>
> > <br>
> > Albert<br>
> <br>
> Could we implement the backup method for Okular?<br>
<br>
As Laura described yes, as you described it no.<br>
<br>
Okular is not a file management system, you use git or whatever other tool for <br>
that, keeping N old copies of the same file makes no sense.<br>
<br>
Cheers,<br>
Albert<br>
<br>
> <br>
> Best,<br>
> Wen<br>
> <<a href="mailto:okular-devel-request@kde.org" target="_blank">okular-devel-request@kde.org</a>> 於 2024年7月18日 週四 下午7:00寫道：<br>
> <br>
> > Send Okular-devel mailing list submissions to<br>
> > <br>
> > <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
> > <br>
> > To subscribe or unsubscribe via the World Wide Web, visit<br>
> > <br>
> > <a href="https://mail.kde.org/mailman/listinfo/okular-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/okular-devel</a><br>
> > <br>
> > or, via email, send a message with subject or body 'help' to<br>
> > <br>
> > <a href="mailto:okular-devel-request@kde.org" target="_blank">okular-devel-request@kde.org</a><br>
> > <br>
> > You can reach the person managing the list at<br>
> > <br>
> > <a href="mailto:okular-devel-owner@kde.org" target="_blank">okular-devel-owner@kde.org</a><br>
> > <br>
> > When replying, please edit your Subject line so it is more specific<br>
> > than "Re: Contents of Okular-devel digest..."<br>
> > <br>
> > Today's Topics:<br>
> > 1. [okular] [Bug 490337] Allow to get PDF passwords from a<br>
> > <br>
> > org.freedesktop.secrets service (yan12125)<br>
> > <br>
> > 2. [okular] [Bug 490337] Allow to get PDF passwords from a<br>
> > <br>
> > org.freedesktop.secrets service (Albert Astals Cid)<br>
> > <br>
> > 3. Re: Add autosave function to Okular (Albert Astals Cid)<br>
> > 4. Re: Add autosave function to Okular (Wen Chang)<br>
> > 5. [okular] [Bug 490435] New: printing from the selected range<br>
> > <br>
> > of pages does not work correctly (Nazar)<br>
> > <br>
> > ----------------------------------------------------------------------<br>
> > <br>
> > Message: 1<br>
> > Date: Wed, 17 Jul 2024 13:59:53 +0000<br>
> > From: yan12125 <<a href="mailto:bugzilla_noreply@kde.org" target="_blank">bugzilla_noreply@kde.org</a>><br>
> > To: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
> > Subject: [okular] [Bug 490337] Allow to get PDF passwords from a<br>
> > <br>
> > org.freedesktop.secrets service<br>
> > <br>
> > Message-ID: <<a href="http://bug-490337-85596-IgPGCqe1St@http.bugs.kde.org/" rel="noreferrer" target="_blank">bug-490337-85596-IgPGCqe1St@http.bugs.kde.org/</a>><br>
> > Content-Type: text/plain; charset=UTF-8<br>
> > <br>
> > <a href="https://bugs.kde.org/show_bug.cgi?id=490337" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=490337</a><br>
> > <br>
> > --- Comment #2 from yan12125 <<a href="mailto:yu3actxt2tttfimx@chyen.cc" target="_blank">yu3actxt2tttfimx@chyen.cc</a>> ---<br>
> > Ah, I forgot the main point: I use neither KDE nor kwalletd. Instead, I<br>
> > use<br>
> > KeePassXC as a cross-platform solution to manage all my secrets. That<br>
> > program<br>
> > also provides org.freedesktop.secrets service like kwalletd. If Okular<br>
> > supports<br>
> > org.freedesktop.secrets, I can just use KeePassXC instead of setting up<br>
> > another<br>
> > secrets service for PDF passwords.<br>
> > <br>
> > --<br>
> > You are receiving this mail because:<br>
> > You are the assignee for the bug.<br>
> > <br>
> > ------------------------------<br>
> > <br>
> > Message: 2<br>
> > Date: Wed, 17 Jul 2024 20:19:56 +0000<br>
> > From: "Albert Astals Cid" <<a href="mailto:bugzilla_noreply@kde.org" target="_blank">bugzilla_noreply@kde.org</a>><br>
> > To: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
> > Subject: [okular] [Bug 490337] Allow to get PDF passwords from a<br>
> > <br>
> > org.freedesktop.secrets service<br>
> > <br>
> > Message-ID: <<a href="http://bug-490337-85596-yNCrJ0qU5B@http.bugs.kde.org/" rel="noreferrer" target="_blank">bug-490337-85596-yNCrJ0qU5B@http.bugs.kde.org/</a>><br>
> > Content-Type: text/plain; charset=UTF-8<br>
> > <br>
> > <a href="https://bugs.kde.org/show_bug.cgi?id=490337" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=490337</a><br>
> > <br>
> > --- Comment #3 from Albert Astals Cid <<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>> ---<br>
> > Ok, i guess that makes some sense, I wouldnt' be against such feature.<br>
> > <br>
> > --<br>
> > You are receiving this mail because:<br>
> > You are the assignee for the bug.<br>
> > <br>
> > ------------------------------<br>
> > <br>
> > Message: 3<br>
> > Date: Wed, 17 Jul 2024 23:22:41 +0200<br>
> > From: Albert Astals Cid <<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>><br>
> > To: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
> > Subject: Re: Add autosave function to Okular<br>
> > Message-ID: <2416547.6LXrqp22Eu@xps15><br>
> > Content-Type: text/plain; charset="utf-8"<br>
> > <br>
> > El dimecres, 17 de juliol del 2024, a les 7:26:20 (CEST), Laura David<br>
> > Hurka va<br>
> > <br>
> > escriure:<br>
> > > On Wed, 17 Jul 2024 11:01:53 +0800 Wen Chang wrote:<br>
> > > > I can do it that way by saving the changes in a backup file.<br>
> > > > <br>
> > > > I would like to know why modifying the file on disk without user<br>
> > > > interaction is a bad idea based on your experience.<br>
> > > > <br>
> > > > Also, I noticed that VSCode automatically saves changes once they are<br>
> > > > made.<br>
> > > > To my knowledge, only the file that the user is working on will be<br>
> > > > modified.<br>
> > > > <br>
> > > > What drawbacks would there be if a file is directly modified without<br>
> > <br>
> > user<br>
> > <br>
> > > > interaction?<br>
> > > <br>
> > > Drawback would be that it is unusual and unexpected for many users<br>
> > <br>
> > (unless<br>
> > <br>
> > > the user explicitly configured it that way).<br>
> > > <br>
> > > Imagine you have a form that you need to fill out often, and then just<br>
> > <br>
> > print<br>
> > <br>
> > > once.<br>
> > > If changes are saved automatically, you can’t use the file the next time<br>
> > > anymore, because it is already filled.<br>
> > > <br>
> > > It would also not make much sense with “Open...”, “Save”, and “Save<br>
> > <br>
> > As...”.<br>
> > <br>
> > Exactly, auto save is just not how desktop software generally works.<br>
> > <br>
> > Cheers,<br>
> > <br>
> > Albert<br>
> > <br>
> > > Laura<br>
> > <br>
> > ------------------------------<br>
> > <br>
> > Message: 4<br>
> > Date: Thu, 18 Jul 2024 11:28:31 +0800<br>
> > From: Wen Chang <<a href="mailto:changyaowen19980629@gmail.com" target="_blank">changyaowen19980629@gmail.com</a>><br>
> > To: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
> > Subject: Re: Add autosave function to Okular<br>
> > <br>
> > Message-ID:<br>
> > <<br>
> > <br>
> > <a href="mailto:CAKPy6qvpTJeYnfT6v_qB0pB1TJEpkUE8gProHN-mrGxEz_rA9w@mail.gmail.com" target="_blank">CAKPy6qvpTJeYnfT6v_qB0pB1TJEpkUE8gProHN-mrGxEz_rA9w@mail.gmail.com</a>><br>
> > Content-Type: text/plain; charset="utf-8"<br>
> > <br>
> > That's indeed the concern of the autosave method.<br>
> > Thanks for letting me know.<br>
> > <br>
> > About your concern, I provide my suggestion as follows:<br>
> > > Drawback would be that it is unusual and unexpected for many users<br>
> > <br>
> > (unless the<br>
> > <br>
> > > user explicitly configured it that way).<br>
> > <br>
> > The autosave function is disabled by default. Once the user clicks the<br>
> > button to turn it on, changes will be saved automatically. This ensures<br>
> > that users are aware they are in autosave mode. Additionally, autosave<br>
> > will<br>
> > remain enabled the next time the user opens Okular.<br>
> > <br>
> > Does implementing the method this way make more sense? Feel free to let me<br>
> > know.<br>
> > <br>
> > > If changes are saved automatically, you can’t use the file the next time<br>
> > > anymore, because it is already filled.<br>
> > <br>
> > In this situation, I suggest saving a backup file whenever the user closes<br>
> > Okular. This would create a list of backup files in a folder located in<br>
> > the<br>
> > same directory as the document. Users would then be able to roll back by<br>
> > checking different versions of the backup files.<br>
> > <br>
> > To my understanding, the current policy in Okular does not allow users to<br>
> > revert to the original version of a file once they have saved it manually,<br>
> > right? Please correct me if I am mistaken. Thanks.<br>
> > <br>
> > Best,<br>
> > Wen<br>
> > <<a href="mailto:okular-devel-request@kde.org" target="_blank">okular-devel-request@kde.org</a>> 於 2024年7月17日 週三 下午7:00寫道：<br>
> > <br>
> > > Send Okular-devel mailing list submissions to<br>
> > > <br>
> > > <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
> > > <br>
> > > To subscribe or unsubscribe via the World Wide Web, visit<br>
> > > <br>
> > > <a href="https://mail.kde.org/mailman/listinfo/okular-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/okular-devel</a><br>
> > > <br>
> > > or, via email, send a message with subject or body 'help' to<br>
> > > <br>
> > > <a href="mailto:okular-devel-request@kde.org" target="_blank">okular-devel-request@kde.org</a><br>
> > > <br>
> > > You can reach the person managing the list at<br>
> > > <br>
> > > <a href="mailto:okular-devel-owner@kde.org" target="_blank">okular-devel-owner@kde.org</a><br>
> > > <br>
> > > When replying, please edit your Subject line so it is more specific<br>
> > > than "Re: Contents of Okular-devel digest..."<br>
> > > <br>
> > > Today's Topics:<br>
> > > 1. Re: Add autosave function to Okular (Laura David Hurka)<br>
> > > <br>
> > > ----------------------------------------------------------------------<br>
> > > <br>
> > > Message: 1<br>
> > > Date: Wed, 17 Jul 2024 07:26:20 +0200<br>
> > > From: Laura David Hurka <<a href="mailto:laura.stern@mailbox.org" target="_blank">laura.stern@mailbox.org</a>><br>
> > > To: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
> > > Subject: Re: Add autosave function to Okular<br>
> > > Message-ID: <6009722.DvuYhMxLoT@doro><br>
> > > Content-Type: text/plain; charset="utf-8"<br>
> > > <br>
> > > On Wed, 17 Jul 2024 11:01:53 +0800 Wen Chang wrote:<br>
> > > > I can do it that way by saving the changes in a backup file.<br>
> > > > <br>
> > > > I would like to know why modifying the file on disk without user<br>
> > > > interaction is a bad idea based on your experience.<br>
> > > > <br>
> > > > Also, I noticed that VSCode automatically saves changes once they are<br>
> > > <br>
> > > made.<br>
> > > <br>
> > > > To my knowledge, only the file that the user is working on will be<br>
> > > <br>
> > > modified.<br>
> > > <br>
> > > > What drawbacks would there be if a file is directly modified without<br>
> > <br>
> > user<br>
> > <br>
> > > > interaction?<br>
> > > <br>
> > > Drawback would be that it is unusual and unexpected for many users<br>
> > <br>
> > (unless<br>
> > <br>
> > > the<br>
> > > user explicitly configured it that way).<br>
> > > <br>
> > > Imagine you have a form that you need to fill out often, and then just<br>
> > > print<br>
> > > once.<br>
> > > If changes are saved automatically, you can’t use the file the next time<br>
> > > anymore, because it is already filled.<br>
> > > <br>
> > > It would also not make much sense with “Open...”, “Save”, and “Save<br>
> > <br>
> > As...”.<br>
> > <br>
> > > Laura<br>
> > > <br>
> > > <br>
> > > <br>
> > > <br>
> > > ------------------------------<br>
> > > <br>
> > > Subject: Digest Footer<br>
> > > <br>
> > > _______________________________________________<br>
> > > Okular-devel mailing list<br>
> > > <a href="mailto:Okular-devel@kde.org" target="_blank">Okular-devel@kde.org</a><br>
> > > <a href="https://mail.kde.org/mailman/listinfo/okular-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/okular-devel</a><br>
> > > <br>
> > > <br>
> > > ------------------------------<br>
> > > <br>
> > > End of Okular-devel Digest, Vol 214, Issue 22<br>
> > > *********************************************<br>
> > <br>
> > -------------- next part --------------<br>
> > An HTML attachment was scrubbed...<br>
> > URL: <<br>
> > <a href="http://mail.kde.org/pipermail/okular-devel/attachments/20240718/0caf1ab8/a" rel="noreferrer" target="_blank">http://mail.kde.org/pipermail/okular-devel/attachments/20240718/0caf1ab8/a</a><br>
> > ttachment-0001.htm<br>
> > <br>
> > <br>
> > ------------------------------<br>
> > <br>
> > Message: 5<br>
> > Date: Thu, 18 Jul 2024 07:21:26 +0000<br>
> > From: Nazar <<a href="mailto:bugzilla_noreply@kde.org" target="_blank">bugzilla_noreply@kde.org</a>><br>
> > To: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
> > Subject: [okular] [Bug 490435] New: printing from the selected range<br>
> > <br>
> > of pages does not work correctly<br>
> > <br>
> > Message-ID: <<a href="http://bug-490435-85596@http.bugs.kde.org/" rel="noreferrer" target="_blank">bug-490435-85596@http.bugs.kde.org/</a>><br>
> > Content-Type: text/plain; charset=UTF-8<br>
> > <br>
> > <a href="https://bugs.kde.org/show_bug.cgi?id=490435" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=490435</a><br>
> > <br>
> > Bug ID: 490435<br>
> > <br>
> > Summary: printing from the selected range of pages does not<br>
> > <br>
> > work correctly<br>
> > <br>
> > Classification: Applications<br>
> > <br>
> > Product: okular<br>
> > Version: 23.08.1<br>
> > <br>
> > Platform: Microsoft Windows<br>
> > <br>
> > OS: Other<br>
> > <br>
> > Status: REPORTED<br>
> > <br>
> > Severity: normal<br>
> > Priority: NOR<br>
> > <br>
> > Component: printing<br>
> > <br>
> > Assignee: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
> > Reporter: <a href="mailto:nazar2692@gmail.com" target="_blank">nazar2692@gmail.com</a><br>
> > <br>
> > Target Milestone: ---<br>
> > <br>
> > SUMMARY<br>
> > printing from the selected range of pages does not work correctly<br>
> > <br>
> > STEPS TO REPRODUCE<br>
> > 1. File<br>
> > 2. Printing<br>
> > 3. Pages: page range 1,3,5<br>
> > 4. Button - Print<br>
> > <br>
> > OBSERVED RESULT<br>
> > prints only the currently displayed page, rather than the selected page<br>
> > range<br>
> > <br>
> > EXPECTED RESULT<br>
> > <br>
> > <br>
> > SOFTWARE/OS VERSIONS<br>
> > Windows: Windows 11 Home<br>
> > macOS:<br>
> > Linux/KDE Plasma:<br>
> > (available in About System)<br>
> > KDE Plasma Version:<br>
> > KDE Frameworks Version: 5.109.0<br>
> > Qt Version: 5.15.10<br>
> > <br>
> > ADDITIONAL INFORMATION<br>
> > <br>
> > --<br>
> > You are receiving this mail because:<br>
> > You are the assignee for the bug.<br>
> > <br>
> > ------------------------------<br>
> > <br>
> > Subject: Digest Footer<br>
> > <br>
> > _______________________________________________<br>
> > Okular-devel mailing list<br>
> > <a href="mailto:Okular-devel@kde.org" target="_blank">Okular-devel@kde.org</a><br>
> > <a href="https://mail.kde.org/mailman/listinfo/okular-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/okular-devel</a><br>
> > <br>
> > <br>
> > ------------------------------<br>
> > <br>
> > End of Okular-devel Digest, Vol 214, Issue 23<br>
> > *********************************************<br>
<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 24 Jul 2024 00:11:23 +0200<br>
From: Albert Astals Cid <<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>><br>
To: Okular development <<a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a>><br>
Subject: Re: Add possibility to adjust the font size for PDF form<br>
filling<br>
Message-ID: <23268509.iS4c0tQboZ@xps15><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
El dimarts, 23 de juliol del 2024, a les 12:46:59 (CEST), Andy Sardina va <br>
escriure:<br>
> Hi,<br>
> <br>
> I have used Okular recently to fill a PDF form and I haven't found a way<br>
> (in the UI) to adjust the font size for text fields. This is a problem<br>
> because for some text fields, specially the ones where one has to write an<br>
> address, even if the text fits perfectly in the Okular::FormLineEdit, when<br>
> it gets rendered, the text could be cut.<br>
> <br>
> For example:<br>
> <br>
> [image: form-show.png]<br>
> <br>
> but when the form is hidden:<br>
> <br>
> [image: form-hidden.png]<br>
> <br>
> The problem seems to be that the font (and font size) for the<br>
> Okular::FormLineEdit is different from the one in the Default Appearance<br>
> (DA) in the PDF.<br>
> <br>
> My proposal is to take advantage of the method<br>
> Poppler::FormFieldText::setTextFontSize to adjust the font size in<br>
> the PopplerFormFieldText (Poppler Generator).<br>
> <br>
> Ideally, Poppler::FormFieldText could have a member function that returns a<br>
> pointer (to avoid duplicating the same object if many text files share the<br>
> same font) to<br>
> the font defined in the DA (implies changes in Poppler itself). This font<br>
> can then be used on the constructor of Okular::FormLineEdit to "sync" both<br>
> fonts.<br>
> <br>
> What do you think? Is this a change that could be accepted?<br>
<br>
Setting the font & font size is possibly a valid feature, we do that already <br>
for annotations so i don't see why we would not do it for Forms.<br>
<br>
What you suggest of sharing pointers between poppler and okular, that's <br>
possibly a bad idea.<br>
<br>
Cheers,<br>
Albert<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 23 Jul 2024 22:14:38 +0000<br>
From: "Albert Astals Cid" <<a href="mailto:bugzilla_noreply@kde.org" target="_blank">bugzilla_noreply@kde.org</a>><br>
To: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
Subject: [okular] [Bug 490714] The program is not restored from a<br>
saved session after another update.<br>
Message-ID: <<a href="http://bug-490714-85596-AMyCNgARf4@http.bugs.kde.org/" rel="noreferrer" target="_blank">bug-490714-85596-AMyCNgARf4@http.bugs.kde.org/</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
<a href="https://bugs.kde.org/show_bug.cgi?id=490714" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=490714</a><br>
<br>
Albert Astals Cid <<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>> changed:<br>
<br>
What |Removed |Added<br>
----------------------------------------------------------------------------<br>
Severity|major |normal<br>
CC| |<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a><br>
<br>
--- Comment #1 from Albert Astals Cid <<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>> ---<br>
It is also tiresome that you decided your report important is "major" instead<br>
of "normal", it's not.<br>
<br>
I don't even know what you are reporting.<br>
<br>
Are you reporting that saving a session doesn't work? That would be a Plasma<br>
bug, not an Okular bug.<br>
<br>
Are you wishing Okular had its own session concept? That's not even a bug,<br>
that'd be a wish.<br>
<br>
-- <br>
You are receiving this mail because:<br>
You are the assignee for the bug.<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 24 Jul 2024 10:35:05 +0300<br>
From: Andy Sardina <<a href="mailto:andysardina22@gmail.com" target="_blank">andysardina22@gmail.com</a>><br>
To: Okular development <<a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a>><br>
Subject: Re: Add possibility to adjust the font size for PDF form<br>
filling<br>
Message-ID:<br>
<CA+mZVhT-iJtQ0wDLFomCaxdGG=<a href="mailto:7oL40yFanK6cwp8k-4o75FNw@mail.gmail.com" target="_blank">7oL40yFanK6cwp8k-4o75FNw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Cool!<br>
<br>
I’ll work on a PR and avoid sharing pointers between the two levels.<br>
<br>
On Wed, 24 Jul 2024 at 1:11 AM Albert Astals Cid <<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>> wrote:<br>
<br>
> El dimarts, 23 de juliol del 2024, a les 12:46:59 (CEST), Andy Sardina va<br>
> escriure:<br>
> > Hi,<br>
> ><br>
> > I have used Okular recently to fill a PDF form and I haven't found a<br>
> way<br>
> > (in the UI) to adjust the font size for text fields. This is a problem<br>
> > because for some text fields, specially the ones where one has to write<br>
> an<br>
> > address, even if the text fits perfectly in the Okular::FormLineEdit,<br>
> when<br>
> > it gets rendered, the text could be cut.<br>
> ><br>
> > For example:<br>
> ><br>
> > [image: form-show.png]<br>
> ><br>
> > but when the form is hidden:<br>
> ><br>
> > [image: form-hidden.png]<br>
> ><br>
> > The problem seems to be that the font (and font size) for the<br>
> > Okular::FormLineEdit is different from the one in the Default Appearance<br>
> > (DA) in the PDF.<br>
> ><br>
> > My proposal is to take advantage of the method<br>
> > Poppler::FormFieldText::setTextFontSize to adjust the font size in<br>
> > the PopplerFormFieldText (Poppler Generator).<br>
> ><br>
> > Ideally, Poppler::FormFieldText could have a member function that<br>
> returns a<br>
> > pointer (to avoid duplicating the same object if many text files share<br>
> the<br>
> > same font) to<br>
> > the font defined in the DA (implies changes in Poppler itself). This font<br>
> > can then be used on the constructor of Okular::FormLineEdit to "sync"<br>
> both<br>
> > fonts.<br>
> ><br>
> > What do you think? Is this a change that could be accepted?<br>
><br>
> Setting the font & font size is possibly a valid feature, we do that<br>
> already<br>
> for annotations so i don't see why we would not do it for Forms.<br>
><br>
> What you suggest of sharing pointers between poppler and okular, that's<br>
> possibly a bad idea.<br>
><br>
> Cheers,<br>
> Albert<br>
><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://mail.kde.org/pipermail/okular-devel/attachments/20240724/ae3724b6/attachment-0001.htm" rel="noreferrer" target="_blank">http://mail.kde.org/pipermail/okular-devel/attachments/20240724/ae3724b6/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 24 Jul 2024 09:06:56 +0000<br>
From: "Adrian Carver" <<a href="mailto:bugzilla_noreply@kde.org" target="_blank">bugzilla_noreply@kde.org</a>><br>
To: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
Subject: [okular] [Bug 490714] The program is not restored from a<br>
saved session after another update.<br>
Message-ID: <<a href="http://bug-490714-85596-5hEMAl5AzD@http.bugs.kde.org/" rel="noreferrer" target="_blank">bug-490714-85596-5hEMAl5AzD@http.bugs.kde.org/</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
<a href="https://bugs.kde.org/show_bug.cgi?id=490714" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=490714</a><br>
<br>
--- Comment #2 from Adrian Carver <<a href="mailto:adrian.carver@yandex.ru" target="_blank">adrian.carver@yandex.ru</a>> ---<br>
(In reply to Albert Astals Cid from comment #1)<br>
<br>
Albert, if you don't understand something, you can always ask clarifying<br>
questions to the authors of the two “brilliant” ideas: the one who decided that<br>
the idea of redirecting a KDE user to the project's internal bug tracker with<br>
mandatory registration there was a very good idea. The second person who can<br>
explain to you what's going on is the one who, after the first one, decided not<br>
to create a sane registration form with a short introductory FAQ on how to use<br>
this bug tracker, sincerely hoping in his heart that an ordinary user wouldn't<br>
register here.<br>
<br>
I wouldn't, if I hadn't once again started to be annoyed by the non-obvious<br>
behavior of the system and its separate component - ocular. I clicked on the<br>
“Report a bug...” menu and wrote it down as best I could. Where to redistribute<br>
it - to bugs, non-critical bugs, wishes...in general, this is the job of<br>
“moderator”, I assume yours. To me, this kind of behavior is critical in use.<br>
Well, no one has explicitly familiarized me with what the statuses in your<br>
tracker mean.<br>
<br>
At the same time, you can start a couple of tasks to finalize the registration<br>
form on the basis of the above: the situation shows that it will be useful.<br>
<br>
-- <br>
You are receiving this mail because:<br>
You are the assignee for the bug.<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Okular-devel mailing list<br>
<a href="mailto:Okular-devel@kde.org" target="_blank">Okular-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/okular-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/okular-devel</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Okular-devel Digest, Vol 214, Issue 28<br>
*********************************************<br>
</blockquote></div></div></div>