Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.html > #23984 > unrolled thread

Wha' Hoppen?

Back to article view | Back to alt.html

Contents

  Wha' Hoppen? Joy Beeson <jbeeson@invalid.net.invalid> - 2024-10-07 13:20 -0400
    Re: Wha' Hoppen? Ray_Net <Ray_Net@picarre.be.invalid> - 2024-10-08 00:58 +0200
    Re: Wha' Hoppen? "Jukka K. Korpela" <jukkakk@gmail.com> - 2024-10-08 23:09 +0300
    Re: Wha' Hoppen? Joy Beeson <jbeeson@invalid.net.invalid> - 2024-10-11 13:01 -0400
      Re: Wha' Hoppen? Joy Beeson <jbeeson@invalid.net.invalid> - 2024-10-11 13:29 -0400
        Re: Wha' Hoppen? "Jukka K. Korpela" <jukkakk@gmail.com> - 2024-10-12 20:41 +0300
          Re: Wha' Hoppen? Joy Beeson <jbeeson@invalid.net.invalid> - 2024-10-12 20:37 -0400
            Re: Wha' Hoppen? "Jukka K. Korpela" <jukkakk@gmail.com> - 2024-10-13 20:31 +0300
              Re: Wha' Hoppen? Joy Beeson <jbeeson@invalid.net.invalid> - 2024-10-13 20:38 -0400

#23984 — Wha' Hoppen?

I have the folowing boilerplate at the bottom of the file for my diary
< http://wlweather.net/LETTERS/2024BANN/2024BANA.HTM >


<!-- 
</div> 
<center> 
<a href=".JPG"> 
<img src="6h.JPG" 
alt=" ******* " 
width=600 height=450> 
</a> 
</center> 
<div> 
<p>
-->


I used it to add three photos to the October issue.  On viewing the
file with my browser, I couldn't see the pictures, but the link to the
enlarged versions worked perfectly.

"View image" told me that there was no such picture, so I went to the
index, opened the image, and copied and pasted the filespec into the
link.

Still "Can't find file:///C:/LETTERS/2024BANN/HANK6h76.JPG"

So I validated it and got a complaint that there were three close
paragraphs for paragraphs that were not open.

I found that there was a <p> before the </div> and a </p> after the
<div> in each picture, and that these marks were absent from a
previous photo that worked properly.

So I deleted them and now all is well.

But how did an unwanted paragraph mark prevent the browser from seeing
a file that was right in front of its nose?


-- 
joy beeson at centurylink dot net
http://wlweather.net/PAGESEW/

[toc] | [next] | [standalone]

#23985

In article <hu58gj94g9o7tcpa7v61en3ti6irufn0f9@4ax.com>, jbeeson@invalid.net.invalid says...
> 
> I have the folowing boilerplate at the bottom of the file for my diary
> < http://wlweather.net/LETTERS/2024BANN/2024BANA.HTM >
> 
> 
> <!-- 
> </div> 
> <center> 
> <a href=".JPG"> 
> <img src="6h.JPG" 
> alt=" ******* " 
> width=600 height=450> 
> </a> 
> </center> 
> <div> 
> <p>
> -->
> 
> 
> I used it to add three photos to the October issue.  On viewing the
> file with my browser, I couldn't see the pictures, but the link to the
> enlarged versions worked perfectly.
> 
> "View image" told me that there was no such picture, so I went to the
> index, opened the image, and copied and pasted the filespec into the
> link.
> 
> Still "Can't find file:///C:/LETTERS/2024BANN/HANK6h76.JPG"
> 
> So I validated it and got a complaint that there were three close
> paragraphs for paragraphs that were not open.
> 
> I found that there was a <p> before the </div> and a </p> after the
> <div> in each picture, and that these marks were absent from a
> previous photo that worked properly.
> 
> So I deleted them and now all is well.
> 
> But how did an unwanted paragraph mark prevent the browser from seeing
> a file that was right in front of its nose?

"file:///C:/LETTERS/2024BANN/HANK6h76.JPG" is not the good syntax to display an image

per example -> Try this:
<A HREF="HANK6h76 pic"><IMG SRC="HANK6h76.JPG" ALT="HANK6h76" HEIGHT=150 WIDTH=200></A>

The file "HANK6h76.JPG" must be present in the same directory of the html file
and not somewhere on your disk "C:"

another example could be:
Your html file is in "C:\LETTERS" like C:\LETTERS\mytest.html
inside the LETTERS directory you may create a subdirectory "IMAGES" 
then you can have your image here C:\LETTERS\IMAGES\HANK6h76.JPG
then the part of the html file must be: 
<A HREF="HANK6h76 pic"><IMG SRC="IMAGES/HANK6h76.JPG" ALT="HANK6h76" HEIGHT=150 WIDTH=200></A>

[toc] | [prev] | [next] | [standalone]

#23986

Joy Beeson wrote:

> I have the folowing boilerplate at the bottom of the file for my diary
> < http://wlweather.net/LETTERS/2024BANN/2024BANA.HTM >
> 
> 
> <!--

That starts a comment, which ends at the next occurrence of “-->”. The 
content of a comment is ignored by browsers.
> I used it to add three photos to the October issue. 

What you probably mean is that you edited the code by removing the 
comment delimiters and editing the content somehow. It is always a good 
idea to post the URL of your actual page, instead of a template.

> On viewing the
> file with my browser, I couldn't see the pictures, but the link to the
> enlarged versions worked perfectly.

You probably changed <a href=".JPG"> to something else, which does not 
refer to an actual image either.

> Still "Can't find file:///C:/LETTERS/2024BANN/HANK6h76.JPG"

Now it is obvious that your actual code uses a file: URL, which is 
formally valid but almost never useful on web pages. There’s an old and 
dusty but still basically correct explanation of this on my page
https://jkorpela.fi/fileurl.html

Probably some authoring tool you used created such a URL. In that case, 
consider using a better tool. But you can probably make the tool create 
working code, or you can manually edit the code.

> So I validated it and got a complaint that there were three close
> paragraphs for paragraphs that were not open.

It’s useful to fix the markup, but those errors hardly had anything to 
do with the image proble,

> So I deleted them and now all is well.

There’s something missing from this story. For example, you may have 
done something that changed the <img ...> code.

> But how did an unwanted paragraph mark prevent the browser from seeing
> a file that was right in front of its nose?

It didn’t.

The key to the image issue is that the src attribute must refer to an 
image resource with a working URL. For example,
src="file:///C:/LETTERS/2024BANN/HANK6h76.JPG"
might work for a user whose system has a C drive with the folder LETTERS 
containing a subfolder 2024BANN containing a file named HANK6h76.JPG. 
Most probably this means that it only works for you when using a 
particularpersonal computer of yours.

The simplest way is to put the image in the same folder on the web 
server as the HTML document referring to it and use a simple relative 
reference like
src="HANK6h76.JPG"

Yucca

[toc] | [prev] | [next] | [standalone]

#23987

On Mon, 07 Oct 2024 13:20:40 -0400, Joy Beeson
<jbeeson@invalid.net.invalid> wrote:

> 
> I have the folowing boilerplate at the bottom of the file for my diary

> < http://wlweather.net/LETTERS/2024BANN/2024BANA.HTM >

[snip boilerplate and the original description of the puzzle]

Friday, 11 October 2024

Apologies for taking so long to respond -- My excuse is what the
old-time fen called Real Life (TM).

Ignoring back-ups, I have three copies of my diary:  a working copy in
the same directory with my text editor, the primary copy in a
sub-directory of my letters folder, and the Web copy at the link
above.

Today I copied two of the photograhps to file:///C:/Pcw/ROLL1996.JPG
and file:///C:/Pcw/ROLL6h96.JPG, then verified that those two links
worked in the current version of the working copy.

Then I opened the working copy and added <p> where, I think, I deleted
the mark W3C objected to.  (Well, it objected to the close, but I also
deleted the open.)

Saved, re-loaded the file, picture still where it belongs.

Added the </p> that was flagged, saved, reloaded, file still works.

But I didn't change anything but the stray paragraph marks, and this
text editor doesn't have invisible tags that I could have deleted
without being aware of it.

<walks away gibbering>

Wait!  The photograph that I copied was added later, not one of the
offending photographs.

Forget it.  Computers are not deterministic and work in mysterious
ways, and I've spent more mental energy on this than is available.

-- 
Joy Beeson
joy beeson at centurylink dot net
http://wlweather.net/PAGEJOY/

[toc] | [prev] | [next] | [standalone]

#23988

On Fri, 11 Oct 2024 13:01:58 -0400, Joy Beeson
<jbeeson@invalid.net.invalid> wrote:

> Forget it.  

You might know I couldn't.  I copied one of the offending photographs
into the working directodry, with the same result.

The world will never know why the browser couldn't see INIT6h.JPG
before I deleted the stray paragraph mark.

-- 
joy beeson at centurylink dot net
http://wlweather.net/PAGESEW/

[toc] | [prev] | [next] | [standalone]

#23989

Joy Beeson wrote:

> You might know I couldn't.

Next time consider posting a real URL that actually demonstrates your 
problem. Now you have just wasted everyone’s time.

Also consider writing a Subject line that describes the problem you 
have, instead of an incomprehensible slang expression for some emotion.

[toc] | [prev] | [next] | [standalone]

#23990

On Sat, 12 Oct 2024 20:41:29 +0300, "Jukka K. Korpela"
<jukkakk@gmail.com> wrote:

> Next time consider posting a real URL that actually demonstrates your 
> problem. Now you have just wasted everyone’s time.

< http://wlweather.net/LETTERS/2024BANN/2024BANA.HTM >

was at the top of each post, and works when I click on it.   
I just checked, and this copy works too.

What should I have done to make it real?


-- 
Joy Beeson
joy beeson at centurylink dot net
http://wlweather.net/PAGEJOY/

[toc] | [prev] | [next] | [standalone]

#23991

Joy Beeson wrote:

> On Sat, 12 Oct 2024 20:41:29 +0300, "Jukka K. Korpela"
> <jukkakk@gmail.com> wrote:
> 
>> Next time consider posting a real URL that actually demonstrates your
>> problem. Now you have just wasted everyone’s time.
> 
> < http://wlweather.net/LETTERS/2024BANN/2024BANA.HTM >
> 
> was at the top of each post, and works when I click on it.

In your first post, you quoted a comment from it, and as I explained, 
comments are ignored by browsers.

> I just checked, and this copy works too.
> 
> What should I have done to make it real?

You should have initially quoted the part of code (not a comment) that 
does not work in your opinion.

Since the data at the URL is variable, I can only conjecture, with just 
about 99% certainty, that at some moment of time, your actual code 
contained an <img> element with a src attribute value that was a file: URL.

[toc] | [prev] | [next] | [standalone]

#23992

Thank you.

-- 
Joy Beeson
joy beeson at centurylink dot net

[toc] | [prev] | [standalone]

Back to top | Article view | alt.html

csiph-web