stew has asked for the wisdom of the Perl Monks concerning the following question:

Hi,

I have been asked to pick up a project started by a colleague who has gone swanning of on holiday for a week.

Basically he is using Perl to create a summary of an XML document and output it in RTF format. He is using XSL and Sablotron to generate the RTF. All his code has been done and tested on windows.

The XML repository is on a Linux server, when I have done a batch of RTF's they look ok when you view the source, but appear without formatting when you open them in Word, but the examples built on his Windows machine look OK

Methinks it must be a compatability issue twixt Linux and Windows \n's and the like???? When I view my versions and his in a text editor they look identical.

Anybody got any quick advice, it would be greatly appreciated. I know it's not a 100% Perl question but if theres some sort of file conversion I can do

Stew

Replies are listed 'Best First'.
Re: Windows incompatability problems
by PodMaster (Abbot) on May 23, 2003 at 11:36 UTC
    Did you compare hexdumps?


    MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
    I run a Win32 PPM repository for perl 5.6x+5.8x. I take requests.
    ** The Third rule of perl club is a statement of fact: pod is sexy.

Re: Windows incompatability problems
by stew (Scribe) on May 23, 2003 at 12:16 UTC
    There seems to be lots of bytes either replaced or deleted in the Linux generated rtf.

    No expert on XSL but could it be something to do with character encoding??

      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.

        Sure

        First few bytes good file

        7B5C727466315C616E73695C616E7369637067313235325C64656666

        First few bytes bad file

        0A20207B5C727466315C616E73695C616E7369637067313235325C64

        Hope this helps