in reply to Re: Windows incompatability problems
in thread Windows incompatability problems

Can you come up with a very simple example, e.g. just one formatted sentence, and then find out the differences with a hex editor? If we know more details, we'll be able to help better.

  • Comment on Re: Re: Windows incompatability problems

Replies are listed 'Best First'.
Re: Re: Re: Windows incompatability problems
by stew (Scribe) on May 23, 2003 at 16:08 UTC
    Sure

    First few bytes good file

    7B5C727466315C616E73695C616E7369637067313235325C64656666

    First few bytes bad file

    0A20207B5C727466315C616E73695C616E7369637067313235325C64

    Hope this helps
[reply]
[d/l]
[select]

      Might be a bug in the Linux version... these three bytes are a (Unix) newline and two spaces. Don't know how they end up being there.

      Can you confirm that this difference exists for all the files you create? Is it the only difference? If yes, the obvious quick hack du jour would be to chop those three bytes off. Of course, it might also be a well-known bug in the RTF-creating component. You might check whether you have the latest version and also check any bug reports/mailinglists available.

[reply]

      Other than the first three bytes, these samples appears to be identical.

      After doing a quicky test, prepending these three bytes to beginning of my test ".RTF" was enough to hose it up.

      HTH.

      Update: All is not lost, however... Removing these three bytes was enough to salvage the file.

      Cē

[reply]

In Section Seekers of Perl Wisdom