George Paul, Rob and all
The main problem with the validator is it checks the that the coding
of your page has a valid syntax. What happens inside that synatx can
be loaded with problems and will still work.
I've taken a look at the page code and the first thing I'd be fixing
is the spaces in the path names. I've had problems on a site I
maintain with with IE choking on url's with encoded characters in the
past. Spaces are not legal characters for URL's so get encoded as "%
20", either by the web server or your authoring program. The Raccon
url for instance is currently:
"Welcome _files/mp3%20racoon%20encounter%20publis.mp3"
to eliminate the path name from the list of likely suspects try
renaming folders and files to:
"Welcome_files/mp3_racoon_encounter_publis.mp3" for example...
cheers
Paul
On 12/07/2007, at 2:06 AM, Rob Danielson wrote:
> At 2:14 PM +0000 7/11/07, George Paul wrote:
>> I received an e-mail from Gerald, GWAPuffin, as follows:
>>
>> "George Paul,
>> I have FireFox installed and it uses QuickTime to play the files, it
>> works the way you would
>> expect. The problem is with IE and Windows Meda Player, I don't
>> think IE recognizes the
>> format that your web page is using. I only mention the problem
>> because there may be
>> many
>> people that can not hear the files, it is possible to do a work
>> around but many users just
>> use
>> one product and depend on it working as expected.
>> Gerald"
>>
>> Thanks Gerald:
>>
>> Just curious. I built that site with Apples iWeb software. I was
>> assuming it could be
>> accessed by all web browsers.
>>
>> Just to know, how many other people could not access the site, and
>> what browser are they
>> using? It is good to know these things, as who wants to build a web
>> site if no one can
>> look at it? Indeed, many might just try for a second or two, and if
>> things aren't working,
>> they give up and go on to something else. You really have to look
>> at something to trouble
>> shoot, just as Puffin says.
>>
>> Thanks to Gerald for tipping us all off to this dynamic and
>> possible problem.
>>
>> George Paul
>>
>>
>
> This is on-topic to the extent that we are discussing ways of
> accessing each other's work.
>
> I did a quick search and pros are reporting that the iWeb code (for
> the newest version only), though bulky, is for the most part web
> compliant-. George's page seems to be compliant:
> http://validator.w3.org/check?uri=3Dhttp%3A%2F%2Fweb.mac.com%2Fgeopaul
> %2FiWeb%2FThe%2520Visit%2FWelcome%2520%2520.html
>
> I could not find any specific references to mp3 download issues with
> IE. With this compliancy in mind, Jerry's IE difficulty spells out
> the dilemma pretty clearly for me. As a novice web page maker, which
> is easier for me to do? (1) Help visitors who come to my site using
> IE adjust their settings and update their plugs or (2) Encourage them
> to try FireFox? FireFox also has excellent accessibility support.
>
> I've not heard from one IE/Windows XP user who went back to regular
> use of IE after using FireFox as their regular browser. It takes
> about 5 minutes to install (DSL) and you can import all of your IE
> bookmarks. I checked my website and Firefox (42%) is now edging out
> and IE (41%) and Safari is at %15,. IE was closer to 70% last
> spring, so more folks could be exercising their options. Rob D.
>
>
>
>
>
>
> "While a picture is worth a thousand words, a
> sound is worth a thousand pictures." R. Murray Schafer via Bernie
> Krause
>
> Yahoo! Groups Links
>
>
>
|