Bug 689670

Summary:	command line argument for font directory
Product:	GhostPCL	Reporter:	Michael <brogdons>
Component:	PCL fonts	Assignee:	Henry Stiles <henry.stiles>
Status:	RESOLVED WONTFIX
Severity:	enhancement
Priority:	P4
Version:	1.51
Hardware:	PC
OS:	other
Customer:		Word Size:	---

Description Michael 2008-01-25 13:21:40 UTC

OS: Vista Business 32-bit

Hi, I have ran into a few problems. 

I noticed that the ghostpcl binary does not support the -I argument for
specifying a path to search for fonts, I was wondering if this could be added.

I also noticed that the pjparser does not seem to like window style paths. If I
change the font resource table to contain a fixed server path,
\\\\server\\share, it will turn this into \servershare. And I assume it is doing
the same for the Environment variable PCLFONTSOURCE, because it keeps
complaining that it cannot find fonts. For now I have put
\\\\\\\\server\\\\share to get it to work, it seems that this should not be the
case.

Comment 1 Ray Johnston 2008-01-25 13:42:38 UTC

We STRONGLY recommend using '/' instead of '\' -- they work the same on
Windows and don't run afoul of shell and C escape confusion.

I agree that a command line option instead of requiring the PCLFONTSOURCE
environment variable seems handy.

Henry can decide who "owns" the PCL and language_switch command line options
and assign it to that person.

Comment 2 Michael 2008-01-25 14:44:55 UTC

agreed, I thought I tried this but I realized I did not do //server/share/, I
did //server/share which got turned into //server/share* instead of
//server/share/*, not allowing for the files to be found. It seems that it would
be easy to check for the existance of the trailing '/' || '\' and append it if
not before appending the wildcard character.

Comment 3 Henry Stiles 2011-02-24 16:53:27 UTC

Unless there is strong objection I find the current code acceptable, closing as WONTFIX.  Please reopen if there really is a problem.