🚀 go-pugleaf

        As i reported to the list some days before, we had problems
        with the uuencoded files too. We located the problem in our
        EBCDIC --> ASCII Translation-Table. Looking around i found
        some other obscure tables. So some sites like to do a
        "visual - replacement". This means that for example the
        ASCII ! (exclamation point) ist translated to the EBCDIC
        | (short vertical bar). At our VAX there are two different
        Translation Tables (supported to choose at generating).
        So if a site in the (Bit-)Net is using the other table .....

        So i like to propose that people who are sending uuencode files
        may support an additional line, which shows the used characters
        in the ASCII-Order. ( I think in UUENCODE this are the chars
        between 20hex and 5Fhex in ASCII)

        for example a line like the one below

 !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_


        starting with blank, may be very helpfull to decide where from
        troubles come.

        So with such line everyone could see, if there are some chars
        double, or the chars ar not in the ASCII-sequence, that he could
        save the time for transmitting the file to his ATARI

                        Steve

        Name : Stephan Leicht
Organisation : Computer Center of Technical University Darmstadt, Germany
      Bitnet : #049@DDATHD21.Bitnet