| |
I0OJJ > PACKET 30.04.21 13:01l 44 Lines 1580 Bytes #999 (0) @ WW
BID : U4VI0OJJ_006
Read: GUEST
Subj: Re: Possible to use uuencode?
Path: IW8PGT<IZ3LSV<I3XTY<I0OJJ
Sent: 210430/1157z @:I0OJJ.ITA.EU [Rome] obcm1.08-5-g2f4a
From: I0OJJ @ I0OJJ.ITA.EU (Gustavo)
To: PACKET @ WW
X-Info: Sent with login password
X-Info: Received by SMTP-gateway
a new addressed copy...
On 4/28/21 3:48 PM, kg7ujh@w7pbs.az.usa.noam wrote:
> R:210428/1537z @:VE3CGR.#SCON.ON.CAN.NOAM [Aurora] jnos2.0m.5Gx $:2163_W7PBS Z:L4G1C5
> R:210428/1437z @:N9SEO.#STX.TX.USA.NOAM [Bastrop] $:2163_W7PBS
> R:210428/1348z @:W7PBS.AZ.USA.NOAM 2.0k.2 #:2165 $:2163_W7PBS
>
> With regards to G8MNY's post, "Decoding BBS Data files (TEXT)", 7plus is referenced
> for compressing, splitting, and creating the files for uploading to the BBS. From what
> I have found, 7plus is windows only. I am on a Linux system and am wondering if it is
> permissible to use uuencode and split the uuencoded output into the appropriate sizes?
>
> I understand that all communications over amateur radio need to be in the clear and I
> am curious if uuencode files are considered in the clear.
>
> 73, de KG7UJH
1) 7plus is for msdos. windoze and linux.
2) uuencode, as per my knowledge, doesn't have the
capability to be splitted in parts as 7plus do;
it can encode very large text and binary files
.txt, .zip, .jpg, tgz, and so on,,
But, being only a pure text encoder it has roughly
the 40% of overhead payload with respect to the
original file..
3) At least, in Europe, any usual/known compression
can be safely used in our hamradio activities.
--
73 and ciao, gustavo i0ojj/ir0aab/ir0eq
non multa, sed multum
begin-base64-encoded 666 c2lnbmF0dXJl
NzMgYW5kIGNpYW8sIGd1c3Rhdm8gaTBvamovaXIwYWFiL2lyMGVxCm5vbiBt
dWx0YSwgc2VkIG11bHR1bQo=
====
Read previous mail | Read next mail
| |
