DO NOT REPLY [Bug 40288] - base url requires /, failes otherwise

2006-08-19 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40288.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40288


[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|normal  |critical




--- Additional Comments From [EMAIL PROTECTED]  2006-08-19 07:50 ---
(In reply to comment #0)
 A file:// url in the base element in fopconfig.xml must end with a slash on 
 Linux. If it does not, images (specified by url(foo) where foo is a 
 relative 
 file name) won't be found and will thus not be added to the PDF. FOP should 
 probably either accept both ways to specify the url or display an ERROR that 
 refers to this setting. This would make it much easier to debug this problem.

Well, this is the normal behavior of URLs (and more generally URIs). When
resolving a relative reference against a base URI, all the characters of the
base URI which are to the right of the rightmost slash are removed, and replaced
by the relative path:
file://path/to/images + myImage.png - file://path/to/myImage.png
file://path/to/images/ + myImage.png - file://path/to/images/myImage.png
So the ending slash is important!

The best Fop can do IMO is display the full resolved URI in the error message,
so that the user immediately sees that there is something wrong with URI 
resolution.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


DO NOT REPLY [Bug 40288] - base url requires /, failes otherwise

2006-08-19 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40288.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40288


[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|critical|normal




--- Additional Comments From [EMAIL PROTECTED]  2006-08-19 07:54 ---
Hey, I didn't want to change the severity of this bug! Sorry :-\

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


Re: DO NOT REPLY [Bug 40288] - base url requires /, failes otherwise

2006-08-19 Thread Simon Pepping
 (In reply to comment #0)
  A file:// url in the base element in fopconfig.xml must end with a slash 
  on 
  Linux. If it does not, images (specified by url(foo) where foo is a 
  relative 
  file name) won't be found and will thus not be added to the PDF. FOP should 
  probably either accept both ways to specify the url or display an ERROR 
  that 
  refers to this setting. This would make it much easier to debug this 
  problem.
 
 Well, this is the normal behavior of URLs (and more generally URIs). When
 resolving a relative reference against a base URI, all the characters of the
 base URI which are to the right of the rightmost slash are removed, and 
 replaced
 by the relative path:
 file://path/to/images + myImage.png - file://path/to/myImage.png
 file://path/to/images/ + myImage.png - file://path/to/images/myImage.png
 So the ending slash is important!
 
 The best Fop can do IMO is display the full resolved URI in the error message,
 so that the user immediately sees that there is something wrong with URI 
 resolution.

This could be documented on the configuration web page. There could
also be more info about debugging a configuration file, and about
debugging the font setup.

Regards, Simon

-- 
Simon Pepping
home page: http://www.leverkruid.eu