My company is developing a new browser-based software package that is
specced to include screen-level context sensitive help.
The coders haven't done this before and are asking for
help/assistance/advice on developing the coding standard for this and other
products going forward.
I'm thinking the
I implemented this successfully.
Tomorrow I will be in the office, and be able to send you the code we used.
It is also on the Adobe forum, if I find the link I will send it to you.
Caroline Tabach
___
This message is from the Framers mailing list
Se
Hi
Please see this link on Adobe forum, and the threads it links to
https://forums.adobe.com/message/10912271#10912271
Caroline Tabach
On Tue, 14 May 2019, 19:20 Caroline Tabach,
wrote:
> I implemented this successfully.
>
> Tomorrow I will be in the office, and be able to send you the code we
Since you're posting this on the Framers list, I presume you're using
FrameMaker.
Its "multi-channel publishing" feature is a subset of RoboHelp. You
probably want to choose Responsive HTML. Do not choose Microsoft HTML
Help.
Alternatively, link the FrameMaker source to RoboHelp, and you'll have
Graphic import appears to work differently in FM2019 compared to FM2017. To me
it appears to be broken.
If I import a TIF file by reference that is NOT one of the default resolution
options, let's say a 600dpi TIFF:
1. Under FM 2017 it would read the resolution as 600dpi and the scaling
percen
If you're importing into a table cell, this is a known bug that is being
worked on. See here: https://tracker.adobe.com/#/view/FRMAKER-6271
I'm using FM 2019 on Windows 10 and importing an image directly to the body
of the document, as opposed to into a table cell, works fine.
Unless it's an SVG
Looks like having both FrameMaker and RoboHelp (i.e. Adobe Technical
Communication Suite) is essential for publishing context-sensitive
help.
RoboHelp can generate the map file from the TopicAlias markers:
https://help.adobe.com/en_US/robohelp/2017/robohtml/#t=book%2Frob_createhelp_ch%2FManaging_
I have made context sensitive help without RoboHelp.
See links sent above.
Frame 2017
Caroline Tabach
On Tue, 14 May 2019, 20:58 Robert Lauriston, wrote:
> Looks like having both FrameMaker and RoboHelp (i.e. Adobe Technical
> Communication Suite) is essential for publishing context-sensitive
Sure, it's technically possible, but automatically generating the map
file is a basic feature of help authoring tools. Doing it manually in
a text editor invites human error.
The FrameMaker doc itself points to the RoboHelp "Information for
Developers" section. That's the correct way to write help
