*.opml file output to console problem

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

Replies are listed 'Best First'.
Re: *.opml file output to console problem by stevieb (Canon) on May 13, 2012 at 18:26 UTC
Post a sample of the input file here (so we don't have to go search an external site for it) as well as a sample of your desired output data. Personally, I find this line: `$str = $str.$_;` [download] More readable and easier to see the intent like this: `$str .= $_;` [download] Also, you should use the three argument form of open: `open my $SPE, '<', 'specification.opml' or die "Can't open the damned specification.opml file! $!"; while ( <$SPE> ){ ...` [download] One last thing... I've never used XML, but this may be a candidate for one of the many modules available from CPAN. I see esteemed members of PerlMonks frequently giving praise to XML::Twig, so it may be worth looking into. If that doesn't do the job, search CPAN for XML or perhaps even OPML.	[reply] [d/l] [select]
Re^2: *.opml file output to console problem by Anonymous Monk on May 13, 2012 at 19:05 UTC
Sorry for the inconvenience, I want the exact opml text from the file in my string like this: <?xml version="1.0" encoding="ISO-8859-1"?> <opml version="2.0"> <head> <title>workspace.userlandsamples.doSomeUpstreaming</title> <dateCreated>Mon, 11 Feb 2002 22:48:02 GMT</dateCreated> <dateModified>Sun, 30 Oct 2005 03:30:17 GMT</dateModified> <ownerName>Dave Winer</ownerName> <ownerEmail>dwiner@yahoo.com</ownerEmail> <expansionState>1, 2, 4</expansionState> <vertScrollState>1</vertScrollState> <windowTop>74</windowTop> <windowLeft>41</windowLeft> <windowBottom>314</windowBottom> <windowRight>475</windowRight> </head> <body> <outline text="Changes" isComment="true"> <outline text="1/3/02; 4:54:25 PM by DW"> <outline text="Change "playlist" to "ra +dio"."/> </outline> <outline text="2/12/01; 1:49:33 PM by DW" isComment="true" +> <outline text="Test upstreaming by sprinkling a few fi +les in a nice new test folder."/> </outline> </outline> <outline text="on writetestfile (f, size)"> <outline text="file.surefilepath (f)" isBreakpoint="true"/ +> <outline text="file.writewholefile (f, string.filledstring + ("x", size))"/> </outline> <outline text="local (folder = user.radio.prefs.wwwfolder + &q +uot;test\\largefiles\\")"/> <outline text="for ch = 'a' to 'z'"> <outline text="writetestfile (folder + ch + ".html&qu +ot;, random (1000, 16000))"/> </outline> </body> </opml> [download] use my perl code print out in console I got: `<opml ve</opml>2</body>e</outline>ext="writetestfile (folder + ch + &q +uot;.html", random (1000, 16000))"/>lder."/>` [download] it seems like a encoding problem, which I have no experience. So I wonder, how do I read such a file and properly stored in a perl string? This is a homework. Am not allow to use any module.	[reply] [d/l] [select]
Re^3: *.opml file output to console problem by tobyink (Canon) on May 13, 2012 at 19:17 UTC
At a guess you've got a mismatch between the line endings that Perl is outputting, and the line endings supported by your console. I imagine that if you redirect the output of your script into a file, then the file will look sensible. `perl myscript.pl > myoutput.txt` [download] ... and then open myoutput.txt in a decent text editor. In particular, I think your OPML file currently has Macintosh-style line endings. `perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'`	[reply] [d/l]
Re^4: *.opml file output to console problem by Anonymous Monk on May 13, 2012 at 23:14 UTC