TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Re: Of HTML Frames, WebWorks, and FrameMaker ADDED CLARITY
Subject:Re: Of HTML Frames, WebWorks, and FrameMaker ADDED CLARITY From:Kris Olberg <kjolberg -at- IX -dot- NETCOM -dot- COM> Date:Fri, 14 Nov 1997 10:34:04 -0600
-----Original Message-----
From: Brian Heifner <bheifner -at- RATIONAL -dot- COM>
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU <TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU>
Date: Wednesday, November 12, 1997 4:39 PM
Subject: Re: Of HTML Frames, WebWorks, and FrameMaker ADDED CLARITY
>I am envisioning a link something like this:
><A HREF=3D"../Reference_Guide/frames.html" MAINFRAME=3D"chap2.html">.
>where MAINFRAME is setting the contents of one of the frames.
You can specify a target frame in an anchor as follows:
<a href="../chap2.html" target="MAINFRAME">
The value of the target attribute is the name assigned to the frame tag in
your FRAMES.HTML. For example:
<FRAME ... name="MAINFRAME">
Regards...Kris
------------------------------
kolberg -at- actamed -dot- com
kris -at- olberg -dot- com