Robo 8 and DocBook
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.
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.
Similar Messages
-
I'm trying to build xmlto on the Mac and I'm getting errors like:
I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
Anyone been able to actually resolve this?I had been. I found this:
https://wincent.com/wiki/InstallingGit_1.5.2.3_on_Mac_OS_XTiger
But things had changed. The ultimate point of confusion was with:
http://docbook.sourceforge.net/release/xsl/1.72.0.tar.bz2
it did not exist. And when I downloaded what appeared to be the newest version, it was actually just the documnetation. But if you download:
http://sourceforge.net/projects/docbook/files/docbook-xsl/1.75.2/docbook-xsl-1.7 5.2.tar.gz/download
That is the new version. And then changing the instructions in the first link a bit I finally managed to get it all to work. -
dear all,
I want to make package docbook-utils
but have erroe . someone know why?
Making all in HTML
make[2]: Entering directory `/var/abs/local/docbook-utils/src/docbook-utils-0.6.14/doc/HTML'
SGML_CATALOG_FILES=/etc/sgml/catalog
SGML_SEARCH_PATH=../..:../../doc:..
jade -t sgml -i html -d ../../docbook-utils.dsl#html
-V '%use-id-as-filename%' ../../doc/docbook-utils.sgml
jade:../../doc/docbook-utils.sgml:1:55:W: cannot generate system identifier for public text "-//OASIS//DTD DocBook V3.1//EN"
jade:../../doc/docbook-utils.sgml:9:0:E: reference to entity "BOOK" for which no system identifier could be generated
jade:../../doc/docbook-utils.sgml:1:0: entity was defined here
jade:../../doc/docbook-utils.sgml:9:0:E: DTD did not contain element declaration fordocument type name
jade:../../doc/docbook-utils.sgml:11:11:E: there is no attribute "LANG"
jade:../../doc/docbook-utils.sgml:11:19:E: there is no attribute "ID"
jade:../../doc/docbook-utils.sgml:11:34:E: element "BOOK" undefined
jade:../../doc/docbook-utils.sgml:12:11:E: element "BOOKINFO" undefined
jade:../../doc/docbook-utils.sgml:13:10:E: element "TITLE" undefined
jade:../../doc/docbook-utils.sgml:14:12:E: element "PUBDATE" undefined
jade:../../doc/docbook-utils.sgml:16:16:E: element "LEGALNOTICE" undefined
jade:../../doc/docbook-utils.sgml:17:6:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:24:13:E: element "ABSTRACT" undefined
jade:../../doc/docbook-utils.sgml:25:11:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:28:11:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:34:16:E: element "AUTHORGROUP" undefined
jade:../../doc/docbook-utils.sgml:35:13:E: element "AUTHOR" undefined
jade:../../doc/docbook-utils.sgml:36:11:E: element "FIRSTNAME" undefined
jade:../../doc/docbook-utils.sgml:36:37:E: element "SURNAME" undefined
jade:../../doc/docbook-utils.sgml:37:20:E: element "AFFILIATION" undefined
jade:../../doc/docbook-utils.sgml:38:18:E: element "ADDRESS" undefined
jade:../../doc/docbook-utils.sgml:38:25:E: element "EMAIL" undefined
jade:../../doc/docbook-utils.sgml:41:13:E: element "AUTHOR" undefined
jade:../../doc/docbook-utils.sgml:42:11:E: element "FIRSTNAME" undefined
jade:../../doc/docbook-utils.sgml:42:39:E: element "SURNAME" undefined
jade:../../doc/docbook-utils.sgml:43:20:E: element "AFFILIATION" undefined
jade:../../doc/docbook-utils.sgml:44:18:E: element "ADDRESS" undefined
jade:../../doc/docbook-utils.sgml:44:25:E: element "EMAIL" undefined
jade:../../doc/docbook-utils.sgml:47:13:E: element "AUTHOR" undefined
jade:../../doc/docbook-utils.sgml:48:11:E: element "FIRSTNAME" undefined
jade:../../doc/docbook-utils.sgml:48:38:E: element "SURNAME" undefined
jade:../../doc/docbook-utils.sgml:49:20:E: element "AFFILIATION" undefined
jade:../../doc/docbook-utils.sgml:50:18:E: element "ADDRESS" undefined
jade:../../doc/docbook-utils.sgml:50:25:E: element "EMAIL" undefined
jade:../../doc/docbook-utils.sgml:53:13:E: element "AUTHOR" undefined
jade:../../doc/docbook-utils.sgml:54:11:E: element "FIRSTNAME" undefined
jade:../../doc/docbook-utils.sgml:54:41:E: element "SURNAME" undefined
jade:../../doc/docbook-utils.sgml:55:20:E: element "AFFILIATION" undefined
jade:../../doc/docbook-utils.sgml:56:18:E: element "ADDRESS" undefined
jade:../../doc/docbook-utils.sgml:56:25:E: element "EMAIL" undefined
jade:../../doc/docbook-utils.sgml:63:14:E: there is no attribute "ID"
jade:../../doc/docbook-utils.sgml:63:28:E: element "CHAPTER" undefined
jade:../../doc/docbook-utils.sgml:64:12:E: element "DOCINFO" undefined
jade:../../doc/docbook-utils.sgml:65:13:E: element "AUTHOR" undefined
jade:../../doc/docbook-utils.sgml:66:18:E: element "FIRSTNAME" undefined
jade:../../doc/docbook-utils.sgml:66:44:E: element "SURNAME" undefined
jade:../../doc/docbook-utils.sgml:69:10:E: element "TITLE" undefined
jade:../../doc/docbook-utils.sgml:71:9:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:76:9:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:76:21:E: there is no attribute "URL"
jade:../../doc/docbook-utils.sgml:76:57:E: element "ULINK" undefined
jade:../../doc/docbook-utils.sgml:81:9:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:89:9:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:94:9:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:95:19:E: element "ITEMIZEDLIST" undefined
jade:../../doc/docbook-utils.sgml:96:17:E: element "LISTITEM" undefined
jade:../../doc/docbook-utils.sgml:97:15:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:97:28:E: element "APPLICATION" undefined
jade:../../doc/docbook-utils.sgml:101:17:E: element "LISTITEM" undefined
jade:../../doc/docbook-utils.sgml:102:15:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:102:28:E: element "APPLICATION" undefined
jade:../../doc/docbook-utils.sgml:108:19:E: element "ITEMIZEDLIST" undefined
jade:../../doc/docbook-utils.sgml:109:17:E: element "LISTITEM" undefined
jade:../../doc/docbook-utils.sgml:110:15:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:113:17:E: element "LISTITEM" undefined
jade:../../doc/docbook-utils.sgml:114:15:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:117:17:E: element "LISTITEM" undefined
jade:../../doc/docbook-utils.sgml:118:15:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:123:9:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:129:9:E: element "NOTE" undefined
jade:../../doc/docbook-utils.sgml:130:14:E: element "SIMPARA" undefined
jade:../../doc/docbook-utils.sgml:131:12:E: element "EMAIL" undefined
jade:../../doc/docbook-utils.sgml:134:14:E: element "SIMPARA" undefined
jade:../../doc/docbook-utils.sgml:135:12:E: element "EMAIL" undefined
jade:../../doc/docbook-utils.sgml:138:14:E: element "SIMPARA" undefined
jade:../../doc/docbook-utils.sgml:139:41:E: element "ULINK" undefined
jade:../../doc/docbook-utils.sgml:145:24:E: element "CHAPTER" undefined
jade:../../doc/docbook-utils.sgml:146:12:E: element "DOCINFO" undefined
jade:../../doc/docbook-utils.sgml:147:13:E: element "AUTHOR" undefined
jade:../../doc/docbook-utils.sgml:148:18:E: element "FIRSTNAME" undefined
jade:../../doc/docbook-utils.sgml:148:46:E: element "SURNAME" undefined
jade:../../doc/docbook-utils.sgml:151:10:E: element "TITLE" undefined
jade:../../doc/docbook-utils.sgml:153:6:E: element "SECT1" undefined
jade:../../doc/docbook-utils.sgml:154:6:E: element "TITLE" undefined
jade:../../doc/docbook-utils.sgml:156:9:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:156:23:E: element "CITEREFENTRY" undefined
jade:../../doc/docbook-utils.sgml:156:39:E: element "REFENTRYTITLE" undefined
jade:../../doc/docbook-utils.sgml:157:14:E: element "MANVOLNUM" undefined
jade:../../doc/docbook-utils.sgml:160:9:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:161:16:E: element "APPLICATION" undefined
jade:../../doc/docbook-utils.sgml:162:37:E: element "FIRSTTERM" undefined
jade:../../doc/docbook-utils.sgml:163:14:E: element "FIRSTTERM" undefined
jade:../../doc/docbook-utils.sgml:168:9:E: element "PARA" undefined
jade:../../doc/docbook-utils.sgml:170:23:E: element "FIRSTTERM" undefined
jade:../../doc/docbook-utils.sgml:171:14:E: element "FIRSTTERM" undefined
jade:../../doc/refentry/jw.sgml:1:13:E: there is no attribute "ID"
jade:../../doc/refentry/jw.sgml:1:17:E: element "REFENTRY" undefined
jade:../../doc/refentry/jw.sgml:2:10:E: element "DOCINFO" undefined
jade:../../doc/refentry/jw.sgml:3:11:E: element "AUTHOR" undefined
jade:../../doc/refentry/jw.sgml:4:16:E: element "FIRSTNAME" undefined
jade:../../doc/refentry/jw.sgml:4:42:E: element "SURNAME" undefined
jade:../../doc/refentry/jw.sgml:5:18:E: element "AFFILIATION" undefined
jade:../../doc/refentry/jw.sgml:6:16:E: element "ADDRESS" undefined
jade:../../doc/refentry/jw.sgml:6:23:E: element "EMAIL" undefined
jade:../../doc/refentry/jw.sgml:10:10:E: element "REFMETA" undefined
jade:../../doc/refentry/jw.sgml:11:18:E: element "REFENTRYTITLE" undefined
jade:../../doc/refentry/jw.sgml:12:14:E: element "MANVOLNUM" undefined
jade:../../doc/refentry/jw.sgml:15:13:E: element "REFNAMEDIV" undefined
jade:../../doc/refentry/jw.sgml:16:12:E: element "REFNAME" undefined
jade:../../doc/refentry/jw.sgml:17:12:E: element "REFNAME" undefined
jade:../../doc/refentry/jw.sgml:18:12:E: element "REFNAME" undefined
jade:../../doc/refentry/jw.sgml:19:12:E: element "REFNAME" undefined
jade:../../doc/refentry/jw.sgml:20:12:E: element "REFNAME" undefined
jade:../../doc/refentry/jw.sgml:21:12:E: element "REFNAME" undefined
jade:../../doc/refentry/jw.sgml:22:12:E: element "REFNAME" undefined
jade:../../doc/refentry/jw.sgml:23:12:E: element "REFNAME" undefined
jade:../../doc/refentry/jw.sgml:24:12:E: element "REFNAME" undefined
jade:../../doc/refentry/jw.sgml:25:12:E: element "REFNAME" undefined
jade:../../doc/refentry/jw.sgml:26:15:E: element "REFPURPOSE" undefined
jade:../../doc/refentry/jw.sgml:29:17:E: element "REFSYNOPSISDIV" undefined
jade:../../doc/refentry/jw.sgml:30:16:E: element "CMDSYNOPSIS" undefined
jade:../../doc/refentry/jw.sgml:31:14:E: element "COMMAND" undefined
jade:../../doc/refentry/jw.sgml:32:20:E: there is no attribute "CHOICE"
jade:../../doc/refentry/jw.sgml:32:25:E: element "GROUP" undefined
jade:../../doc/refentry/jw.sgml:32:30:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:32:38:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:33:18:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:34:5:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:34:13:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:35:18:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:36:18:E: element "SBR" undefined
jade:../../doc/refentry/jw.sgml:38:25:E: element "GROUP" undefined
jade:../../doc/refentry/jw.sgml:38:30:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:38:38:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:39:18:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:40:5:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:40:13:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:40:45:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:41:18:E: element "SBR" undefined
jade:../../doc/refentry/jw.sgml:43:25:E: element "GROUP" undefined
jade:../../doc/refentry/jw.sgml:43:30:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:43:38:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:43:63:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:44:12:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:44:20:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:44:48:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:45:18:E: element "SBR" undefined
jade:../../doc/refentry/jw.sgml:47:25:E: element "GROUP" undefined
jade:../../doc/refentry/jw.sgml:47:30:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:47:38:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:48:12:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:48:20:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:49:18:E: element "SBR" undefined
jade:../../doc/refentry/jw.sgml:51:25:E: element "GROUP" undefined
jade:../../doc/refentry/jw.sgml:52:5:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:52:13:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:53:20:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:54:12:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:54:20:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:55:20:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:56:18:E: element "SBR" undefined
jade:../../doc/refentry/jw.sgml:58:25:E: element "GROUP" undefined
jade:../../doc/refentry/jw.sgml:59:12:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:59:20:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:59:45:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:60:12:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:60:20:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:60:48:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:61:18:E: element "SBR" undefined
jade:../../doc/refentry/jw.sgml:63:25:E: element "GROUP" undefined
jade:../../doc/refentry/jw.sgml:64:12:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:64:20:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:64:45:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:65:12:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:65:20:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:65:53:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:66:18:E: element "SBR" undefined
jade:../../doc/refentry/jw.sgml:68:25:E: element "GROUP" undefined
jade:../../doc/refentry/jw.sgml:69:12:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:69:20:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:69:45:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:70:12:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:70:20:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:70:51:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:71:18:E: element "SBR" undefined
jade:../../doc/refentry/jw.sgml:73:25:E: element "GROUP" undefined
jade:../../doc/refentry/jw.sgml:74:12:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:74:20:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:74:45:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:75:12:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:75:20:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:75:51:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:76:18:E: element "SBR" undefined
jade:../../doc/refentry/jw.sgml:78:18:E: there is no attribute "CHOICE"
jade:../../doc/refentry/jw.sgml:78:23:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:78:31:E: element "OPTION" undefined
jade:../../doc/refentry/jw.sgml:79:20:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:79:57:E: element "REPLACEABLE" undefined
jade:../../doc/refentry/jw.sgml:79:88:E: element "SBR" undefined
jade:../../doc/refentry/jw.sgml:81:25:E: element "GROUP" undefined
jade:../../doc/refentry/jw.sgml:82:12:E: element "ARG" undefined
jade:../../doc/refentry/jw.sgml:82:20:E: element "OPTION" undefined
jade:I: maximum number of errors (200) reached; change with -E option
jade:../../docbook-utils.dsl:5:73:W: cannot generate system identifier for public text "-//James Clark//DTD DSSSL Style Sheet//EN"
jade:../../docbook-utils.dsl:9:96:W: cannot generate system identifier for public text "-//Norman Walsh//DOCUMENT DocBook HTML Stylesheet//EN"
jade:../../docbook-utils.dsl:15:0:E: reference to entity "STYLE-SHEET" for which no system identifier could be generated
jade:../../docbook-utils.dsl:5:0: entity was defined here
jade:../../docbook-utils.dsl:15:0:E: DTD did not contain element declaration for document type name
jade:../../docbook-utils.dsl:9:1:E: notation "DSSSL" for entity "docbook.dsl" undefined
jade:../../docbook-utils.dsl:17:12:E: element "STYLE-SHEET" undefined
jade:../../docbook-utils.dsl:19:26:E: there is no attribute "ID"
jade:../../docbook-utils.dsl:19:38:E: there is no attribute "USE"
jade:../../docbook-utils.dsl:19:47:E: element "STYLE-SPECIFICATION" undefined
jade:../../docbook-utils.dsl:20:29:E: element "STYLE-SPECIFICATION-BODY" undefined
jade:../../docbook-utils.dsl:32:45:E: element "STYLE-SPECIFICATION" undefined
jade:../../docbook-utils.dsl:33:29:E: element "STYLE-SPECIFICATION-BODY" undefined
jade:../../docbook-utils.dsl:68:44:E: element "STYLE-SPECIFICATION" undefined
jade:../../docbook-utils.dsl:69:29:E: element "STYLE-SPECIFICATION-BODY" undefined
jade:../../docbook-utils.dsl:113:29:E: there is no attribute "ID"
jade:../../docbook-utils.dsl:113:48:E: there is no attribute "DOCUMENT"
jade:../../docbook-utils.dsl:113:61:E: element "EXTERNAL-SPECIFICATION" undefined
jade:../../docbook-utils.dsl:115:13:E: end tag for "EXTERNAL-SPECIFICATION" omitted,but its declaration does not permit this
jade:../../docbook-utils.dsl:113:2: start tag was here
jade:E: specification document does not have the DSSSL architecture as a base architecture
jade:E: no style-specification or external-specification with ID "HTML"
DocBook Utils
18 June 2000
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Version 1.1 or any later version published by the Free Software
Foundation. A copy of the license is included in the section
entitled "GNU Free Documentation License".
This documentation describes the DocBook-utils version
0.2.
The DocBook-utils are a collection of various utilites to
convert and analyse SGML documents in general and DocBook files
in particular. They are developped by many authors and released
under GPL licence.
Eric Bischoff
[email protected]
Jochem Huhmann
[email protected]
Steve Cheng
[email protected]
Frederik Fouvry
[email protected]
Eric Bischoff
Introduction
The DocBook-utils are a collection of various utilites to
convert and analyse SGML documents in general and DocBook files
in particular. They are developped by many authors and released
under GPL licence.
DocBook
is a SGML-based or XML-based standard for writing technical
documentation defined by the DocBook Technical Committee of the
OASIS consortium.
The DocBook-utils try to be as general as possible, and
therefore it is possible to use them with other SGML formats
than DocBook, like TEI or HTML. But each time there was an
opportunity to make them biased to DocBook to ease the life of
DocBook users, this opportunity has been given a higher priority
than generality considerations. This is why this package is not
called "SGML-utils".
The DocBook-utils are independant of any existing distribution
of SGML parsers and of DocBook resources. However, they conform
with the new draft on SGML and DocBook standardization being
discussed at Linux Standard Base project.
So far, the DocBook-utils only consist of:
jw, a script used to convert
from DocBook or other SGML formats into "classical" file
formats like HTML, man, info, RTF...
sgmldiff, a script used to
compare the markup of a SGML file with its translation into
another language.
but we would like to see them accomplish other tasks in the future:
Conversion from "legacy" formats like LinuxDoc, man,
info, HTML or PDF into DocBook.
Refined analysis of DocBook files like a "sgmlgrep"
program that would allow context-sensitive searchs.
Support for XML.
If you want to help or keep informed of the latest developments,
please subscribe to the "[email protected]"
mailing list. This list has been set up to allow collaborative
development of these
tools.
To subscribe: Send a message to
[email protected]
- you will get a confirmation message, just reply to it.
To unsubscribe: Send a message to
[email protected]
and reply to the confirmation message
For any additional information, write to Jorge Godoy who is
the maintainer of this list.
Jochem Huhmann
jw
Command reference
jw
1 converts DocBook or other
SGML-based formats into "classical" file formats.
The modular architecture used by
jw allows to write plug-in
programs (we call them backends and
frontends). The backends are specific to
output formats while the frontends are specific to input formats. We
would like to encourage you to write such programs and to submit
them to the docbook-utils project.
While most backends are based on Jame's Clark Jade, or its
OpenJade alternative, some of the backends make use of the programs
from the docbook2X project. We call these
helper programs.
Eric Bischoff
[email protected]
jw
1
jw
docbook2dvi
docbook2html
docbook2man
docbook2pdf
docbook2ps
docbook2rtf
docbook2tex
docbook2texi
docbook2txt
(Jade Wrapper) converts SGML files to other formats
jw
-f
frontend
--frontend
frontend
-b
backend
--backend backend
-c file
--cat file
-n
--nostd
-d
file|default|none
--dsl
file|default|none
-l file
--dcl file
-s path
--sgmlbase path
-p program
--parser program
-o directory
--output directory
-V
variable[=value]
make[2]: *** [api.html] Error 1
make[2]: Leaving directory `/var/abs/local/docbook-utils/src/docbook-utils-0.6.14/doc/HTML'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/abs/local/docbook-utils/src/docbook-utils-0.6.14/doc'
make: *** [all-recursive] Error 1
ERROR: Build Failed. Aborting...
==>[root@lion docbook-utils]#Hello,
is there any solution now?
Because i need doocbook-utils.
I hope so :-D -
Robo v9 Show/Hide without Twisties - One button no longer working
Hey there, as stated I am using Robo v9 with Show/Hide without Twisties (One button) with javascipts. We have most of our images using DHTML drop-downs and when folks click on "Show All Images" on the page, the GIF changes to "Hide All Images" and all drop-downs (our images) and expanding text are diaplayed.
It had been working all the time, but now it only works when I right click the topic in the TOC and choose "Edit Topic", then while in the Edit Window (Display view), when I do a View (Ctrl-W) and it displays the page within RoboHelp..I can click the "Show All Images" and it works like it always had. BUT, if that page is not in the Edit Window, and I right click "Preview Topic", the click "Show All Images" (or on the DHTML dropdown itself) it will NOT show the images, *but the GIF image does properly toggle to "Hide All Images" (and if I do again, then it properly toggles to the "Show All Images" GIF, if I do it again), but now NO images are getting displayed for some reason. It also NEVER works properly when I publish to our website (even when clicking the DHTML dropdown itself), but the GIF images toggle properly.
If I right click and choose "Preview Topic" and click "View With" and use Internet Explorer 8 it still never works anymore, unless the topic is in the Edit Window (Display View), so I know the issue is not on the server. It stops working after I do a generate and run on my pc. Also when I view it IE8 within Robo (and Allow the Blocked Content to run the scripts), many instances of the same error is shown as:
Message: Access is denied.
Line: 2646
Char: 3
Code: 0
URI: file:///D:/Users/_RBH9_TPO-Generate/v9-testing/ehlpdhtm.js
...but I *do* have access to the folder system, but in checking the coding of the ehlpdhtm.js, that area show, where I believe line 2646, character 3 starts at the "values = getAttribute(element, prop );" line below...but maybe something does not exist:
==
//End HTML code invoked function
function InitEffect( element, prop )
var values = null;
if( getAttribute(element,prop))
values = getAttribute(element, prop );
else if( getAttribute( element, "currentStyle" ) && element.currentStyle.getAttribute)
values = element.currentStyle.getAttribute( prop );
else if (element.style.getAttribute)
values = element.style.getAttribute( prop );
if( !values )
return;
var functions = new Array();
==
I have a much older backup when restored, it all works properly again in all cases, but I have done so much work since then that I think would need to be manually redone. I have played with keeping those some javascipts alone (in case I changed something) and updated the rest of the data files I had added, deleted the .CPD file, but it somehow stops working again, probably with some updated file. I am not sure what specific files could be causing the negative impact that is preventing it from working. Maybe if I knew what files could impact, I couldrestore those from my old backup. The newer backups when restored do not work properly, so there was a point in time where something changed and is causing this.
All prior versions of RoboHelp (v7 and v8) have always worked and still do. I am using v9.0.1.262, as the latest version has not yet been allowed on our pcs (per security), but since my earlier backup works, I thought it may not be the issue, but wanted to tell you anyway. ;->
Any ideas on how I should proceed? What files may have impact to cause it not to work anymore? The showhide.js is the only .js to show up as a baggage file. Also, the DHTML line does exits in each html page's code, as we are still using Robo v7 as the production software and the Show/Hide always works, and I copy them into the respective Robo v9 folders (and if new, then I copy them, then import them), otherwise the newer v7 updated pages are copied over the older v9 html files while RoboHelp is closed.
Thanks in advance for any info you can provide!I may have figured out what to fix to get v9 back to working on the Show/Hide button, but not the "why?" .
It looks to all be dealing with the Robo automatic html coding of where to locate the .js file(s)...here is a quick overview of this issue and what I did. When I view the non-working pages within Internet Explorer 8 within Robo (and Allow the Blocked Content to run the scripts), I saw many instances of the same error is shown as this in the log, which implied since I *do* have access rights, maybe the file was just not being found.
Message: Access is denied.
Line: 2646
Char: 3
Code: 0
URI: file:///D:/Users/_RBH9_TPO-Generate/v9-testing/ehlpdhtm.js
OK, here are my findings. EXAMPLE #1 and EXAMPLE #2 below are excerpts of the same file. EXAMPLE #1 is from Robo v7 and is copied to the v9 folder after it was updated so our soon to be "production" webhelp will be from Robo v9 (instead of making the same manual updates in Robo v9 as in Robo v7, I copy the updated the .html file to the Robo v9 file system). Note the direction of the directory slashes of the java scripts listed below, as they are all DOS type slashes (back slashes), EXCEPT for ehlpdhtm.js as it is the ONLY one using UNIX (forward) slashes.
EXAMPLE #1 (from Robo v7)
==
<link rel="StyleSheet" href="..\..\sty-std-topic.css">
<script type="text/javascript" language=JavaScript x-save-method=compute-relative
src="..\..\showhide.js"></script>
</head>
<body>
<robohelp><script type="text/javascript" language=JavaScript1.2 src="../../ehlpdhtm.js"
x-save-method=compute-relative></script>
<script type="text/javascript" language=JavaScript1.2>
<!--
if( typeof( InitEffects ) != 'function' ) InitEffects = new Function();if( typeof( InitTrigger ) != 'function' ) InitTrigger = new Function();if( typeof( FilePopupInit ) != 'function' ) FilePopupInit = new Function();if( typeof( TextPopupInit ) != 'function' ) TextPopupInit = new Function();
//-->
</script>
==
EXAMPLE #2(from Robo v9)
This is from the restored backup of the Robo v9 files that always work when I restore them, and note they are ALL UNIX (forward) slashes. These backup files were generated from Importing/Upgrading a copy of the Robo v7 files into Robo v9.
++
<title>[Endpoint Protection] Symantec Overview</title>
<link rel="StyleSheet" href="../../sty-std-topic.css" type="text/css" />
<script type="text/javascript" language="JavaScript" src="../../showhide.js">
</script>
</head>
<body>
<?rh-script_start ?><script src="../../ehlpdhtm.js" type="text/javascript" language="JavaScript1.2">
</script><?rh-script_end ?>
++
Additional info: The following is from another file from the Robo v9 backup files that always WORK and once again they are ALL UNIX (forward) slashes.
~~
<link rel="StyleSheet" href="../../sty-std-topic.css" type="text/css" />
<script type="text/javascript" language="JavaScript" src="../../showhide.js">
</script>
</head>
<body>
<?rh-script_start ?><script src="../../ehlpdhtm.js" type="text/javascript" language="JavaScript1.2">
</script><?rh-script_end ?>
~~
BUT since all .js files are referenced in EXAMPLE #1 have DOS slashes (back slashes), EXCEPT for the ehlpdhtm.js, I decided to change the line in ehlpdhtm.js FROM src="../../ehlpdhtm.js" TO src="..\..\ehlpdhtm.js" and IT (this one page) BEGAN WORKING AGAIN after I published. So having all DOS back slashes DOES work in Robo v9!!!! BUT it appears that Robo v9 only generates new pages using UNIX (forward) slashes in ALL coding. I've read about issues like this occurring with the FireFox browser, but we only use IE8, and have not read anything like this related to IE8 issues.
So if all UNIX forward slashes and all DOS back slashes can work in Robo v9 in finding and using ehlpdhtm.js, (the Show/Hide buttons function properly) why is this problem existing in Robo v9 when there are mixed "slashes" (using forward and backward)? ...and the mixed slashes ALWAYS works in Robo v7! They do not have to all be in the same direction in Robo v7 as it appears to have to be in the newer/more advanced Robo v9. Why does it matter that all slashes need to be all the same direction, if Robo v9 CAN actually read and figure out the DOS back slashes (formatted by Robo v7 creation) and actually generates UNIX forward slashes for the .js files in new Robo v9 output within the .html?
More importantly will I have to always do a Global search and replace in Robo v9 to change the direction of the "back slashes" when I copy updated Robo v7 .html files into the Robo v9 folders (instead of manually reworking each change), while in transition from v7 to v9?
Thanks in advance any information, recommendations, and feedback as your time is greatly appreciated! -
I imported my word .doc file into robohelp to start the
project.
When I went to the HTML files to start the changes, I found
that the converter had given me a perfect copy of my word
formatting including putting margins in inches and "no page break
instructions in my tables.
The css file is about eight pages long!!!
To make things worse: not all of the formatting is in the
style sheet. Every table has cell padding and every list item is a
paragraph with a list having a class tagged with my Word
formatting.
I am looking for any tips or tricks to make this cleanup
easier, either before I convert it from word or after.
I would be interested both in people's individual techniques
as well at any site with tutorials or lists of techniques.
Thanks,
MarjorieMarjorie, for what it's worth, I have experienced the same
thing trying to import a complex document into RH. So I kind of
reverse-engineered the process. For documents in Word that I want
to put into RH, I just design a style/CSS sheet in Robo and then
cut/paste the material into RH. It's not as "easy" of a method as
importing in that it does take a little longer and you do have to
reconstruct tables. However, I end up with much much cleaner HTML
and a better output.
For what it's worth, documents that are really complex (with
an complicated .dot style sheet, TOCs with more than one or two
levels/corresponding headings, and things like text boxes or frames
and captions) really do not import well directly into RH. A lot of
my Word docs are highly structured and the structures themselves do
not necessarily go straight into a clean CSS/HTML. I've had much
better luck directly importing simpler Word docs (uses only level
headings 1 and 2, perhaps a couple of tables, no complex TOC, no
captions, textboxes, or frames). -
Okay - so I am ignorant - lets get this out upfront. I inherited Robo, and enjoy working it in, but I'm still ignorant.
We're splitting our emars KB into two, and it appears the way it was set up everything is under the LocalCopies folder > sub-directory emars. However, what are these folders off root under emars? Is this for source control? We just copied the folders under LocalCopies, and everything seems to be working fine (same web server, just a different folder name), but I want to make sure something isn't going to come bite me in the butt.
Many thanks - AnahidHi,
While generating a Robohelp project, by default the tool generates folders !Language!, !SkinSubFolder!, and !SSL!. All other folders are manually created by the author based on their convenience/ logics (such as grouping of topics within a single business process/main heading) of maintaining the folder structure for easy retrieval of HTML files. Thus, in the sample image provided folders Chapter 1_XXXXX to Cahpter12_XXXXX were created by the author of emars for ease of folder maintenance.
The !Language! folder contains details related to the Language and !SkinSubFolder! contains details about the skins settings used in your respective project. !SSL! (Single Source Layouts) is the default folder where all the output files you generate are saved.
With the Task Support Cluster concept gaining its momentum, as a practice folder structures can be maintained as Concept, Tasks or Procedures, and References.
Concept – In this folder place all the files that provide an overview, insight, what can be done in this page, or any other conceptual information a user must know to perform the task effectively.
Tasks or Procedures – In this folder place all the HTMLs which tells the user how to perform a task.
Reference Topic – In this folder place all the topics which provides additional information to the user or topics which the user might require to know.
Thanks,
MS -
Document validates but NoName is generated when opening
Hi all,
We have an xDocbook structured app based on Frame 11 and Docbook 4.2. It has been stable until the last week or so. Here are the changes we made to the structured app recently:
1. Added some functionality to the EDD including some Format Change Lists and attribute values, but nothing that seems major. The EDD validates and does not produce errors when its element definitions are imported into a document.
2. Added support to the DTD for an equation element to be allowed inside a line element
3. No edits to the rules.
4. In structapps.fm, we turned off "Try Alternative Extensions"
5. In the template, we added or tweaked some styles.
We retain our documents in XML and open them in Frame only to edit them.
However, each time we open any document in Frame now, a NoName element wraps whatever the top-level valid element is, whether a <chapter> or <appendix>. I can unwrap it and the document validates using the Element | Validate feature. I save and close the document. If I open the XML in a text editor, its top level element is <chapter>. There is no <NoName.> But if I open it again in FrameMaker, NoName is generated again at the top of the hierarchy. This is true even for documents that we have not edited or touched in months, so it cannot be the content itself; it must be something with the structured app.
To test, I have reverted the EDD back to a timeframe when it was known to have worked properly, and imported it into the template, then reopened the documents. This is problematic of course because the documents currently contain attribute values that were not supported earlier, so Frame complains about these when I validate. But the NoName element is always created no matter how far back I go with the EDD.
Finally -- and particularly strange -- is that I revert the EDD to an earlier, known stable version, import it into the template, and open some documents that we have not edited in months -- thus, recreating an environment that worked before. Still, NoName is generated. I have not yet reverted the changes to structapps or the DTD and will try that next -- but I don't see how those could be the issue.
So the questions are:
1. What would make Frame generate a NoName element for a document that has valid structure?
2. What can trigger the generation of a NoName element?
Thanks for any help!
Shelley
Shelley Hoose
Sr Doc Developer
Rogue Wave SoftwareShelley,
If the main flow in your template has content when you open an XML document, FM places the content of the XML document after the existing content. It then creates a NoName element to hold these two content segments. It's fairly easy to insert something like a space by accident into a template--something that's there but not visible. If you then open an XML document with <chapter> as the document element, the result will be a space followed by the chapter. Since the structured flow must have a root element, FM creates a NoName element.
This doesn't seem to be quite your situation, since in the case I just described, you won't be able to unwrap the NoName. Your case, though, may have been some variation of such a situation. By the way, if your template contains a paragraph break (caused by unintentially pressing Return), FM does not create a NoName. With this variation, NoName is not needed since FM discards end-of-paragraph characters at element boundaries when it is manipulating elements.
--Lynne -
Word styles not appearing in Print Document Appearance dialog
My custom list styles in Style Mapping.dot are not appearing in the Print Document Appearance dialog when I try to map CSS styles to Word styles.
The styles do appear in the template when I open it in Word. They appear in the styles task pane whether I select "In current document" or "In use" in the Style Pane Options dialog in Word. The styles have the same name (such as "Bullet" or "Number") in Word as the CSS styles in RoboHelp.
I tried saving Style Mapping.dot as .dotx, thinking that RoboHelp 8 might work better with the current template type, but no help. I tried adding the template to the same folder as the Normal.dotm template is in and opening it there. No improvement.
Oddly, the built-in Word styles List, List 2, & etc and List Continue and its series appear in the Robo dialog, but the styles List Bullet and others in that series do not appear.
I suppose I could modify the list styles that do appear in Robo and map them to my CSS list styles, but that feels a bit like a desperate kluge.
Does anyone know what might be wrong, either with my Word template or with Robo, that might be causing what seem to be perfectly good Word styles to not present themselves for mapping?
Thanks again,
JohnPeter,
I think your discussion of this problem could explain the situation and propose a workaround more simply than it does.
Based on your article, I assumed that Robo displays only the built in Word list styles such as List and List Continue (since those were the only styles showing up in the style mapping dialog and since your example shows matching a Robo style named List Mapping to a Word built in style named List). I assumed I would have to match my Bullet style to a style named List in Word, and match the indented bullet style to List 2, and so on. The actual situation is that Robo, for some godforsaken reason that only idiots would understand, will not show a Word style if any numbering (bullets or numbers) is applied to it. That is, one does not have to avoid a class of styles called “List styles”, one only has to avoid applying numbering to the styles until later.
Thus the workaround is to create the word styles (with names that match the Robo styles!) that contain every attribute you need EXCEPT the numbering. That is, I can link Bullet to Bullet and Number to Number and Indented Number to Indented Number, and so on and on, as long as I have all the Word styles in the template with their numbering set to None.
Then after I generate the document, I can modify the styles to add the appropriate numbering, and voila!
Currently scrolling the doc & modifying styles. Might be a glimpse of daylight.
John
From: Peter Grainge [email protected]
Sent: Thursday, October 13, 2011 8:47 AM
To: John Dawson
Subject: Word styles not appearing in Print Document Appearance dialog
Re: Word styles not appearing in Print Document Appearance dialog
created by Peter Grainge<http://forums.adobe.com/people/Peter+Grainge> in RoboHelp - View the full discussion<http://forums.adobe.com/message/3969382#3969382 -
RH7 not saving or generating Webhelp
Have been using RH7 since November 2007 and presently have 4
projects active. OS is Windows XP Pro running MS Office 2007.
Approx 1 week ago RH suddenly stopped saving my Word docs and as a
consequence of this, will not allow Webhelp generation.
Looking at other forums I am not the only user encountering
this problem but nobody seems to have a definitive answer. I have
tried all of the suggestions posted as follows:
- Repair RH7
- Repair Office 2007
- Uninstall RH7
- Re-install RH7
All to no result
RH7 was installed AFTER Office 2007 (which was one of the
suggested reasons for the problem)
In short, I am getting desperateHi Peter. Thanks for getting back to me. I'll answer your
questions and tell you where I'm at...
I have alerted Adobe to this. Can you run without Live Messenger
for a short while just as a test. Doubt that is it but we need to
rule out all possibilities.
Tried that (saw the post on anything that might be touching
Word could cause the problem). I actually stopped running every
single thing--sidebar, IE, Outlook, Messenger, Defender, everything
in the task bar. Didn't help.
Does it drop out if you close RH and immediately re-open it?
Yes.
Do you have any Office 2003 components on your PC? Running or
not?
Not as far as I can tell. Here's all my MS OS/software stats:
- Windows Vista Enterprise version 6.0 (Build 6000) patched
to the latest level, including all optional updates from
Update.Microsoft.com.
- Office 2007 Enterprise (Word itself is at: Word 2007
version 12.0.6212.1000 SP1 MSO (12.0.6213.1000),
- Windows Live Messenger 2008, version 8.5.1302.1018.
- Visual SourceSafe 2005 version 8.0.50727.42
- Visual Studio 2005 version 9.0.21022.8 RTM
- .NET Framework version 3.5
- IE 7 version 7.0.6000.16575
Have you installed Vista SR1?
No, but I do have all the latest patches from the Update
site.
Where I am now:
After trying all the things I saw online, to no avail, and
discovering you can't write a macro to programmatically load the
Dll (you can load Wll files...), I uninstalled Robo & Office
completely, and scrubbed the registry by hand, followed by a
shutown/pause to clear all memory. Then, I followed the last bit of
advice I saw, I installed RoboHelp FIRST, then Office 2007.
RoboHelp is CURRENTLY working, though I haven't touched a
single "Word Option" yet and I have a couple of the harder tasks to
put through the paces.
I do need to turn off/on a few options, such as AutoCorrect
(off), but I will not touch the save/convert/open options this
time. (I had made my standard options settings, but changed them
back when I was troublshooting, to no avail.) I will be switching
an option at a time, in case there is a spurious side effect that
hoses Robo. (If I find such a beastie, I'll be letting you know...
/grin/.) If this goes well, I will be
stripping/scrubbing/re-installing my co-worker's system this
afternoon with the same procedure and seeing if I can get the same
results. I will let you know. The co-worker did NOT touch any
options, so it's just install order on his machine (he's not
running IE or Messenger while in Robo and still experiencing these
problems).
I did not expect this to work--it makes little to no sense to
have the install order have such a dramatic effect on the ability
to retain a COM add-in registration. I only tried it out of due
diligence. Go figure. :)
I'll let you know the results. Let me know if you need any
more specifics to help feed Adobe information.
Cheers!
~~dmarie (volt) -
Trouble with MergeFormat tags appearing in Word doc
Hello! I have been living with this problem for ages, and
just manually deleting them. But, I now have a new coworker who
does not get the same problem when we single-source the same
project to Word.
When I create a single-source Word document, before each
topic heading in the newly generated Word doc, I get a tag like
this: { XE "GPA:setting up" \MERGEFORMAT} I get one for each index
entry for the topic. I do not generate an index when I generate
printed docs. I'm trying to figure out where to get rid of these.
It looks like a Word setting. My coworker and I have looked at all
of our options in both Robo and Word, and can't seem to find which
one made hers go away.
I use RH7 and Word 2003.
Any ideas? Thank you for your help in advance.Sorry - I think I figured it out. I have to look at
formatting (Show/Hide Formatting) when I use Word, she does not. I
see now that the index entry tags don't print when you print the
Word docs (so I don't need to delete them) - but they are ugly to
look at as you are editing! Not sure if there is any other way to
view all other formatting marks without those. As long as I don't
have to delete them all anymore, and they don't appear in the
printed docs, I'm happy.
Thanks anyway. -
Best practices for TOC, versus PROJ title, filename
I am seeking "best practice" help from the forum. Say a TOC
is to have numbers as part of the organization, 1,2,3...and topics
will be sub-numbered (as in 1.1, 1.2.1, 1.2.2, etc). I am not aware
of any way to automatically manage this, they must be explicitly
typed in the TOC editor.
I have heard some say that the "view" in the Project should
mirror the view in the TOC. That would imply that folder
organization, filenames and titles would be in sync with the TOC,
and also include the section/chapter numbering.
If you have to make a change and resequence things, or insert
a new chapter between 2 and 3 then there is a LOT of work to do.
I am leaning in the direction of having filenames and titles
be separate from the TOC structure, and not use Field[title] in the
documents to simplify the update process. This would also simplify
updating links within the documents.
However, I am still pretty new with Robo and don't have the
seasoning some of you have with long term effects of particular
organization.
Any help, or best practices that can be shared?
Thanks!
DonThanks for your input Colum,
I am actually considering the opposite of your comment - to
have numbering in the TOC but NOT with the Project folders. I
consider the TOC much more volatile and flexible than the folder
structure. As long as one knows what goes with what. So the good
news is there is not a sacrosanct line drawn between the project
names and structure and that in the TOC. This helps. If I have to
resequence section 2 and section 5, I mainly just change the TOC. I
would not have to move or rename any folders in the Project view.
The other part, using the document title (in the topic
properties) to automatically update the topic title in the text I
like quite a bit and I think can make the case with my peers. That
offers a lot of flexibility. As in the above mentioned
resequencing, I would have to access the properties for each topic
in the project folder that used to be in section 2, and edit the
document title to reflect its new position in section 5 (and vice
versa). That is pretty straightforward. I do NOT have to rename all
those folders and files in the Project view.
Thanks again for chiming in.
Don -
SEARCH results - shows file name. Can I change this?
I am using TCS2 in Windows XP.
In Robohelp when you search the online help, it brings back the search results but they are displayed under the filename heading. Can I change that? I don't necessarily want my filename displayed to users... maybe the Chapter name?
TIA
-AdrianaHi--
I have no solution yet but am having very much the same problem, and would like to get in on this conversation while I continue experimenting. I'm working TCS2 (Frame 9 and Robo 8), linking the Frame book to Robo to create CSH. I'm a long-time Framer but a newbie to Robo and TCS2.
As far as I can tell from reading through the thread, I've got some kind of variation going: some of my CSH Search results show the heading, and some show the filename. I haven't yet discovered what is the difference in the Frame file, although I believe that's where I'll find it. It's consistent from search to search. (That is, if it a topic shows up in Search results as the filename once, it does so consistently. Ditto others showing up as the heading.)
In addition to hereby signaling moral support (!) and an interest in a solution, I'd like to provide my settings here and see how yours compare.
The marker I created to manage output CSH filenames is "FileName." I'm working with engineers who are not native English speakers and have never implemented CSH. For the 30 or so (out of 75) topics that actually are going to be linked from the application, I created FileName marker text that starts with "LinkTo_<menupath>." (Example: "LinkTo_WebSecurity_ServerSecurityGroups_Adding.") The idea is to help them see what to link up where. (It also made editing map IDs faster: I just select and automap any topic name starting with LinkTo_.)
So I'm getting Search results that look like this:
Things to know about xyz
text text text...
LinkTo_Statistics_Events
text text text...
My "File > Project Settings > Edit conversion settings... > Other" settings are:
Context Sensitive Help Marker: blank
Topic Name Pattern: grayed out but is "(Default)"
Topic Name Marker: FileName
Not sure this is optimum. (As I said, a Robo newbie.) Also, my chapter titles and H1 thru H3 are set up to paginate, although I realized later that filling Topic Name Marker field disables pagination.
Thanks, will keep working on it --
Anne -
After upgrading from 7 to 8 my iPad 3 will freeze using email, safari, games. I never ever had a problem before this upgrade. Have done all the temporary suggestions but nothing is a permanent and will come right back. I am so sorry that I upgraded, can not go back. I really want to thank the IOS guys for screwing everything up. Seems like old times with the Microsoft Tech guys. I have no problem with my iPhone 6 Plus phone.
It seems to be caused by roboform 7.5.1. I upgraded to the latest version of robo and it's working now. Sorry mozilla, not your fault.. very frustrated.
-
After upgrade to 8.0 FF crashes every time I try to start it, even in safe mode
I guess the automatic upgrade happened last night (i hate that you auto upgrade btw) and now FF at work crashes every time I try to open it. I've had problems with FF ever since 7.0 came out. Please fix these problems because FF is almost unusable now :( So sad it is such a great program that has been ruined now
It seems to be caused by roboform 7.5.1. I upgraded to the latest version of robo and it's working now. Sorry mozilla, not your fault.. very frustrated.
-
Will other applications become available for Cloud subscription?
So I have the Adobe Creative Cloud subscription (student price) going, and so far all seems to be working well. The price is right and I much prefer the subscription model over buying outright.
However I'm more interested in the applications from the Technical Communication Suite that aren't part of this package; RoboHelp, Captivate, FrameMaker. I'm looking to change careers and am back in school. I could really benefit from learning and becoming certified in these applications. Robo and Frame don't even have student pricing at present. Even if they did, they would most likely be cost prohibitive for me to purchase outright.
Now I could make use of the 30-day trials for each, doing them one at a time and trying to learn as much as possible in a month. That might be enough to learn my way around and get my feet wet, and possibly even enough to pass a certification exam. That said, I'd much rather have access for a longer period in a subscription model similar to the Creative Cloud. The level of integration between these applications makes it important to have them all available at the same time.
The purchase price of some of those applications and suites might be fine for commercial clients, but an absolute non-starter for students who need to learn them. A month trial simply isn't long enough. On the other hand, the Cloud subscription model seems perfect for this. Someone like me could join up for a year or so, become comfortable with the applications, and then stop subscribing once employed by a company who licenses these applications. Or, perhaps then I might have a justification to purchase them for contract work and the like.
I was wondering if Adobe has any plans in the pipeline as far as making these other applications available under this Cloud model .
Thanks,
JThe new TCS4 suite is available for subscription now:
http://www.adobe.com/products/technicalcommunicationsuite/upgrade.displayTab3.edu.html
$69/month for a year commitment or $99/month. It's a tougher proposition at $70 as (for now) I'd just be using them to learn on and have 2 of the 5 apps via the Creative Suite. Student pricing would help.
In any case, the option is now at least available, just sharing a link.
Maybe you are looking for
-
Printing specific Excel worksheets from ePrint on Iphone
I'm attempting to print selected pages from an Excel file via HP ePrint v5.2.1 software on my IPhone 3GS, created by Docs ToGo. I can get the software to see the file, even show me the second worksheet, which I want to print. I can save it as a Doc
-
Upgrade graphics on T43 with Intel Integrated adapter?
Machine type is 1871-4AU. Can I upgrade the graphics? If not, is there anything like a list somewhere of the upgrades I can do? I would also like to add a dvd burner. I like the machine and have now dumped about a hunded bucks in memory and new k
-
Standard program for uploading budget values in expenses
Hi Experts, can u please tell me the standard program to upload budget values in Expenses thanks & regards.. Narendra
-
The error message is below and its been the same on firefox, chrome and internet explorer on my same computer. All the cookies are on and accpeted on all three. There shouldnt be a reason why Im getting this still, help! cuyamlp We detected that the
-
I'd appreciate some help and assistance re RSS. I've been working on some web pages and would like to add an RSS feed to them. I've decided to use a service called 'feeddigest.com (www.feedigest.com/). They offer five free feeds and that's more than