I found another online translator. Here is the TOC using DeepL:
I Basics
1.1 FidoNet - structure and addressing
1.2 Point in FidoNet
1.3 The nodelist(s)
"Translated with www.DeepL.com/Translator (free version)"
Do you see anything amiss above?
Nope, that's an excellent job. Is that exactly as it came
out or did you do a bit of tickling up?
I'm asking because I tried it out with a short paragraph
and it came out looking like a dog's dinner.
I would suggest that we can split the effort..
I would NOT advise using the XPOINT echo for that purpose
as it's actually a gated *German* newsgroup. Some sort of
versioning system, such as git or svn, would be a far
better way of handling it IMO.
I found another online translator. Here is the TOC using DeepL:
I Basics
1.1 FidoNet - structure and addressing
1.2 Point in FidoNet
1.3 The nodelist(s)
[...]
"Translated with www.DeepL.com/Translator (free version)"
Do you see anything amiss above?
Nope, that's an excellent job. Is that exactly as it came
out or did you do a bit of tickling up?
That's the exact result, with indenting. Mind you, since the
original had indenting and added spacing, the proper spacing in
the restul was noticeable after a cut'n'paste into Notpad or
this wider editor space.
I'm asking because I tried it out with a short paragraph
and it came out looking like a dog's dinner.
Was your test with DeepL?
I just learned about TortoiseSVN, since it support Windows. It
looks like a fine tool for managing doc changes.
But I suppose we would need a webbased versioning system, not a
local one for participants/editors?
Was your test with DeepL?
Yes it was.
[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 :)
https://www.smartsvn.com/
I've used the Linux version for many years and have found
that "Lite" mode more than meets my needs.
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 :)
Here is section I.0
Yes, very nice :)
So.. if we were to engage in this project, we would need to
settle on using the same svn program I suppose.
No, not at all, each user would be free to use whatever svn client they chose, even the commandline version of svn would do. In fact, that may well be easier for the new svn user because it's only really necessary to learn 3 basic commands(checkout, update and commit).
I wouldn't really recommend SmartSVN if you're new to version control, I feel that TortoiseSVN would be the better choice. The only reason I use SmartSVN is because there isn't a Linux version of TortoiseSVN.
However, I don't see the point of trying it out just yet because I
haven't seen any volunteers step forward and therefore, there's no repository to try it out on.
--But I suppose we would need a webbased versioning
system, not a local one for participants/editors?
Oh.. and one person is designated as managing and releasing the
final "master" copy?
Yes, there would need to be a project coordinator.
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 :)
However, I don't see the point of trying it out just yet because I
haven't seen any volunteers step forward and therefore, there's no
repository to try it out on.
But I could use some practice first, with your help -
and experiment with the paragraphs in section I for starters.
What minimum # of people do you envision should participate in the translation project? DeepL can work with 5000 chars at a time. The fido.tx file is about 133K chars.
That would make it about 26 or 30 files in the depository?
From the sounds of it, svn is something I should have been using
all along especially for the invoices that I sometimes need to
modify and keep track of what was changed.
Apparently tortoisesvn "integrates" into windows explorer (the
file management display) but I can't seem to figure out how to
get started with anything.
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 :)
It sounds amazing! I am anxious to try it. But like I wrote
earlier, I wasn't able to kick-start anything to work on.
If the master is to be on a server, how does that work with
tortoisesvn? Tortoisesvn seems to be a local program that works
with one's own files only.
and experiment with the paragraphs in section I for starters.
Nice idea but experimenting with other folks' repositories is a NO-NO.
What minimum # of people do you envision should participate in the
translation project? DeepL can work with 5000 chars at a time. The
fido.tx file is about 133K chars.
That's a good question which I can't really answer but I would guess at probably two.
That would make it about 26 or 30 files in the depository?
No it wouldn't, there would only be one file in the repository.
Apparently tortoisesvn "integrates" into windows explorer (the
file management display) but I can't seem to figure out how to
get started with anything.
Right-Clicking on the Desktop would be a good place to start and then click on "SVN Checkout" but without a repository URL, that's as far as
you could go.
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 140:21:29 |
Calls: | 328 |
Files: | 5,823 |
Messages: | 228,086 |