Yes, sorry, I shoud have said: I did play around with all the page break options but nothing seemed to make any difference. I'll try again, though, maybe there's some combination that I missed.
Michele
-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Yvonne Kester
Sent: Thursday, September 11, 2014 8:39 AM
To: [log in to unmask]
Subject: Re: Not strictly EAD but sort of related
Hi Michele,
It's hard to know what you are dealing with, without seeing the code you use for your printer-friendly versions, but I found this page online that may help. A similar situation. http://stackoverflow.com/questions/1763639/how-to-deal-with-page-breaks-when-printing-a-large-html-table
I hope this helps!
Yvonne
Yvonne Kester
Library Systems Analyst
Lucy Scribner Library - Skidmore College Saratoga Springs, NY 12866
(518) 580-5518
-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Michele R Combs
Sent: Wednesday, September 10, 2014 4:42 PM
To: [log in to unmask]
Subject: Not strictly EAD but sort of related
Hi all --
I'm hoping that someone might have suggestions for a weird issue we've run into with the printer-friendly versions of our finding aids.
Our style sheet renders the inventory section as tables, one table for each c01 (I know, I know, using tables for layout is bad practice, mea culpa, but we don't have the time to completely rewrite our style sheets [although it's on my list]).
When printing a finding aid, very occasionally we'll encounter a situation where the end of a table row butts up exactlypreciselysmackdab against a page break. This causes the printed version to truncate the remainder of that particular table (i.e., the rest of that c01 information), as if it doesn't even exist. The worst part is, there is NO EVIDENCE that anything is missing, so the poor researcher that prints this out will have no idea that he's missing part of the finding aid. Clearly something is wonky in the browser's interpretation of the file behind the scenes, perhaps in the way it thinks it's OK to break pages. We're not using divs, just plain old tables.
Can anyone suggest a css fix for this?
Michele
+++++++++++++++
Michele Combs
Lead Archivist
Special Collections Research Center
Syracuse University Libraries
315-443-2081
[log in to unmask]
scrc.syr.edu
|
