Hi Albert, Could you give another (last ?) try, as of rev. 917 ? This *should* work. I tried under XP and Linux, works ok for me.
My mistake was to handle to linefeed chars in my script and writing files in ASCII format. Python seems to automatically handle them in this mode. Using binary mode, it just saves what it gets. So when I saved "\r\n", python was replacing "\n" by "\r\n" under XP, thus gives "\r\r\n" (aka Seb's format). Now it just saves "\r\n". Maybe I shouldn't take care of linefeed in my script and use "\n" only, and let python deals with platform/OS details... Cheers, Seb 2009/4/4 Sebastien Lelong <[email protected]> > Forget this, I'm on it. > > Seb > > 2009/4/4 Sebastien Lelong <[email protected]> > > Could you post the board + test file, and the generated sample so I can >> have a look ? (and try under XP) >> >> >> Thanks, >> Seb >> >> >> >>> Hi Seb, >>> Still see an issue with the latest jallib.py (rev 911), the end of >>> line is terminated with 0x0D 0x0D 0x0A >>> >>> > -- mine gives "\n" as standard linefeed char-- , Albert are you under >>> Mac OS >>> >>> No, on Windows XP >>> >>> Albert >>> >>> >>> >>> >> >> >> -- >> Sébastien Lelong >> http://www.sirloon.net >> http://sirbot.org >> > > > > -- > Sébastien Lelong > http://www.sirloon.net > http://sirbot.org > -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
