Daryl wrote --

Some folks have no idea how to cut and paste...unless they think it's
with scissors, paper, and glue. :P

Some years ago I was helping to write a grant or something, doing the
typing and so forth.
Anyway, parts of this paper had to be repeated (over and over again) and
I told the woman in charge we could just copy and paste rather than re-write several paragraphs at a time.
She didn't know how to do that, wasn't interested in learning at the time
so it was the old system of re-typing everything.
We had several people doing different things: one would organise the information, another compile it, one to dictate, another to type, and couple of others as editors who were not involved in anyway with the above so it was
all new to them and who could cat
Joe


--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: Fido Since 1991 | QWK by Web | BBS.FIDOSYSOP.ORG (1:123/140)

Re: Copy and paste (was: Re: journal)
By: JOE MACKEY to DARYL STOUT on Mon Jan 13 2020 07:41:06

We had several people doing different things: one would
organise the information, another compile it, one to
dictate, another to type, and couple of others as editors
who were not involved in anyway with the above so it was
all new to them and who could cat

chopped again... you really need to bring this up with your BBS operator if you
haven't already... their software has an ugly defect in it that really needs to
be fixed :(


)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

On Jan 13, 2020 09:33am, MARK LEWIS wrote to JOE MACKEY:

We had several people doing different things: one would
organise the information, another compile it, one to
dictate, another to type, and couple of others as editors
who were not involved in anyway with the above so it was
all new to them and who could cat

chopped again... you really need to bring this up with your BBS
operator if you haven't already... their software has an ugly defect in
it that really needs to be fixed :(

Mark, this software is from 1997 and this is the 1st ive heard about this particular problem. Nothing has changed on this end. Might be a web-browser specific error. I'm on it :)

... Still Here Since 1991 BBS.DOCSPLACE.ORG Web or Telnet
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: Fido Since 1991 | QWK by Web | BBS.FIDOSYSOP.ORG (1:123/140)

Re: RE: Copy and paste (was: Re: journal)
By: ED KOON to MARK LEWIS on Tue Jan 14 2020 07:53:46

who were not involved in anyway with the above so it was
all new to them and who could cat

chopped again... you really need to bring this up with your BBS
operator if you haven't already... their software has an ugly
defect in it that really needs to be fixed :(

Mark, this software is from 1997 and this is the 1st ive heard about this

particular problem. Nothing has changed on this end. Might be a web-browser specific error. I'm on it :)

i understand, ed... the problem seems to be related to line lengths and how your software handles long lines... i know there's a buffer that they have to be read into for processing... possibly that buffer is only 255 characters whereas long lines may be up to 32k or 64k in length... no clue how to fix it without the sources and compiling a new binary... possibly someone with the deep skills could patch on a replacement routine and adjust the binary to jump to the new routine but that's some deep binary level hacking to do without the source code...

FWIW: it has been happening for quite a while... i've mentioned it to JM a few times in the past several years and he makes attempts to work around it by manually shortening his lines by hitting enter on them like old typewriter days
but sometimes he/we forget to do that... when that happens we see the chop where the rest of the line longer than the available buffer space is lopped off
and never processed as the code jumps to the next line to process it...

hopefully there will be a fix coming for you... good luck! :)


)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

i understand, ed... the problem seems to be related to line lengths and how your software handles long lines... i know there's a buffer that they have to be read into for processing... possibly that buffer is only 255 characters whereas long lines may be up to 32k or 64k in length... no clue how to fix it without the sources and compiling a new binary... possibly someone with the deep skills could patch on a replacement routine and adjust the binary to

jump

to the new routine but that's some deep binary level hacking to do without

the

source code...

FWIW: it has been happening for quite a while... i've mentioned it to JM a

few

times in the past several years and he makes attempts to work around it by manually shortening his lines by hitting enter on them like old typewriter

days

but sometimes he/we forget to do that... when that happens we see the chop where the rest of the line longer than the available buffer space is lopped

off

and never processed as the code jumps to the next line to process it...

hopefully there will be a fix coming for you... good luck! :)

I see it now after posting a 8 generated paragraphs. Must be from Wildcat 5 internal coding. I see the vultures flying overhead! :)
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: Fido Since 1991 | QWK by Web | BBS.FIDOSYSOP.ORG (1:123/140)

Joe,

Anyway, parts of this paper had to be repeated (over and over again) and
I told the woman in charge we could just copy and paste rather than re-write JM>several paragraphs at a time.
She didn't know how to do that, wasn't interested in learning at the time
so it was the old system of re-typing everything.

Was she blonde?? :P

This old dog doesn't like to learn new tricks, but sometimes, you have
to.

daryl


* OLX 1.53 * Without geometry, life is pointless.
--- SBBSecho 3.10-Win32
* Origin: The Thunderbolt BBS - tbolt.synchro.net (1:19/33)