what i am trying to say is that custom fonts load fine when we specify -c 
$fop-config-path, however when we do this a single file takes 300mb and over 30 
seconds. 

while debugging this we tried to convert with default option ie no config path. 
Simple fop input.fo ouput.pdf. it works like a charm except that it didnt load 
our custom fonts. 

so we tried to put config in system wide path, modified config to load custom 
fonts explicitly etc. Nothing works... and i have lost 15% of my hair in the 
process. 

Hope this helps in some / any pointers in any direction !!

Thanks
Ali



Sent from my iPhone

On 09.09.2010, at 19:22, "Eric Douglas" <[email protected]> wrote:

> What are you trying to say?
> You're saying you got it to work with the configuration file?
> What are you trying to do which isn't working? 
> Are you saying using the configuration file without modification works
> but takes up too much resources?
> I just tested FOP 0.95 on mine using a configuration file and a command
> line and it ran really fast and produced proper output.
> I think we need more details.
> 
> -----Original Message-----
> From: Ali Shaheen [mailto:[email protected]] 
> Sent: Thursday, September 09, 2010 1:16 PM
> To: [email protected]
> Subject: Custom font issue
> 
> Hello guys, 
> 
> We have a strange issue. We are using some custom fonts in and we
> generate pdfs using command line. IF we specify the fop configuration
> file (not edited) via -c , the custom fonts are loaded fine. If not they
> aren't loaded! 
> 
> We tried changing system wide path, embedding fonts directly in fop
> configuration as per the online guideline but nothing works. 
> 
> It only works via command line -c switch and if we use that each
> document takes 350Mb and 100% CPU - without this parameter, it's fine. 
> 
> We are using FOP 0.95. 
> 
> Please see the example fo file too. 
> 
> What to do?
> 
> Best wishes,
> Ali
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to