Subj : de.komm.software.kreuzungspunkt To : Martin Foster From : August Abolins Date : Thu Mar 18 2021 08:41:00 Hello Martin! ** On Thursday 18.03.21 - 11:44, you wrote to me: AA>> I found another online translator. Here is the TOC using DeepL: AA>> I Basics AA>> 1.1 FidoNet - structure and addressing AA>> 1.2 Point in FidoNet AA>> 1.3 The nodelist(s) [...] AA>> "Translated with www.DeepL.com/Translator (free version)" AA>> Do you see anything amiss above? MF> Nope, that's an excellent job. Is that exactly as it came MF> 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. MF> I'm asking because I tried it out with a short paragraph MF> and it came out looking like a dog's dinner. Was your test with DeepL? AA>> I would suggest that we can split the effort.. MF> I would NOT advise using the XPOINT echo for that purpose MF> as it's actually a gated *German* newsgroup. Some sort of MF> versioning system, such as git or svn, would be a far MF> 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) .