🚀 go-pugleaf

In article <na.68b203479b.a40040rmurray@argonet.co.uk>,
 Richard Murray <rmurray@argonet.co.uk> wrote:
> In article <479acc6791jsd@argonet.co.uk>, Jonathan Duddington
> <jsd@argonet.co.uk> wrote:

> Hmmm... I wrote a long bit on UUcode not that long ago. Did it get lost?

The 6.Jun article? I've got that, but it doesn't tell me everything I need to know.  I've found the Unix source and document for UUE now, which looks helpful.

I'm still not sure though why (some) UUE attachments have every line
ending in an 'a' character.

There seem to be two topics:
a.  Basic UUE
b.  Attachments in mail and news messages.

How should an attachment be recognised?
Anything starting with "begin 644 "?
Or only if it's after the sig. (if there is a sig.)?
Does it have to have "644" in the "begin" line?
  (the Unix UUE document doesn't say it must be "644")
If not, then does "begin" at the start of *any* line of the message mean
  an attachment?  Or "begin <number>" ?

> It'd be nice if you could support the InfoSys method. It gives you
> size, filetype and attributes. Optional CRC too.

Where do I find the definition of "infoSys"?
-- 
  Demo version of !Speak from:  http://www.argonet.co.uk/users/jsd
  
  Jon Duddington                jsd@argonet.co.uk
  Coventry, England.            Speech synthesis for Acorn RiscOS computers