DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15316>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15316 FOP does not resolve relative paths [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[EMAIL PROTECTED] Status|CLOSED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2003-10-08 22:05 ------- I want to reopen this bug. Some time ago I talked to J. Pietschmann (I hope he has nothing against cc-ing and can comment if necessary) about this issue and he answered: Hmhm, irgendwo lag mal ein Patch rum... Ich bin durchaus versucht, FontResolver/ImageResolver/SourceResolver in den maintenance Code einzubauen, nur mal so als Test obs was taugt. Grosse Magie ist nicht dahinter: drei neue Klassen, ein paar schnelle Config-Methoden und etwas Code hin-und-hergeschoben... The translation in short: There was a patch somewhere ... Moving FontResolver/ImageResolver/SourceResolver (from FOP head if I'm not wrong) to maintenance branch (0.20.x), some configs and moving around a bit code should do it. Are these changes only related to FOP? Joerg
