Are they now extra ^Ms in the output, or are there ^Ms in the source data? The former might be a bug. The latter would not be.
On Win32, the binmode option to ttree is necessary to correctly handle binary data. Prior to the patch supplied for 2.20, ttree would generate correct output for text based templates on Win32, but if you needed to INSERT a binary file then it would mangle the file replacing LF characters with CR/LF characters.....the resulting output being less than desirable. Of course, on Unix platforms which don't distinguish between text and binary mode IO, this is a moot point. Dustin, as others have suggested....if you could post a test case that shows where ttree is not generating correct output, then I think the list could be able to provide more assistance. Hope that helps. Lyle Quoting Andy Wardley ([email protected]): > Dustin Frazier wrote: > > Anyone have any idea A) what's going on, and/or B) how best to debug > > this? > > Hi Dustin, > > I can offer some insight into why this is happening now. > From the CHANGES file: > > ttree > ----- > > * Applied patch from Lyle Brooks to add binmode to the process() > call in ttree. > http://rt.cpan.org/Ticket/Display.html?id=38076 > > As I understand it, ttree is now doing the correct thing (for some definition > of "correct") by preserving the original line endings in your document. > Previously is would automagically convert them to Unix-like line endings, or > rather, it would allow Perl to do that for you. > > Having said that, it's a long time since I did anything on Windows using > ttree or even TT, so my understanding could be flawed. > > A > > > > > > _______________________________________________ > templates mailing list > [email protected] > http://mail.template-toolkit.org/mailman/listinfo/templates _______________________________________________ templates mailing list [email protected] http://mail.template-toolkit.org/mailman/listinfo/templates
