Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Printing Strangeness

Status
Not open for further replies.

Arion23

IS-IT--Management
Mar 29, 2001
132
AU
Hi all,

This ones been stumping me for most of the day now, so I figured I'd unleash it on the collective...

At
is a lengthy document. A number of people have reported when attempting to print it (from IE or Netscape, not sure about anything else), only about 1/4 to 1/3 of the page is printed. The odd thing is that the footer section of the page (disclaimer and agency links) is printed on the last page.

Printing it out from different PC's browsers results in varying print lengths, but none of them complete. The guy that built the page is of the thought that it is something related to the HTML code. I ran the code through a verifier, and fixed missing <tr> and extra </a> tags, but still having the same problem.

I'm thinking it's a browser/printer/memory issue but I would appreciate your thoughts on possibilities.....
 
Just an update, I was incorrect when I said its not working from Netscape (4.7) - it is - still leaving me wondering why its having problems with IE.
 
well you could cut out a lot of unnecessary code. like the constant td width=&quot;100&quot;, tr valign=&quot;top&quot;, and p class=&quot;body&quot; ... why don't just set all TR valign's to top.. and the td width is definitely redundant. If they're in the same column, then they will all be 100 by default. As for <FONT FACE=monospace>p class=&quot;body&quot;</font>... why don't just throw the whole thing in a <FONT FACE=monospace>&lt;div class=&quot;body&quot;&gt;Stuff&lt;P&gt;more stuff&lt;/div&gt;</font>. Structurally, you have one body with many paragraphs, not many body paragraphs. This would cut down on file size and complexity. And the <FONT FACE=monospace>&lt;td bgcolor=&quot;#ccff99&quot;&gt;</font>... also redundant. Make a CSS class.<br><br>I once worked with this guy in a web development group when I was starting out... I was experienced but with no resume, he had a resume but with little experience, it was supposed to be a perfect match. He took a huge table, built it in Microsoft Excel, and asked me why it took so long to load. My first thought was, &quot;oh my *%@$#!&, the file size is 1.5 MB!&quot; I got out of that project <i>fast</i>.<br><br>The point is, you need to optimize your code. It seems as though you've had this code generated for you. That can be more trouble than it's worth, as many times you'll spend a LOT of time painfully going through the code. Simplify simplify simplify, and pages like this won't be quite so bad. <p>Liam Morley<br><A HREF="mailto:"></A><br>&quot;light the deep, and bring silence to the world.<br>light the world, and bring depth to the silence.&quot;
 
Thanks for the thoughts, just want to point out tho that it is not a site of my making, and not something that I have any control over. I am, however, required to give the owner assistance.

What I'm after is some solid technical evidence that would explain why the page is not printing correctly in IE. If that evidence points to the way the page was generated (ie the sheer bulk of the code) then I can use that to convince the owner to consider alternative means of producing his content (rather than just scripts in MS Office).

Thanks again...
 
Ahh, I see, sorry then. All I can say is that the code optimization would probably do the trick (and if optimization alone isn't the problem, it probably would take care of any other obscure bug), although that's not much of a technical explanation.<br><br>I did try running it through the W3C validator and this does look interesting:<br><FONT FACE=monospace>&lt;input type=&quot;hidden&quot; name=&quot;restrict&quot; value&gt;</font><br><br>you don't have a name-value pair for the value attribute.<br><br>Here's a link to the W3C validator output... most of it has problems with a bunch of proprietary code.. but that shouldn't be an issue. I'd say optimization would be the biggest issue, but again that's not much of a technical answer. Sorry I can't do much more...<br><br><A HREF=" TARGET="_new"> <p>Liam Morley<br><A HREF="mailto:"></A><br>&quot;light the deep, and bring silence to the world.<br>light the world, and bring depth to the silence.&quot;
 
>> Sorry I can't do much more...

Not at all, I appreciate the input. Looks like I'll just put the case forward that the amount of code and poor structure are potentially the cause of the problem...

Thanks for the help...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top