Bug 482363

please attach a file where you're having this problem.

(In reply to Albert Astals Cid from comment #1)
> please attach a file where you're having this problem.
I can't share the document as it has private content, but I have captured the screen shot in the attached document, compared to "Foxit Reader".


However, I have discovered that the problem lies in the "type" of checkbox. The ones containing an "X" are always displayed without problems by Okular. The ones containing the "✓" symbol are the ones that Okular does not display until you enter edit mode.

Created attachment 166428 [details]
Screenshots

Without a file we can-t fix the bug, because all the files we have work.

Please reopen the bug when you find a file you can share that fails

I am sorry it is not enough. The bug exists and I took the time to document it, but I can't keep looking for ways to recreate it, as I don't know with which tools to create such files. 

Closing the thread does not seem adequate or appropriate, but I think it should be up to you - based on the information provided - to find out which word processor generates such peculiar checkboxes.

Best regards

You can find the word processor that generated your particular document by looking at "File -> Properties".

Following your instructions, I have found that they have used "PDFCreator 2.4.1.13" to create the PDF, so I get the impression that they must be using an old version of "MSWord" or, less likely, are unaware of the "Convert to PDF" function of their word processor (they can only be using either MSOffice or OpenOffice/LibreOffice, which are "official" in the company).

I took some additional time to check browsers internal PDF reader. "EDGE" (for Linux), "Chrome" and "Chromium" all them shows right marked checkboxes with symbol "✓". "Firefox" too, but shows an "✕" symbol instead.

To make sure it's not my computer and not to waste anyone's time, I even checked on a computer also running openSUSE but outdated, if Okular behaves the same, and it does. On that PC "Okular" is version 21.08.3.

Any other thing I can do, please, aks me.

Thanks

Do you have access to Adobe professional? Then you could try to strip the problematic of all the confidential parts.  Really, the/a file is needed to fix this.

 Before I opened this thread, I tried to delete private information with LibreOffice Draw, but the form is lost, so it didn't work. As it is more complex than using Adobe tools, I remembered that there is "Master PDF" which is multiplatform and, although it adds a watermark, it works perfectly for this case.

Now I will attach the file with just those checkboxes. I have already checked that the problem remains despite having altered the document with "Master PDF".

Best regards

Created attachment 166472 [details]
Only the checkboxes

Is this maybe a font issue?  Because I do see the checkmark in the box even with disabled 'forms' mode.

might be a fonts issue, works fine here too.

Can you attach a screenshot of files->properties->fonts?

Created attachment 166556 [details]
Fonts

The PDF doesn't embed all fonts, which may lead to problems. In fact in this case the gyre font is used for symbols, and that font has been a source of issues:

https://bugs.kde.org/show_bug.cgi?id=332595
https://bugs.kde.org/show_bug.cgi?id=399107
https://bugs.kde.org/show_bug.cgi?id=423914
https://bugs.kde.org/show_bug.cgi?id=431012
https://bugs.kde.org/show_bug.cgi?id=441623

However, why does it show the character in "form mode"? Furthermore, I understand that the correct thing to do in these cases would be to apply the same solution that the PDF readers that are built into web browsers use. Shouldn't this thread be reopened so that the problem can be solved?

(In reply to Rafael Linux User from comment #13)
> Created attachment 166556 [details]
> Fonts

Next time send the attachment of the document we have not the one you have ;)

(In reply to Luigi Toscano from comment #14)
> The PDF doesn't embed all fonts, which may lead to problems. In fact in this
> case the gyre font is used for symbols, and that font has been a source of
> issues:
> 
> https://bugs.kde.org/show_bug.cgi?id=332595
> https://bugs.kde.org/show_bug.cgi?id=399107
> https://bugs.kde.org/show_bug.cgi?id=423914
> https://bugs.kde.org/show_bug.cgi?id=431012
> https://bugs.kde.org/show_bug.cgi?id=441623

I don't think it's the gyre font, but the ZapfDingbats font, since he says he can reproduce the problem with the modified file he gave us and there ZapfDingbats is the only one that is not embedded

(In reply to Rafael Linux User from comment #15)
> However, why does it show the character in "form mode"? Furthermore, I
> understand that the correct thing to do in these cases would be to apply the
> same solution that the PDF readers that are built into web browsers use.
> Shouldn't this thread be reopened so that the problem can be solved?

This is not a bug, your system is wrongly configured, we are asking for the ZapfDingbats font and it's saying "arial" and arial is not a ZapfDingbats compatible font.

My suggestion is to install whatever package provides D050000L.otf (ord050000l.pfb) it seems that in opensuse it would be something called ghostscript-fonts and that should fix your issue.

I really don't know by what logic you understand that it is not a "bug". I have clearly defined the scenario: A computer, with a certain configuration. Among all PDF reader software tested (from embedded in web browsers of all kinds, to professional applications like FoxitReader or Master PDF) only Okular fails to show as enabled the checkboxes in cases like this. And yet, it does show it correctly in form mode. 

I don't know under what criteria Okular can't be considered to have a resolution problem in these cases. 

I give up. The solution after everything I have said is not to consider it an error to be solved by you and, thanks to that attitude, unfortunately I can only stop using Okular since we are talking about transcendental information that is not correctly processed by Okular.

Best wishes

(In reply to Rafael Linux User from comment #19)
> I really don't know by what logic you understand that it is not a "bug". 

Please note that the scope here is "a bug in a something developed on kde.org". 
It is true that other programs don't show it, but are they using the same libraries to get the fonts? It may be just an error in a different part of the stack, and that's what was being discussed.