<p>We use BIRT since version 2.x (currently using 4.2.2) and have <strong>always</strong> been plagued by the PDF (itext?) fonts register time.</p><p> </p><p><span>org</span><span>.</span><span>eclipse</span><span>.</span><span>birt</span><span>.</span><span>report</span><span>.</span><span>engine</span><span>.</span><span>layout</span><span>.</span><span>pdf</span><span>.</span><span>font</span><span>.</span><span>FontMappingManagerFactory$2</span><span> run<br />
INFO</span><span>:</span><span> </span><strong><span>register</span></strong><span><strong> fonts in</strong> c</span><span>:/</span><span>windows</span><span>/</span><span>fonts [color=#b22222;]cost[/color]</span>[color=#b22222;]<span>:[/color]<strong><span>17803ms</span></strong></span></p><p> </p><p>This process only occurs the first time the render is used. Subsequent renders are not problematic.</p><p> </p><p>The problem seems to be the time wasted when accessing ALL the system connected DRIVES.</p><p> </p><p>Editing the fontsConfig.xml in <strong>org.eclipse.birt.report.engine.fonts plugin</strong>, reducing the search paths does not resolve the issue. <strong>ALL connected drives are accessed by BIRT</strong>.</p><p> </p><p><span><</span><span>font</span><span>-</span><span>paths</span><span>></span><br />
<span><</span><span>path path</span><span>=</span><span>"/windows/fonts"</span><span> </span><span>/></span><br />
<span></</span><span>font</span><span>-</span><span>paths</span><span>></span></p><p> </p><p>Is this a problem beyond BIRT control (itext)? Or can it be "fixed"?</p>
