Re: Patch for documentation

Peter J Ross <[email protected]>
Newsgroups gmane.network.slrn.user
Message-ID <[email protected]>
On Saturday 26 April 2008 10:04:20 Jörg Sommer wrote:
> Hi John,
>
> can you apply this patch? I improves the description of the behaviour of
> forward.

In the past, patches for manual.txt have been refused because the file is 
generated automatically from slrn-manual.sgml.

The advantage of this approach is that it keeps manual.txt and the HTML 
documentation synchronised. The disadvantage is that some knowledge of SGML 
and the linuxdoc DTD is required in order to maintain the documentation, 
while many people have moved on to XML and docbook for such purposes.

Anyway, if you're interested, you can get the last official SGML sources for 
manual and FAQ here: <http://slrn.cvs.sourceforge.net/slrn/manual/>. Note 
that they're not available in the SVN repository, so may no longer be 
official.

There are updated unofficial versions of manual and FAQ (as plain text and 
HTML) for 0.9.9 here: <http://pjr.lasnobberia.net/slrn-doc/>. (These pages 
are maintained by me, though Thomas Wiegner is the principal writer of recent 
additions to the documentation.)

But I'm not sure how to submit the changes in the right way to update the 
official doc/manual.txt and doc/FAQ. If the manual/ directory were copied 
from CVS to SVN, there would be a clear, "official" original to be patched.

While I'm here, thanks, Jörg, for updating the Debian testing/sid slrn package 
to pre0.9.9. That should simplify things for us news.software.readers posters 
a lot!

-- 
PJR :-)

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.