Remote debugging means assumptions or questions or both. I started by assuming this user like most is running from a command line. Finding the fonts correctly is a lot easier from embedded code. It's even easier if I can compile the fonts into a jar and reference them internally so they never have a path. The second easiest way is if you can reference them with a path relative to the path of the fop.jar.
Users frequently expect remote debugging but unless you have remote access to view their machine instructions look like Step 1: Does your screen show this? If yes do this, else do that. -----Original Message----- From: Jeremias Maerki [mailto:[email protected]] Sent: Wednesday, February 02, 2011 1:35 PM To: [email protected] Subject: Re: font missing warning Check the environment ("set" on Windows). Look for the "TEMP" entry. It's TEMP=C:\Users\Jeremias\AppData\Local\Temp on my machine for my user. If it's not around, maybe the user under which FOP is running has no write access to the user directory or there is no user directory at all. I have no idea. I love remote debugging. ;-) On 02.02.2011 18:58:53 Roberto Cahanap wrote: > Hello Jeremias, > > Thank you for shaking my memory. Yes on the TEST server, we have a folder named .FOP that is in the USERACCOUNT's directory. Inside this is a file called fop-fonts.cache. > > There is no such folder on our Production server. Would you know why this is so? > > If this folder is not there, then where would it be looking for these "cached" fonts? If like you say "in the temp directory", where would that be on a Windows system? > > Thank you again. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
