atw: Re: robohelp is overwriting the XML schema

  • From: "Daryl Colquhoun" <atw@xxxxxxxxxxxxx>
  • To: "austechwriter list" <austechwriter@xxxxxxxxxxxxx>
  • Date: Sun, 15 Jun 2008 21:20:05 +1000

>I am using the RObohelp 7.0 version.
>I generated some files (Webhelp and HTML help) and sent it across the team
>in&nbsp; U.S (Redlands) to incorporate in their existing system.&nbsp;
>When they published the file using their publishing tool the Robohelp is
just
>overwriting the their XML schema and all the format is lost. They can't
find
>a way to fix that up. &nbsp; They use Oxygen XML tool instead of Robohelp.
Is their a way to
>fix&nbsp;this problem, or use the XML editor as the editor in Robohelp

I only have the vaguest acquaintance with Robohelp. However, the above
sounds very odd. If you are generating HTML Help, that would give you a
single file with .chm suffix. And this HTML Help has all its formatting
built into the single .chm file. Maybe the application is simply failing to
link to your .chm file. Check settings.

If you're delivering HTML, you're delivering .htm or .html files, a .css or
two and some image files. While an XML schema is .xsl (or is it .xslt? not
sure) so I don't see how your HTML files can overwrite it. After checking
settings, I think you ought to examine carefully the set of files that you
are delivering to the publishing tool, and the location the tool is writing
to, before and after it does the publishing. This may give a clue to what's
going on.


Emails to this address are automatically deleted unread as an anti-spam
measure.

**************************************************
To view the austechwriter archives, go to 
www.freelists.org/archives/austechwriter

To unsubscribe, send a message to austechwriter-request@xxxxxxxxxxxxx with 
"unsubscribe" in the Subject field (without quotes).

To manage your subscription (e.g., set and unset DIGEST and VACATION modes) go 
to www.freelists.org/list/austechwriter

To contact the list administrator, send a message to 
austechwriter-admins@xxxxxxxxxxxxx
**************************************************

Other related posts: