Re: [evince] can't open Québec Pension Plan documents

[Paul Menzel <pmenzel+evince-list molgen mpg de>]

[Resent from correct address, and added point 3.]

Dear Udvarias,


Am 31.08.22 um 00:05 schrieb Udvarias Ur via evince-list:

> I recently got my /Québec Pension Plan/ PDF documents from their secure 
> /My Account/ WEB site.
>
> /Evince/, both versions 3.18.2 (32 bit) and 3.36.10 (64 bit) open the 
> documents. *Neither displayed any of the data!* On the other hand none 
> of the following had any trouble.
>
>   * /Adobe Read 9/ (32 bit),
>   * /flpsed/ 0.7.3 (32 bit),
>   * /MuPDF/ (32 bit), and
>   * /Libre Office Draw/ 5.1.6.2 (32 bit).

Thank you for your reporting the issue. What distribution do you use?

> That being said when I added a password to one of the documents, so I 
> could send it by eMail;
>
>   * Evince, as usual,
>       o asked for the password,
>       o accepted the pasting of the password and
>       o then opened the document *without any of the data*,
>   * Adobe Read 9
>       o insisted that I type in the the password
>       o but wouldn't accept it because it has punctuation in it.

Sorry, just to be clear, this is a second bug report that adding a 
password with Evince, the document cannot be opened by Adobe Reader?

To fix these issues, can you please:

1.  Test with the latest Evince release to confirm the problem is still 
present.
2.  If it’s still present, create an issue and provide an example 
document to reproduce the issue.
3.  Contact the Québec Pension Plan folks, notifying them about the issue.

> As Adobe has *not* supported Linux since 2010 and Evince has become the 
> flagship PDF reader for Linux, I think it behoves the Evince developers 
> to keep up with and implement the features of the most recent version of 
> Adobe Read. If this does not happen Linux users will be forced either to 
> go back to Windows or Mac so as not to be relegated to the backwaters of 
> the computing world.

Thank you, but this comment is unnecessary, as especially the Evince 
developers are well aware of this. The problem is as always in FLOSS 
manpower and financial resources to pay developers.


Kind regards,

Paul