>
> It's FontFactory.getFont(...) not FontFactoryImp.getFont(...);
> unless you looked at the internal iText classes.
> Apparently there's a difference in the JVM in run mode versus
> debug mode. Did you use registerDirectories() or something else?
> Maybe the state of your JVM is different in run
jb wrote:
> thanks for your quick and valuable observation!
> if i register this font manually, the result is ok. (but i still see
> that FontFactoryImp.getFont() works "fine" in run mode, but it
> always returns the default font when running in debug mode without
> this explicit font registering..
> I don't think you have to look inside the iText source
> to find the culprit. I think you should look into your
> own code; more specifically the lines where you create
> the font "arialn.ttf". Apparently you have access to
> that file when creating tabs_run.pdf but not when creating
> tabs_debu
jb wrote:
> hi,
>
> i am trying to debug a minor bug in my
> iText based application, and i get slightly
> different result when i run my program
> in "run mode" or in "debug mode" in Eclipse.
> it is quite confusing, and so i cannot debug the
> problems, that occur only in run mode...
>
> where
hi,
i am trying to debug a minor bug in my
iText based application, and i get slightly
different result when i run my program
in "run mode" or in "debug mode" in Eclipse.
it is quite confusing, and so i cannot debug the
problems, that occur only in run mode...
where can i find the responsible li
