"http://www.cleancomputes.com/Cub/Cub%20Optional%20Equipment%20Manuals/Cub%20RockShaft%20Packages/Rear%20Rockshaft%20Unit%20512%20652%20R92%206-30-48/Page%2004.jpg"
When I put the img tags around it I got this.

I am using IE 7.
Moderator: Team Cub
Barnyard wrote:I just went to the site and copied the properties from the last pic on it and this is what I got (without the quotation marks)
"http://www.cleancomputes.com/Cub/Cub%20Optional%20Equipment%20Manuals/Cub%20RockShaft%20Packages/Rear%20Rockshaft%20Unit%20512%20652%20R92%206-30-48/Page%2004.jpg"
This presentation contains content that your browser may not be able to show properly. This presentation was optimized for more recent versions of Microsoft Internet Explorer.
If you would like to proceed anyway, click here.
Rudi wrote:How Bill did it is exactly the way it should be done. This will work in IE, Opera, Google Chrome, Safari and most other browsers all but one -- and that would be Mozilla FireFox. For some reason, FireFox is not universally backwardly compatible which is out of sync with the rest of the browser families. FireFox is always difficult as it does not handle punctuation properly. So if you have say an apostrophe in the url you have to substitute ASCII code %27 so that FireFox can understand it.
2.2. Reserved Characters
URIs include components and subcomponents that are delimited by characters in the "reserved" set. These characters are called "reserved" because they may (or may not) be defined as delimiters by the generic syntax, by each scheme-specific syntax, or by the implementation-specific syntax of a URI's dereferencing algorithm. If data for a URI component would conflict with a reserved character's purpose as a delimiter, then the conflicting data must be percent-encoded before the URI is formed.
reserved = gen-delims / sub-delims
gen-delims = ":" / "/" / "?" / "#" / "[" / "]" / "@"
sub-delims = "!" / "$" / "&" / "'" / "(" / ")"
/ "*" / "+" / "," / ";" / "="
The purpose of reserved characters is to provide a set of delimiting characters that are distinguishable from other data within a URI. URIs that differ in the replacement of a reserved character with its corresponding percent-encoded octet are not equivalent. Percent-encoding a reserved character, or decoding a percent-encoded octet that corresponds to a reserved character, will change how the URI is interpreted by most applications.
2.3. Unreserved Characters
Characters that are allowed in a URI but do not have a reserved purpose are called unreserved. These include uppercase and lowercase letters, decimal digits, hyphen, period, underscore, and tilde.
unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~"
Unsafe: Characters can be unsafe for a number of reasons. 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. The characters "<" and ">" are unsafe because they are used as the delimiters around URLs in free text; the quote mark (""") is used to delimit URLs in some systems. The character "#" is unsafe and should always be encoded because it is used in World Wide Web and in other systems to delimit a URL from a fragment/anchor identifier that might follow it. The character "%" is unsafe because it is used for encodings of other characters. Other characters are unsafe because gateways and other transport agents are known to sometimes modify such characters. These characters are "{", "}", "|", "\", "^", "~", "[", "]", and "`". All unsafe characters must always be encoded within a URL. For example, the character "#" must be encoded within URLs even in systems that do not normally deal with fragment or anchor identifiers, so that if the URL is copied into another system that does use them, it will not be necessary to change the URL encoding.
Return to “Message Board & Computer Questions”
Users browsing this forum: No registered users and 0 guests