• de.komm.software.kreuzungspunkt

    From August Abolins@2:221/1.58 to Martin Foster on Thu Mar 18 08:41:00 2021
    Hello Martin!

    ** On Thursday 18.03.21 - 11:44, you wrote to me:

    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 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.

    Yeh, I guess the "de." part in "de.comm.software.crosspoint"
    would be a clue. :/ But the rest of the name is english. I
    mean, it's not like it's "komm.software.kreuzungspunkt" :D

    Personaly, I like the idea of managing a translation discussion
    with OXP, the product underdiscussion itself. The built in
    search and threading would make it easy to follow a development.

    Someone posted a samples of usage of the ftsc documentation in
    git. https://github.com/zoomosis/ftsc There, it looks pretty straightforward to make editing changes right on the spot and
    watch the progress.

    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?


    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)
  • From Martin Foster@2:310/31.3 to August Abolins on Sun Mar 21 09:22:00 2021
    Hello August!

    *** Thursday 18.03.21 at 08:41, August Abolins wrote to Martin Foster:

    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?

    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 :)

    There's also SmartSVN but it's commercial but once the 30-day trial period ends, it switches into "Lite" mode and can be used for as long as is required. Windows, Linux and macOS versions are available from .....

    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 :)

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From August Abolins@2:221/1.58 to Martin Foster on Sun Mar 21 10:03:00 2021
    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)
  • From August Abolins@1:396/45.29 to Martin Foster on Wed Mar 24 21:15:00 2021
    Hello Martin!

    ** On Wednesday 24.03.21 - 13:55, you wrote to me:

    Here is section I.0

    Yes, very nice :)

    Except for a couple of words that duplicated, I thought the
    result was pretty good too!

    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).

    Hmmm. I installed tortoisesvn on my win7 DT pc but nothing
    seemed to load. I got a message saying "Read the manual!" :/

    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.

    The latest tortoisesvn versions don't support XP. But apparently
    I can fetch an older version.

    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?

    Oh.. and one person is designated as managing and releasing the
    final "master" copy?

    Yes, there would need to be a project coordinator.
    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! -> . <- (1:396/45.29)
  • From August Abolins@1:396/45.29 to Martin Foster on Wed Mar 24 21:19:00 2021
    Hello Martin!

    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.

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! -> . <- (1:396/45.29)
  • From Martin Foster@2:310/31.3 to August Abolins on Thu Mar 25 11:31:00 2021
    Hello August!

    *** Wednesday 24.03.21 at 21:15, August Abolins wrote to Martin Foster:

    [snip]
    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 -

    Gulp! =8}

    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.

    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.

    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.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Thu Mar 25 11:38:00 2021
    Hello August!

    *** Wednesday 24.03.21 at 21:19, August Abolins wrote to Martin Foster:

    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.

    Once any changes have been completed in the user's working copy, those changes would be merged into the remote master copy by using TortoiseSVN
    to commit the changes.

    Regards,
    Martin

    --- OpenXP 5.0.49
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From August Abolins@2:221/1.58 to Martin Foster on Mon Mar 29 20:11:00 2021
    Hello Martin Foster!

    ** On Thursday 25.03.21 - 11:31, Martin Foster wrote to August Abolins:

    and experiment with the paragraphs in section I for starters.

    Nice idea but experimenting with other folks' repositories is a NO-NO.

    Huh? The translation hasn't even started (except for the first
    para in section I)

    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.

    OK! But you said there had to be more people involved. Now you
    say only two - how 'bout you and I? :D

    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.

    I think it would be much easier to monitor translations if the
    project proceeded subsectio by subsection. The whole 150K char
    document would be a nightmare to monitor progress. The editing
    work and approval amongst the team would be easier from to
    bottom in an orderly sequence.

    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.

    I watched a few tortoisesvn YT videos. Most of them were
    terrible - the host moving the mouse all over the place and NOT
    explaining WHY and WHERE he was moving the mouse. Literally it
    was "go here, then here, to get that, oops.. I mean here, and
    then this.." ARGHHHH!

    To get started I would need to get an earlier version of
    tortoisesvn that supports XP.

    The only other thing I don't understand and is HOW and WHERE is
    the "repository" hosted so that the files are availble to other
    editors interested in the project?

    --
    ../|ug

    --- OpenXP 5.0.49
    * Origin: The ONLY point that matters! --> . <-- (2:221/1.58)