Ellen Heitman wrote: > My site has large amounts of text (basically you will be able to read > the contents of a book on my site, divided into chapters). I found > the best way to manage the amount of text (we're talking 50+ pages of > a PDF document) was to put all the text into an iframe, and manage it > in a separate HTML file.
That sounds quite odd. The normal approach is to divide the book into smaller pieces, e.g. by chapters, and set up an index page, and possibly offer also the alternative of accessing the book as a single HTML file, e.g. for printing. > Is this the best way to handle this with > CSS? The structural question is not a CSS issue. Your choice with it affects the type of CSS problems you need to solve, though not that much. Frames are not a CSS thing at all but a matter of markup, and largely out of fashion for good reasons, though iframes have some job to do in this imperfect world. If you use an iframe, you need to remember that the <iframe> element creates an inline frame where the referred document is displayed _independently_. It is immune to everything you say in style sheets for the embedding document. They can share style sheets of course, just as any two documents can, but for that you need <link> elements in both the embedding document and the embedded document. -- Yucca, http://www.cs.tut.fi/~jkorpela/ ______________________________________________________________________ css-discuss [[email protected]] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
