A

Anonymous

Question

Robo 8 and DocBook

Forum|Forum|17 years ago
August 6, 2009
12 replies
2230 views

Ok who is the expert on converting RoboHelp 8 HTML project to DocBook then using xsltproc and xhtml/docbook.xsl to convert to html files and using the css stylesheet file used for project in RH8 as the styles to be displayed in converted html files. I have successfully converted help project to docbook and used xsltproc and the doxbook.xsl (and other imported xsl files) in docbook-xsl-1.75.2\xhtml to convert to html. I had to add a line in docbook.xsl to provide a link to my css file in final html output. The problem is that formatting does not look the same in the generated html output. I assume because docbook.xsl is not reading all the styles in the original RH8 project source html files.

Customer wants delivery in DocBook xml output so they can convert to various formats using xslt processor. Anybody else dealt with similar issue. Would like generated html output from xslt to look like a webhelp application with same styles I started with in RH8.

HTML

This topic is closed to new replies. Start a new post to keep the conversation going.

A

Anonymous

Hi Jebzoober,

Yesterday afternoon we quit trying. Our developer believes the complexity is not worth the work, and he can work in the files himself (one of the goals) more easily if we keep the document in DocBook format. We agreed, knowing that single-sourcing does not save a lot of writer work given the differences the between our Windows & Linux application versions.

The developer used his XML and coding skills to fix the headers and broken links. His XML skills do not extend to DocBook stylesheet knowledge, and like your situation, his xsltproc did not fix the format issues. If we were to keep the docs in RH, he would have to fix the output after each generation. He’s now working on adding David Cramer’s WebHelp-like styles to DocBook output (see online "david cramer" "webhelp" 2003).

Neil Perlin replied to my questions - he's a consultant at http://hyperword.blogspot.com/- and notes that as far as he knows, the RH XML module was not documented by the eHelp developers before they left Macromedia, and he knows of no other information about what's going on under the RH XML hood.

Direct RH support is unavailable to us right now – someone ordered the wrong product so we can’t register. I called support anyway, using our previous registration. They put me on hold for an hour, and I finally hung up.

If you need any more resource links, I did a lot of research on this. I also have questions out to other experts as well as RH support. If I learn any more, I'll post. Good luck, and if you do find the answer, would you please post. The day may yet come to switch back.

D

dwcramer

Participant

Hi there,

I just ran across this post. I'm the "David Cramer" mentioned above. Unfortunately, the blog post Scott Nisbett wrote that is referred to is very out of date :-) That was an experiment I tried long ago but never found that useful myself.

Converting RoboHELP to DocBook:

I haven't worked with RoboHELP for a while. but if you want to produce DocBook FROM RoboHELP, it's possible but I would only recommend it as a one-time conversion. It can be partially automated but you're converting non-semantic source to semantic markup so it's bound to be a little messy. I doubt it's possible to get clean enough DocBook from RoboHELP.

If you want to create a web-based help FROM DocBook, then you have some choices:

1. Use the DocBook xsls to create HTML Help output (i.e. the .hhp and .hhc files and the html files), then open the hhp in RoboHELP and generate WebHelp from that. I used this trick for years, but it was annoying to have one manual step in an otherwise automatic build process.

2. Have a look at this project. Depending on your requirements, it might work for you: http://www.thingbag.net/docbook/gsoc2010/doc/content/ch01.html (Note: Someday that link will go away. When it does, check out the DocBook Open Repository at sourceforge: http://docbook.sourceforge.net/

Good luck,

David

A

Anonymous

All,

A small tip, in case you missed it also. We gave the RH/Docbook conversion diligent effort and finally gave up. My part was RH source thru Handler Manager. We had the converted files ready to format to WebHelp, but it frustrating. What I didn't know was that the RH XML output corresponded by default to an older DTD version, and that there's a dropdown selector. There might be a better choice than the default. (If this tip contains incorrect terminology, use the concept). We ended up doing as David suggests, using RH for a thorough, one-time edit, and then the SME updated the docbook thereafter for that Help project.

Linda

A

Anonymous

I'm replying to the top level topic, in case you are getting email notifications and would not be notified of my reply to Rick, below.

Captiv8r

Legend

Hi there

Personally, I'd be astonished if your question is answered here. I'm not sure there are very many folks doing this sort of thing.

You might also try posting the question to the HATT list or the Techwr-L list.

Click here to visit HATT

Click here to visit Techwr-L

Cheers... Rick

Helpful and Handy Links

RoboHelp Wish Form/Bug Reporting Form

Begin learning RoboHelp HTML 7 or 8 within the day - $24.95!

Adobe Certified RoboHelp HTML Training

SorcerStone Blog

RoboHelp eBooks

A

Anonymous

Hooray! I'm here. Same problem, same reasons for using docbook. I posted the question, less specifically, to the Other category. I'll check Rick's suggested links, but would you pls post here if you find an answer. We need this thread.

I found that the RH8 output docbook xml itself is not generating styles for the xml below H1.

A

Anonymous

Yes, I noticed that H1 tags are placed in title tags and H2, H3, etc. are put in para tags in the xml output. I assume this is controlled somewhere in the C:\Program Files\Adobe\Adobe RoboHelp 8\RoboHTML\XmlSupportExt xsl files but I have not investigated this yet.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.