🚀 go-pugleaf

In article <2874@ethz.UUCP>, maer@ethz.UUCP (Matthias Ernst) writes:
> I tried to tranfer a dvi-file created on a IBM-PC to a VAX.
> Beim verarbeiten auf der VAX bekomme ich allerdings immer
> die Fehlermeldung Invalid DVI-File Format.
> 
> I assumed that DVI-file formats are identical on different
> systems.?? 
> 
I will assume that you did a binary transfer (ftp? kermit? ...).  but that
is not all.  most dvi2xxx on the vax assume 'fixed' length record format,
while ftp and kermit will transfer 'constant' length records but will not
create 'fixed' length files.  I think that CKermit (on the vax) can create 
'fixed' files with the command  'set file type fixed' , but Kermit32 is so much
faster that I almost never use it.

Now you can 'convert' your file to a 'fixed' format :

1.  analyze/rms/fld <your dvi file>    this will produce a short new file
                                       with extension  .fdl

2.  edit/fdl        <your fdl file>    changing the format to 'fixed'
                                       and possibly length to '512' .
                                       (you can also do it without the
                                       /fdl but with the manual. it will 
                                       be faster!)

3.  convert/fdl=<your new fdl file>  <your old dvi file>  <your new dvi file>

         and that is all !  (and usualy, it WORKS ...)

The only problem encountered was with a dvi file with 1023 bytes records.
convert can extend/pad records but not cut them in smaler pieces.  For this,
we have a small fortran program that does the trick ...

By the way, you may have the same problem porting fonts. use similar solutions!

               Frohe Weihnachten  und  glukliches neues Jahr 

                                    Paul Bartholdi   -  Observatorium Genf