in reply to Convert HTML docs with frames into a single HTML doc?

That's probably a good order; you may also wish to remove all "target" attributed in A tags, which I believe you can also do with HTML::Parser. This should deal with the problem of navigation issues. Also, you'll have to play with COLSPAN and ROWSPAN attributes of the table cells if you have anything more complex than 2 frames.

Alternatively, if you have your own server with SSI enabled, you can include the text of other HTML files (head/body tags included) directly, so you'd only have to write out a table body with the various include tags, and that will get the job done too, though the final document will not necessarily be HTML4 friendly.

-----------------------------------------------------
Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain
"I can see my house from here!"
It's not what you know, but knowing how to find it if you don't know that's important

  • Comment on Re: Convert HTML docs with frames into a single HTML doc?

Replies are listed 'Best First'.
Re: Re: Convert HTML docs with frames into a single HTML doc?
by Beatnik (Parson) on Nov 29, 2001 at 20:41 UTC
    Actually the TARGET options in anchors should only be removed if they refer to a known frame. What if the "designer" uses stuff like _BLANK?

    Greetz
    Beatnik
    ... Quidquid perl dictum sit, altum viditur.
[reply]
[d/l]
      Personally? I hurt them, unless they can give me a very convincing reason not to.1 target=_blank is one of the most annoyingly used tags ever invented, except maybe (maybe) <blink>.

      Fortunately for most designers, Opera can save me from having to hurt them. I :heart: browser tabs. I also :heart: "Never allow popups."

      1 But yes, there are some valid and good uses for target=_blank, and I've even done it myself once or twice. Too often it is simply not needed.
[reply]
[d/l]
[select]
Re: Re: Convert HTML docs with frames into a single HTML doc?
by osfameron (Hermit) on Nov 29, 2001 at 20:17 UTC
    Thanks! regarding:
    Also, you'll have to play with COLSPAN and ROWSPAN attributes of the table cells if you have anything more complex than 2 frames.
    actually I was thinking of naively nesting my tables in the same way as the framesets I'm basing them on. I'm aware that this is more resource intensive to process - are there any other problems with this approach?

    Cheerio!
    Osfameron

[reply]
      No, there shouldn't be any problems with nesting the tables, either. The only problem that I can see is that there will be come a more noticable difference in the margins as you nest further and further unless you remove the cell padding. The margin difference with some cell padding will probably be minor with only two nestings, but 4 or more, and it could be a problem if layout is somewhat important.

      -----------------------------------------------------
      Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain
      "I can see my house from here!"
      It's not what you know, but knowing how to find it if you don't know that's important

[reply]

In Section Seekers of Perl Wisdom