C1 Community

It looks like most of the messages on this Forum are ancient, but if you are struggling with Doc-To-Help 2000 (or earlier) -- WexTech Doc-To-Help, or are trying to convert old legacy projects to ComponentOne Doc-To-Help, post your questions here.

I'm the former director of technical support and training at WexTech, and am now a ComponentOne Doc-To-Help Trainer and MVP. I'd be glad to help you.

Regards,

Paul Neshamkin
Microsoft Help MVP
ComponentOne Doc-To-Help MVP & Certified Trainer

Yes please. I've inherited a Doc-To-Help 2000 project that needs to be updated. Everything had to be installed on a new computer and now, when I try to compile it, I get the message "Cannot identify the current output target. "...old target name..." is not the name of a defined target in the project. The next message says to contact Wextech.
What do I do with that?

Replying to my own post (well, editing)... nevermind.
Now that I've found out what an output target is and where it's configured, the question has become moot.

Paul,

I've been having trouble with printed manual title pages from DoctoHelp 2007.  I didn't have this problem with DoctoHelp 2001.  When I tell DoctoHelp 2007 to generate a manual, it moves my title pages to unpredictable locations, and generates its own boilerplate title pages.  What are the tricks for gaining control over title pages in the printed manual?  I can't afford to spend time modifying those title pages manually, because we have dozens of manuals to generate.  I need an automated process that will generate exactly the title pages I want.  The DoctoHelp 2007 documentation doesn't seem to contain much information on this, but I suspect the software can handle it.

Thank you -- David

I have been using Doc-2-Help products for several years, but have not yet upgraded beyond Doc-2-Help 2000.

Presently, I have problem with compiled-help images being truncated to approx 800 pixels wide maximum.

I wish to use the compile option "Reset Graphics Scaling to 100%" to allow screenshots to appear clear and non-dithered in the compiled help. Some of my original screenshot images need to be wider than 900 pixels.

The right-hand truncation (beyond 800 pixels) problem occurs regardless of target compiler/platform and independant of the page-space occupied for printed output from Word.

I have tried numerous doc-2-help options and image insertion techniques to avoid the truncation, but with no success.

Can you help?

Have you tried the different compression levels under Conversion Rules > Graphics?

If you can't get this to work, you should just file a standard pre-sales tech support request for Doc-2-Help 2007.  They should be able to tell you within 24 hours whether Doc-2-Help 2007 can handle it.  The new version has a lot of new features.

Steve,

I seem to remember that this type of truncation happened with graphics that were beyond the right margin in Word. I can't remember a solution other than starting with a smaller graphic.

 Paul Neshamkin

With Doc-To-Help 2007, you should modify the template for your printed manual (C1H_PRNORM.DOT or the corresponding one to your source document template). This contains a title page which you can completely customize to meet your needs. The title page should not be included in the source document (as it was in the WexTech version of Doc-To-Help). The template can be opened easily from the Project Editor by clicking on its name in the list of templates visible in the upper-right pane if you click on the Templates branch.

 Paul Neshamkin

Paul, thank you for the information.  In the last few weeks I self-learned how to create a custom template.  However, I have yet to learn how to control headers and footers in the printed manual, or customize the title page format.  These two issues are sort of linked.  For example, if I remove the title and supertitle from my customized template, I get undesired headers and footers.  It seems that the title page must resemble the D2H standard template much more than I would want, to avoid miscellaneous formatting problems in the printed manual.  This is either a limitation of D2H 2007, or there are some features I have yet to learn about.  Please let me know if you have any additional information on this.  -- David

Paul,

I have been using DTH 2000 for years, and only since compiling yesterday, started getting this nasty in my error log.  

HC3021: Warning: topic #1 of C:\CY04 RSupply Documentation (MFOM updates)\MFOM Viking-DLMS-Force Documentation (822-01.06.15)\WinHlp40\File 1.rtf :
 Cannot find the bitmap "help0006.wmf."

 As far as I know, nothing has changed. The compile is fine, but instead of my graphics DTH inserts its own "the picture "help0006.wmf" is missing!"

please help!   :o)

Theresa

Hi,

I'm trying to convert d2h2000 projects to d2h2006. But the conversion of heading 4 doesn't work. I get the following error :

Warning: Field target does not exist in the project.
File: test.doc
Field:  \Relate "test!7", "test" \D2HTargetDefault

This happens to al heading 4 (pop-ups). So i need to create al the heading 4 pop-up's manualy.

Is there a sollution for this problem?

 Tia

Nietsnut

If you have a list of related topics at the end of a parent topic, you may have to reinsert the related topics heading, or the heading that precedes the list of topics and their buttons. Doc-To-Help uses the Help target ButtonLabel property to add a related topics heading.

Here is the manual for D2H 2006, in the manual it will give you step by step information regarding converting, and other useful tools to better help your experience with D2H.

http://download3.componentone.com/pub/Documentation/D2H2006v3Manual.pdf

 Hope this helps, please reply if you need more help.

 -Steve

Hi,

Is there a way to deploy d2h within Sharepoint? I know it can be done in the latest version of of Doc-to-help BUT would there also be a way to do this with d2h? Any suggestions advice would be great. I've 'almost' had luck with .mht files but I lose the functionality for the glossary, index and search.

Hello,

Are you refering to the d2h files after they have been created for users to access them within Sharepoint?  If this is the question, then yes nothing has changed from 06 - 08 on this portion of the application.  Please let me know if this is what you were asking, looking forward to your response.

 Thanks,

-Steve