Hello Martin!
** On Sunday 21.03.21 - 09:22, you wrote to me:
Was your test with DeepL?
Yes it was.
What paragraph did you test? Here is section I.0
I Basics
=======================================================
Actually, CrossPoint was once conceived as a pure Z-net
pointing software designed, and in fact it was supposed
to remain that way. Well, as you you can see that it did
not stay that way - since version a large number of
different networks since version 2.0, and the Fido part
takes the biggest space. This is mainly due to Burkard
Schoof, who has constantly provided me with new ideas
and comments on the Fido implementation.
The FidoNet is the oldest and largest of all mailbox
networks and can therefore be and can therefore offer
the most special features. Because of the number of
special Fido features, I have decided to decided to
summarize all FidoNet related things in this text. in
this text. It should and can replace the manual, but
serves only as a supplement and a quick as a quick start
guide for Fido. To understand the CrossPoint concept you
should at least read the basic chapters of the manual.
read.
The Fido part of CrossPoint is covered by the same
shareware license conditions as for the rest of the
program. For more details can be found in LIZENZ.TXT.
As for the manual also for this text, may be published
in mailbox networks with reference to the source.
mailbox networks.
So, let's finally get to the main thing - the use of
CrossPoint in FidoNet. If you already have experience
with other Fido point software and have a profound
knowledge of Fido technology, you can you can proceed
directly with the installation in chapter 2.1. As a Fido
new user you should at least briefly skim part 1 of this
text, because I will assume you know the concepts and
terms explained there. as known.
In case of problems you can reach the team in the known
support echoes (see manual, chapter 1.3).
Peter Mandrella,
September 1992 - September 1995
(revised by the OpenXP team in March 2000)
--4 PS: Fido and FidoNet are registered trademarks of Tom
Jennings and Fido Software.
--4 PPS: I would like to thank Burkard Schoof, Max Raabe and Michael
Heydekamp for their valuable cooperation.
I added my own wrapping to fit better in this echo.
I don't see too many problems above at all. Minor clean up is
to be expected.
[snip]
I just learned about TortoiseSVN, since it support
Windows. It looks like a fine tool for managing doc
changes.
Yes, it's an excellent piece of software and it's free :)
So.. if we were to engage in this project, we would need to
settle on using the same svn program I suppose.
https://www.smartsvn.com/
I've used the Linux version for many years and have found
that "Lite" mode more than meets my needs.
I'm game to try that one since you're already using it.
But I suppose we would need a webbased versioning system, not a
local one for participants/editors?
The master copy of the document would be held in the remote
svn repository and all changes to the document would be
done in the users' own local working copy of the document.
All changes to the users' working copy of the document
would then be commited by each user to the master copy in
the remote svn repository. That's simplifying it a bit but
you should get the jist of how it works :)
Oh.. and one person is designated as managing and releasing the
final "master" copy?
--
../|ug
--- OpenXP 5.0.49
* Origin: The ONLY point that matters! --> . <-- (2:221/1.58)