<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Japanese text not rendered from a pdf" href="https://bugs.freedesktop.org/show_bug.cgi?id=81746#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Japanese text not rendered from a pdf" href="https://bugs.freedesktop.org/show_bug.cgi?id=81746">bug 81746</a> from <a class="email" href="mailto:jehan@zemarmot.net" title="Jehan <jehan@zemarmot.net>"> Jehan</a> <pre>Created <a href="attachment.cgi?id=103512" name="attach_103512" title="poppler-data: add a pkg-config file.">attachment 103512</a> <a href="attachment.cgi?id=103512&action=edit" title="poppler-data: add a pkg-config file.">[details]</a> <a href='page.cgi?id=splinter.html&bug=81746&attachment=103512'>[review]</a> poppler-data: add a pkg-config file. Oh! Well indeed when I install this in my dev build, it works. I guess our official release does not have it either, then. Could I propose an improvement to poppler-data package? I submit a pkg-config file. This would allow third-party to decide whether they want to have a strong dependency to poppler-data (or at least a warning maybe for the packager if poppler-data is missing). I know pkg-config is rather known to be used for libraries, but it is also actually very commonly used for data packages as well (check your /usr/share/pkgconfig/, you will likely see a lot of .pc files for data packages there). If you were to add this pkg-config, we would likely add at least a check of poppler-data with a warning on GIMP configure script. As a side feature, it will allow the poppler package to detect the right path for the datadir. Right now, poppler determines the data root either if the packager explicitely gives the --datarootdir option, or by assuming by default it will be on the same prefix as poppler itself. Using pkg-config simplifies and gives flexibility. Attached patch: 0001-Adding-a-pkg-config-file-for-poppler-data.patch</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>