Hello Jürgen,
As was stated in the aforementioned thread, solution 2 can be much
(8x) faster with some xslt optimizations, but I think now we
should outline some roadmap before we start to prepare patches and
so.
Maybe we should convert to XML with DocBook4 at first step?
Then, once we get everything stabilized, we can upgrade to
DocBook5.
Shouldn't we decompose the conversion procedure, so we could
perform fully automatic conversion without any manual changes, and
then fix non-valid situations, you described before?
And one more question - Is conversion to DocBook5 your final goal?
Or maybe you have any further plans regarding documentation, such
as translating it to Deutsch?
Best regards,
Alexander
04.05.2016 17:44, Jürgen Purtz пишет:
Hello,
I measured following elapsed times on an Intel i5 processor:
- generate all HTML files with dsl script (make html): 0:48
min.
- generate all HTML files with xslt script (make xslthtml):
16:01 min.
- generate all HTML files with xslt script in the new
environment (pure Docbook5): 4:07 min.
- Generating different things via dsl scripts in the new
environment may be possible. But the changelog of the Docbook5
dsl scripts shows, that the last modification occurred in 2004
- this way is a dead end.
There is one principle and a lot of minor differences between 2
and 3. Solution 2 is based on an xml-file and xslt scripts which
are based on Docbook4. The basic difference to 3 is, that in 3
everything is Docbook5 compliant: there are only Docbook5 xml- and
xslt-files (as my workflow is: db4 --> xml --> db5 -- (db5
xslt) --> html). The minor differences concerns the fact, that
actually there are errors in my xml files and that I made only a
few parameterisation to the Docbook5
standard xslt files - no optimization at all.
I used following tools: perl, xmllint and xsltproc. osx and
OpenJade are obsolete in the new environment (so far, there is
much more work to do).
Jürgen Purtz
On 03.05.2016 22:13, Oleg Bartunov
wrote: