Hi,
sorry for the long silence.
Yes, olinks were correctly set up, but this boiled down to this:
we used the table (a command parameter list) in more than onle location in
the same document and thus got duplicate id names. I'm currently researching
whether we can switch from Saxon to xsltproc to
Hi,
On Wed, Jul 29, 2009 at 8:28 PM, Bob Stayton b...@sagehill.net wrote:
-snip-
You ask why not just use DITA?. I think there are going to be lots of
answers and discussions about that. Just because someone wants to set their
content up in a modular fashion does not mean they have to use
Hello,
I am currently trying to improve the build time of the documentation of
a free scientific software (Scilab).
There are almost 1800 XML files. The size of these files is between 1 k
to 10 k.
Before calling saxon, some processing is done (mathml = png through
jeuclid, etc) and finally
I'm in full agreement with Bergfrid, keep topic in there, Docbook 5 is
the way to go.
I was also horrified at the comment from Adobe on Docbook 5 support in
Framemaker. But I suppose that confirms that Framemaker is aimed at the
lower end of the market, not for professionals.
Ron
Bergfrid
Sylvestre,
A couple of things may help. Make sure that your catalogs are operating
correctly and that the resolution of them are not going out to the net to
resolve entries. This can slow things down greatly.
Also, have you thought about using XSLTPROC instead of Saxon. I maintain my
Docbook
Hello,
Thanks for your quick answer.
Le jeudi 10 septembre 2009 à 06:59 -0700, DeanNelson a écrit :
Sylvestre,
A couple of things may help. Make sure that your catalogs are
operating correctly and that the resolution of them are not going out
to the net to resolve entries. This can slow
A couple of things may help. Make sure that your catalogs are
operating correctly and that the resolution of them are not
going out
to the net to resolve entries. This can slow things down greatly.
A silly question :). How can I be sure of that ?
The way I usually realize when my
One way is to turn on the verbosity in the CatalogManager.properties file
verbosity=4
Non zero values print debugging info to the screen. This will be of great help
in knowing if all of the net centric info is being resolved to a local
location.
This all assumes that you are using a catalog
Bad luck, it does seems to be related to the network ...
I tried with both and it is pretty much the same time.
I am going the same as you about MathML.
Thanks again for your advices!
Sylvestre
Le jeudi 10 septembre 2009 à 07:57 -0700, DeanNelson a écrit :
One way is to turn on the
Hi,
I get the error
Error: unresolved olink: targetdoc/targetptr = 'clink/clisp-link'.
because I have
olink targetdoc=clink
targetptr=clisp-linkcommandclisp-link/command/olink
and
refentry id=clisp-link ...
in the clink doc.
(other olinks with targetdoc=clink seem to work just fine).
is it
On 10/09/09 13:09, Sylvestre Ledru wrote:
Hello,
I am currently trying to improve the build time of the documentation of
a free scientific software (Scilab).
There are almost 1800 XML files. The size of these files is between 1 k
to 10 k.
Before calling saxon, some processing is done (mathml =
11 matches
Mail list logo
