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

[no subject]



Also, I don't completely understand how they've implemented it, but Rice 
University's Connexions Project (<a  rel="nofollow" href="http://cnx.rice.edu";>http://cnx.rice.edu</a>) uses Plone for their 
CMS, and all of the published modules are written in their schema, CNXML. 
The items published have full version histories, too.

WMM

On 8/22/05, gharri2 at emory.edu &lt;gharri2 at emory.edu&gt; wrote:
&gt; 
&gt; Shoot, this is one of those perpetual projects that I never get far along 
&gt; on. In
&gt; my messing around, though, I've found a few things.
&gt; 
&gt; Getting an editor that doesn't scare away the folks you would depend upon 
&gt; to
&gt; maintain the documents, &amp; yet deals with arbitrary XML elements &amp; schemata
&gt; (that is, something other than *HTML) is not easy, except when it's not 
&gt; cheap.
&gt; I have not had sufficient success with doing so in OpenOffice--the steps 
&gt; are
&gt; laid out clearly:
&gt; <a  rel="nofollow" href="http://xml.openoffice.org/xmerge/docbook/";>http://xml.openoffice.org/xmerge/docbook/</a>
&gt; but it didn't entirely work, the last three or so times I tried it (&amp; I 
&gt; had the
&gt; same unsatisfactory results using the Text Encoding Initiative DTD &amp; 
&gt; Sebastian
&gt; Rahtz's stylesheets).
&gt; 
&gt; Conglomerate ( <a  rel="nofollow" href="http://www.conglomerate.org/";>http://www.conglomerate.org/</a> ) is pretty close to what I 
&gt; was
&gt; hoping for, but the problem is in my workplace, which is MS, exclusively.
&gt; 
&gt; DocBookWiki is pretty interesting:
&gt; <a  rel="nofollow" href="http://doc-book.sourceforge.net/homepage/";>http://doc-book.sourceforge.net/homepage/</a>
&gt; At the bottom of that page, the related links include demos, such as the
&gt; Albanian Constitution (kushtetuta).
&gt; 
&gt; Cocoon/Lenya is what I mean to mess with next:
&gt; <a  rel="nofollow" href="http://lenya.apache.org/";>http://lenya.apache.org/</a>
&gt; I'm wondering if either the BXE or kupu editors will work as I hope.
&gt; 
&gt; David Tolpin wrote a What You See Is What You Mean plugin for jEdit, but
&gt; withdrew it soon after making it public. Durn. Here, though, is the user 
&gt; guide:
&gt; <a  rel="nofollow" href="http://www.davidashen.net/PreTI/jEdit/users-guide.html";>http://www.davidashen.net/PreTI/jEdit/users-guide.html</a>
&gt; 
&gt; Grady Harris
&gt; Grady Hospital Branch Library
&gt; Quoting ale-request at ale.org:
&gt; 
&gt; Message: 2
&gt; Date: Sat, 20 Aug 2005 21:58:02 -0400
&gt; From: Jeff Hubbs &lt;hbbs at comcast.net&gt;
&gt; Subject: [ale] Structured Documentation
&gt; To: ale at ale.org
&gt; Message-ID: &lt;1124589482.18405.35.camel at angel&gt;
&gt; Content-Type: text/plain
&gt; 
&gt; I'm looking for open-source ways to generate and maintain structured
&gt; documents.
&gt; 
&gt; When I say &quot;structured documents&quot; I'm talking about technical or
&gt; procedural manuals suitable for printing or screen reading. I'd like to
&gt; be able to create a revision history on a part-by-part basis such that
&gt; if I made a change to part 3.1.7, a new version of the entire doc would
&gt; be generated and a look back at the previous version would show the
&gt; pre-change 3.1.7. Or, if I selected 3.1.7 and did some kind of history
&gt; call-up on it, I'd see the current version plus all previous versions,
&gt; their dates, and who modified them.
&gt; 
&gt; Anyone know of anything in existence that works close to this? I've got
&gt; an idea in my head somewhere between Lyx and how Gentoo's online XML
&gt; docs work.
&gt; 
&gt; Jeff
&gt; 
&gt; 
&gt; 
&gt; ------------------------------
&gt; 
&gt; Message: 3
&gt; Date: Sun, 21 Aug 2005 08:05:34 -0400
&gt; From: &quot;James P. Kinney III&quot; &lt;jkinney at localnetsolutions.com&gt;
&gt; Subject: Re: [ale] Structured Documentation
&gt; To: Atlanta Linux Enthusiasts &lt;ale at ale.org&gt;
&gt; Message-ID: &lt;1124625934.25626.54.camel at merlin.localnetsolutions.com&gt;
&gt; Content-Type: text/plain; charset=&quot;us-ascii&quot;
&gt; 
&gt; On Sat, 2005-08-20 at 21:58 -0400, Jeff Hubbs wrote:
&gt; I'm looking for open-source ways to generate and maintain structured
&gt; documents.
&gt; 
&gt; When I say &quot;structured documents&quot; I'm talking about technical or
&gt; procedural manuals suitable for printing or screen reading. I'd like to
&gt; be able to create a revision history on a part-by-part basis such that
&gt; if I made a change to part 3.1.7, a new version of the entire doc would
&gt; be generated and a look back at the previous version would show the
&gt; pre-change 3.1.7. Or, if I selected 3.1.7 and did some kind of history
&gt; call-up on it, I'd see the current version plus all previous versions,
&gt; their dates, and who modified them.
&gt; 
&gt; Anyone know of anything in existence that works close to this? I've got
&gt; an idea in my head somewhere between Lyx and how Gentoo's online XML
&gt; docs work.
&gt; Sounds like a CVS/Subversion system for documentation to me, Jeff. If
&gt; it's written in XML the output can be any format you want. An article in
&gt; Linux Magazine
&gt; <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>
&gt; may have some ideas.
&gt; 
&gt; Jeff
&gt; 
&gt; _______________________________________________
&gt; Ale mailing list
&gt; Ale at ale.org
&gt; <a  rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
&gt; -- James P. Kinney III \Changing the mobile computing world/
&gt; CEO &amp; Director of Engineering \ one Linux user /
&gt; Local Net Solutions,LLC \ at a time. /
&gt; 770-493-8244 \.___________________________./
&gt; <a  rel="nofollow" href="http://www.localnetsolutions.com";>http://www.localnetsolutions.com</a>
&gt; 
&gt; Message: 5
&gt; Date: Sun, 21 Aug 2005 15:46:06 -0400
&gt; From: Jim Popovitch &lt;jimpop at yahoo.com&gt;
&gt; Subject: Re: [ale] Structured Documentation
&gt; To: Atlanta Linux Enthusiasts &lt;ale at ale.org&gt;
&gt; Message-ID: &lt;1124653566.3616.3.camel at localhost&gt;
&gt; Content-Type: text/plain
&gt; 
&gt; Sounds like a Wiki would satisfy all that. I personally like MoinMoin
&gt; as it is written in Python and simply works well.
&gt; 
&gt; -Jim P.
&gt; Delete | Reply | Reply to All | Forward | Redirect | View Thread | 
&gt; DenyList |
&gt; AcceptList | Message Source | Save as | Print
&gt; Move | Copy Back to sent-mail &gt;
&gt; 
&gt; _______________________________________________
&gt; Ale mailing list
&gt; Ale at ale.org
&gt; <a  rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
&gt; 



-- 
<a  rel="nofollow" href="http://warrenmyers.com";>http://warrenmyers.com</a>
&quot;God may not play dice with the universe, but something strange is going on 
with the prime numbers.&quot; --Paul Erd?s
-------------- next part --------------
An HTML attachment was scrubbed...



</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00324" href="msg00324.html">[ale] Structured Documentation</a></strong>
<ul><li><em>From:</em> gharri2 at emory.edu (gharri2 at emory.edu)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00324.html">[ale] Structured Documentation</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00326.html">[ale] Nvidia 7667 and SUSE 9.3 kernel update</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00324.html">[ale] Structured Documentation</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00401.html">[ale] suse 9.2 and Realtek 8139 eth0 problems</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00325"><strong>Date</strong></a></li>
<li><a href="threads.html#00325"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

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