Re: OT: Firefox image display

This doesn't sound like a Perl issue, since the problem is with the URL format you are using (it might have been a Perl issue if you were using HTTP URLs, but there isn't any chance of that when reading from the filesystem.)

Note: I'm assuming that you copy/pasted the example image tag from the outputted source, or that it is being output as you expected. If not, you should check to make sure the Perl script is outputting what you think it should be.

The mozilla.org site includes file scheme test cases which should show you what formats Mozilla based browsers can cope with. Note that literal spaces are not allowed in URLs, and must be represented as %20.

The simplist solution to this issue is to forget about file scheme URLs and just access the images over HTTP. You'll have to do this if you want to publish the pages on the web anyway.

Comment on Re: OT: Firefox image display

Replies are listed 'Best First'.

Re^2: OT: Firefox image display
by kaif (Friar) on Jun 14, 2005 at 14:58 UTC

The mozilla.org site includes file scheme test cases which should show you what formats Mozilla based browsers can cope with. Note that literal spaces are not allowed in URLs, and must be represented as %20.

I couldn't find such a reference. Where on that page does it say that spaces aren't allowed in URLs? Any modern browser handles spaces in URLs gracefully. After all, remember the original reason for encoding spaces:

The space character is unsafe because significant spaces may disappear and insignificant spaces may be introduced when URLs are transcribed or typeset or subjected to the treatment of word-processing programs.

I don't think that's a significant enough reason to forbid spaces in entered URLs (which can be replaced by %20 in the location bar and page properties, etc. later) compared to the benefits. And indeed I've never had a problem in any Mozilla-based browser involving spaces.

[reply]
[d/l]
[select]


Think about Loose Coupling
	PerlMonks