On 14.10.2004 12:28, Vadim Gritsenko wrote: >>Hi,fop block developers: >> I have checked fop block src and fop own src. >> In fop serializer configuration ,user can use relative path and protocol like : >><user-config>context://fontsconfig.xml</user-config> >>but in fontsconfig.xml the font path is like >> <entry> >> <key>fontBaseDir</key> >> <value>file:/C:/My Documents/IBM/wsad/workspace/PowerOA/WebContent/</value> >> </entry> >> <fonts> >> <font metrics-file="simkai.xml" kerning="yes" >> embed-file="C:/WINNT/Fonts/simkai.ttf"> >> <font-triplet name="simkai" style="normal" weight="normal"/> >> </font> >> <font metrics-file="simsun.xml" kerning="yes" >> embed-file="C:/WINNT/Fonts/simsun.ttc"> >> <font-triplet name="SimSun" style="normal" weight="normal"/> >> <font-triplet name="simsun" style="normal" weight="normal"/> >> </font> >> </fonts> >> Fop using File() and java.net.URL to get font file,so it doesn't support context: >> or cocoon:// protocol >> Obviously,this config is not friendly.Could it possible let user set fontBaseDir in >> serializer config >> using context: and then let serializer convert to real path and then set to >> fop?Maybe it is something >> like <render> in fop serializer configurations. > > It's a known issue: > http://issues.apache.org/bugzilla/show_bug.cgi?id=15316
It's a bit different as the reference to user-config is already possible with Cocoon URLs, but not for the URLs inside user-config. (That's the part the issue addresses.) AFAIU his idea is now to avoid the config in user-config, but to pass the resolved URLs for fontBasDir to FOP. The problem is simple that Cocoon does not touch the user-config at all, but only tells FOP where to find it, so I don't see a chance to do this without touching FOP - and if we do, we can implement the "real" source resolving there too. Joerg
