Word files forshortened by !Posty

[Mr John FO Evans]

I am finding that some Word (.doc) files are forshortened when copied from
!Posty into RISC OS. A workaround is to extract the files from the menu and
then use !Attacher to decode them.

The forshotened files seem to end with:-
[0d]----------------------------------------

Any Ideas?

[Bill (Adopt)]

Post by Mr John FO Evans
I am finding that some Word (.doc) files are forshortened when copied from
!Posty into RISC OS. A workaround is to extract the files from the menu and
then use !Attacher to decode them.
The forshotened files seem to end with:-
[0d]----------------------------------------
Any Ideas?

Failing somebody with better knowledge turning up,
the "0d" usually means an 'end-of-line' marker, ie
the end of each line hasn't been auto-added - which
we tend to do in all RISC OS software..

It's just a slight mismatch between your poster's
machine handling and your own.

If !Attacher works, then use it. There may have been
another proggie somewhere which would convert these
"0d's" for you although I wonder - been using !Pluto
for a long while now - if the conversion is not a
selectable option within !Posty? You'll be able to
find it if it is..

Failing that, use !Edit, !Zap or any text editor to
convert or get rid of spare "0d's"..

hh..

Bill ZFC

[Stuart]

Post by Mr John FO Evans
The forshotened files seem to end with:-
[0d]----------------------------------------
Any Ideas?

Junk !Posty in favour of something newer and less temperamental?

[Dr J E Hurley]

Post by Mr John FO Evans
The forshotened files seem to end with:-
[0d]----------------------------------------
Any Ideas?

We have !TextPort and !TextThing which both perform different adjustments to
MS type files to make them more legible, but we use !Attacher quite
frequently to extract Word etc documents which do not appear in !Posty.

John