Hi Florian,

On 2021-03-04 17:07:35 +0100, Florian Schlichting wrote:
> Hi Vincent,
> 
> this bug was cloned from #848671, where people complain about error
> messages when starting xpdf. The messages were about configuration
> options for which support was removed in poppler, but which were still
> contained in the "language support" (configuration) files shipped with
> xpdf.
> 
> With this bug you seem to request that support for these options should
> be added back. Do you have a specific need for any one of them, or was
> that just meant as a reminder since the error message seems to suggest
> that support would be possible if only someone put in the work?

This was just because the source had:

+        error(errConfig, -1,
+              "Some work needs to be done to suppport this option in the 
Poppler version of xpdf");

This seems to suggest that the user uses a still valid option, but
the issue is that this is not supported yet in the Poppler version
of xpdf (and the message seems to say that this will be done in the
future).

Now, the error message has changed in the current version:

        error(errConfig, -1,
              "This option is not supported by the Poppler version of xpdf");

If the goal was to definitely drop these options, this is no longer
misleading.

> My current understanding is that poppler doesn't and is not going to
> support these any more, at least not as part of its public API. That
> said, all the mapping files referenced in xpdf's "language support"
> files are nowadays shipped in the poppler-data package, which claims in
> its README that poppler will read them automatically when available. So
> there's really no need to try and set any of this from xpdf, no?

I think that the current status (with the new error message) is fine.

For instance, if I create a .xpdfrc file with "drawAnnotations", I get

Config Error: Unknown config file command 'drawAnnotations' 
(/home/vinc17/.xpdfrc:1)
Config Error: This option is not supported by the Poppler version of xpdf

Since one already has an error message "Unknown config file command...",
I'm not sure that the second one is useful in practice, though
(what is its intent?).

-- 
Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Reply via email to