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.
Further, what type of graphics do you need to have accompany the
document? Does the user want to print sections? Is there a compelling
reason to switch other than someone in management wants to?
Searching is going to be a problem. Even if you reconfigure to an HTML
help format you still can have search issues.
How are the documents distributed?
How much time to you have to analyze your document structure and design
a CSS for HTML? Are they willing to eat the time and money to do so? Are
they willing to accept a lesser level of design and layout?
As to linking to a specific point in a PDF document, yes you can do that
if the link is to a named destination in the PDF. Which means you need a
better understanding of PDF and a procedure to do this as well as to
communicate those named destinations to your web developers.
Scott
Robert Lauriston wrote:
> Acrobat Reader can handle URLs to bookmarks:
> www.adobe.com/devnet/acrobat/pdfs/pdf_open_parameters.pdf
>
> What's your source format?
>
> Generally, HTML makes more sense for online use, but PDF is better for
> downloading for offline use. Some places do only PDF, some only HTML,
> some both.
>
> I always produce a PDF, even if it's not distributed to customers, as
> it's more convenient for printing and some kinds of searches.
>
> On Mon, Sep 28, 2009 at 6:22 AM, Anne Woolson <anne -dot- woolson -at- rimage -dot- com> wrote:
>> Hello,
>>
>> My company is wanting to move away from posting our documentation as
>> .PDFs on our support site, and move to presenting them in .HTML. I'm not
>> at all thrilled with this idea, especially since our user manuals are
>> long (300+ pages) and heavily formatted. I think this will be a
>> nightmare to do initially and equally bad (or worse) to maintain.
>>
>> Can anyone tell me what the industry standard really is? And any insight
>> as to what formats are going to be useful in the future? Is there a
>> consensus on what is the right format to be using for online
>> presentation?
>>
>> One point I can't answer is - is there a way to have an html link on our
>> web page jump to a specific bookmark in a .pdf? If so, that may solve my
>> problem outright.
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices. http://www.doctohelp.com/SuperPages/Webcasts/
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-