On 07/31/2018 07:53 PM, Matthew R. Trower wrote:
Jon Trulson <j...@radscan.com> writes:
Not a clue. I think ultimately we would want it to generate HTML and
just use a web browser for both help and the guides.
I'd really hate to see that.
* DtInfo is part of CDE.
* DtInfo (like all of CDE) is very lightweight.
* DtInfo provides index and search capabilities (this is a primary
strength of DocBook). Doesn't that sort of go out the window with
HTML?
Well, converting to docbook XML (not html) should preserve all of that
functionality actually. With that, we could generate HTML if we wanted,
or PDF's of the guides, or a variety of other formats. But I don't know
what the cde-specific software like dthelp and dtinfo are actually doing.
There's the format and manipulation of the documentation itself - this
is what I'm talking about.
Then there is the software that deals with it - dtinfo, dthelp, man page
generation, etc. That is what I have little knowledge about.
It might be one thing if we were just starting out with a new
documentation system, but we have rich tooling in place already. Heck,
we already have it all in tree. I believe I understand the general
thrust of moving to out-of-tree XML, but I don't want to sacrifice
quality (e.g. look-and-feel or functionality) in the name of newer,
out-of-tree technology.
I'm not sure what you mean by out-of-tree technology. I do not think
trying to maintain ancient copies of code (nsgmls, et. al) is a viable
solution. No one maintains it.
I'm not suggesting we do away with dtinfo and the like, at least not
initially (until we know a lot more).
I do suggest we offload the utilities portion (like osgmls) to OS
versions and not keep bit-rotting versions in our tree.
I am also for converting the current older SGML document formats to XML
and docbook 5. As to how that affects dthelp/dtinfo, I just don't know
at this time.
I was hoping others here would :)
-jon
At least in the simple case. There is also dtsearch/dtmmdb which fits
into all this somewhere as well.
But a conversion to XML for the documents themselves seems quite
possible with some inevitable tweaking.
This ought to be possible. I would imagine our existing tooling should
basically handle XML DocBook.
-mrt
--
Jon Trulson
"Fire all weapons and open a hailing frequency for my victory yodle."
- Zapp Brannigan
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
