[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]



Getting an editor that doesn't scare away the folks you would depend upon to
maintain the documents, & yet deals with arbitrary XML elements & schemata
(that is, something other than *HTML) is not easy, except when it's not cheap.
I have not had sufficient success with doing so in OpenOffice--the steps are
laid out clearly:
<a  rel="nofollow" href="http://xml.openoffice.org/xmerge/docbook/";>http://xml.openoffice.org/xmerge/docbook/</a>
but it didn't entirely work, the last three or so times I tried it (&amp; I had the
same unsatisfactory results using the Text Encoding Initiative DTD &amp; Sebastian
Rahtz's stylesheets).

Conglomerate ( <a  rel="nofollow" href="http://www.conglomerate.org/";>http://www.conglomerate.org/</a> ) is pretty close to what I was
hoping for, but the problem is in my workplace, which is MS, exclusively.

DocBookWiki is pretty interesting:
<a  rel="nofollow" href="http://doc-book.sourceforge.net/homepage/";>http://doc-book.sourceforge.net/homepage/</a>
At the bottom of that page, the related links include demos, such as the
Albanian Constitution (kushtetuta).

Cocoon/Lenya is what I mean to mess with next:
<a  rel="nofollow" href="http://lenya.apache.org/";>http://lenya.apache.org/</a>
I'm wondering if either the BXE or kupu editors will work as I hope.

David Tolpin wrote a What You See Is What You Mean plugin for jEdit, but
withdrew it soon after making it public. Durn. Here, though, is the user guide:
<a  rel="nofollow" href="http://www.davidashen.net/PreTI/jEdit/users-guide.html";>http://www.davidashen.net/PreTI/jEdit/users-guide.html</a>

Grady Harris
Grady Hospital Branch Library
Quoting ale-request at ale.org:

Message: 2
Date: Sat, 20 Aug 2005 21:58:02 -0400
From: Jeff Hubbs &lt;hbbs at comcast.net&gt;
To: ale at ale.org
Subject: [ale] Structured Documentation
To: ale at ale.org
Message-ID: &lt;1124589482.18405.35.camel at angel&gt;
Content-Type: text/plain

I'm looking for open-source ways to generate and maintain structured
documents.

When I say &quot;structured documents&quot; I'm talking about technical or
procedural manuals suitable for printing or screen reading.  I'd like to
be able to create a revision history on a part-by-part basis such that
if I made a change to part 3.1.7, a new version of the entire doc would
be generated and a look back at the previous version would show the
pre-change 3.1.7.  Or, if I selected 3.1.7 and did some kind of history
call-up on it, I'd see the current version plus all previous versions,
their dates, and who modified them.

Anyone know of anything in existence that works close to this?  I've got
an idea in my head somewhere between Lyx and how Gentoo's online XML
docs work.

Jeff



------------------------------

Message: 3
Date: Sun, 21 Aug 2005 08:05:34 -0400
From: &quot;James P. Kinney III&quot; &lt;jkinney at localnetsolutions.com&gt;
To: ale at ale.org
Subject: Re: [ale] Structured Documentation
To: Atlanta Linux Enthusiasts &lt;ale at ale.org&gt;
Message-ID: &lt;1124625934.25626.54.camel at merlin.localnetsolutions.com&gt;
Content-Type: text/plain; charset=&quot;us-ascii&quot;

On Sat, 2005-08-20 at 21:58 -0400, Jeff Hubbs wrote:
I'm looking for open-source ways to generate and maintain structured
documents.

When I say &quot;structured documents&quot; I'm talking about technical or
procedural manuals suitable for printing or screen reading.  I'd like to
be able to create a revision history on a part-by-part basis such that
if I made a change to part 3.1.7, a new version of the entire doc would
be generated and a look back at the previous version would show the
pre-change 3.1.7.  Or, if I selected 3.1.7 and did some kind of history
call-up on it, I'd see the current version plus all previous versions,
their dates, and who modified them.

Anyone know of anything in existence that works close to this?  I've got
an idea in my head somewhere between Lyx and how Gentoo's online XML
docs work.
Sounds like a CVS/Subversion system for documentation to me, Jeff. If
it's written in XML the output can be any format you want. An article in
Linux Magazine
<a  rel="nofollow" href="https://www.linux-magazine.com/issue/30/OpenOffice_Revision_Control.pdf";>https://www.linux-magazine.com/issue/30/OpenOffice_Revision_Control.pdf</a>
may have some ideas.

Jeff

_______________________________________________
Ale mailing list
Ale at ale.org
<a  rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
-- James P. Kinney III          \Changing the mobile computing world/
CEO &amp; Director of Engineering \          one Linux user         /
Local Net Solutions,LLC        \           at a time.          /
770-493-8244                    \.___________________________./
<a  rel="nofollow" href="http://www.localnetsolutions.com";>http://www.localnetsolutions.com</a>

Message: 5
Date: Sun, 21 Aug 2005 15:46:06 -0400
From: Jim Popovitch &lt;jimpop at yahoo.com&gt;
To: ale at ale.org
Subject: Re: [ale] Structured Documentation
To: Atlanta Linux Enthusiasts &lt;ale at ale.org&gt;
Message-ID: &lt;1124653566.3616.3.camel at localhost&gt;
Content-Type: text/plain

Sounds like a Wiki would satisfy all that.  I personally like MoinMoin
as it is written in Python and simply works well.

-Jim P.
Delete | Reply | Reply to All | Forward | Redirect | View Thread | DenyList |
AcceptList | Message Source | Save as | Print
	Move | Copy 	Back to sent-mail   &gt;



</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00325" href="msg00325.html">[ale] Structured Documentation</a></strong>
<ul><li><em>From:</em> volcimaster at gmail.com (Warren Myers)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00323.html">[ale] MySQL Cluster</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00325.html">[ale] Structured Documentation</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00320.html">[ale] Structured Documentation</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00325.html">[ale] Structured Documentation</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00324"><strong>Date</strong></a></li>
<li><a href="threads.html#00324"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>