[Poppler-bugs] [Bug 49037] Noncompliance with Standard-14 fonts requirement in PDF specs

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=49037

--- Comment #13 from suzuki toshiya <mpsuzuki at hiroshima-u.ac.jp> 2012-04-25 07:42:46 PDT ---
When I was writing about the replacement of hardwired pathnames
by configured strings for Ghostscript directories in GlobalParams.cc,
I was thinking about Unix systems. But...

(In reply to comment #7)
> (In reply to comment #6)
> > Exposing the path to the configure script is probably a good idea.
> 
> Yes, for MinGW users. On a pure Windows system there is no way to use a
> "configure" script. When I started with poppler, I used MinGW, too, but in some
> way it breaks my Visual C compilations, as far as I remember, therefore I
> removed it and create my project files for Visual C manually..

This is very enlightening comment and I should reconsider.

(In reply to comment #5)
> 3. Of course we could search the registry for a ghostscript installation, it's
> quite easy, too, and look for the GS_LIB-key, it already has a pointer to the
> ghostscript installed fonts. But unfortunately ghostscript removes its font
> installer, so also here You have to download the ghostscript fonts manually and
> have to put them in the correct directory.

I think this idea (searching the font directory of Ghostscript by
the registry) is better than playing with the pathname of poppler
executables. Just I've scratched a small tool to search the registry
keys named "XXX Ghostscript\XXX\GS_LIB" and collect the directories
from their values into GooList object.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.