Speaking of hyperlinks, I have a:
message URL http://url
And when I click on it, it does not open a web browser. Basically, it's
a dead link.
Any ideas?
Regards,
Shmuel Wolfson
Steve Rickaby wrote:
I have the solution for my posting below, although I don't understand it.
For hyperlinks
When you click on it in Frame or in output, like in a generated PDF or
generated HTML?
If you are testing in Frame, you are doing Ctrl-Alt-Click, right?
Also, on my current underpowered box, it's taking 6-8 seconds to come
up...
Art
On Tue, Apr 1, 2008 at 9:25 AM, Shmuel Wolfson [EMAIL
I can't answer *all* of your questions, but I know someone who can. ;-)
ATCS includes RoboHelp, and the current version of RH provides seamless
integration from FM source, skipping the RTF step that used to be required.
Additionally, you can set the new RH to recognize TopicAlias markers as
Speaking of hyperlinks, I have a:
message URL http://
And when I click on it, it does not open a web browser. Basically, it's
a dead link.
Any ideas?
Regards,
Shmuel Wolfson
Steve Rickaby wrote:
> I have the solution for my posting below, although I don't understand it.
>
> For hyperlinks
When you click on it in Frame or in output, like in a generated PDF or
generated HTML?
If you are testing in Frame, you are doing Ctrl-Alt-Click, right?
Also, on my current underpowered box, it's taking 6-8 seconds to come
up...
Art
On Tue, Apr 1, 2008 at 9:25 AM, Shmuel Wolfson wrote:
>
At 16:25 +0300 1/4/08, Shmuel Wolfson wrote:
>Speaking of hyperlinks, I have a:
>
>message URL http://
>
>And when I click on it, it does not open a web browser. Basically, it's
>a dead link.
>
>Any ideas?
Sure it's a hypertext link? ;-) FrameMaker has a foxy way of changing this link
type as
My doc team currently uses Frame 7.1, Acrobat 7.0 Standard, and WebWorks
ePublisher Pro 9.1 to generate our printed docs and online help. Now we are
looking at the Adobe Technical Communication Suite to do it all. However we
have some concerns about moving everyone over and the impact it could
I can't answer *all* of your questions, but I know someone who can. ;-)
ATCS includes RoboHelp, and the current version of RH provides seamless
integration from FM source, skipping the RTF step that used to be required.
Additionally, you can set the new RH to recognize TopicAlias markers as
I have the solution for my posting below, although I don't understand it.
For hyperlinks of the form 'message URL http://', FrameMaker correctly
opens the default browser. However, for hyperlinks that omit the protocol
field, i.e. 'message URL ', for example 'message URL www.microsoft.com',
it
