Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

It'll probably need tweaking constantly for different input, but it works for the sample data. I've no idea what $thing is though.

#! perl -slw use strict; $^W=0; while( <DATA> ) { my( $authors, $title, $thing, $pub, $date, $comment, $no ) = m/ ^ -( .*? \. ) \s(?=[A-Z][a-z]) ( .+ ) \.\s+ ( [^:]+? ) : \s+ (\S+), \s+ ( \d{4} ) [^.]* \. \s+ ( [^\[]+ ) \[ ( \d+ ) \] \s* $ /x; printf " Author:'%s'\n" . " Title:'%s'\n" . " Thing?:'%s'\n" . "Publisher:'%s'\n" . " Date:'%4d'\n" . " Comment:'%s'\n" . " No:'%d'\n\n", $authors, $title, $thing, $pub, $date, $comment, $no; } __DATA__ -Lightfoot, J. B. St. Paul’s Epistle to the Philippians. Grand Rapids: + Zondervan, 1953 (= 1913). Classic commentary by one of the greatest +English-speaking NT scholars of all time. [2] -Martin, Ralph P. Philippians. Rev. ed.; NCB. Grand Rapids: Eerdmans, +1980. Clear and informed. [2] -O'Brien, Peter, T. Commentary on Philippians. NIGTC. Grand Rapids: Ee +rdmans, 1991. Thorough and insightful comments on the Greek text. [1] -Silva, Moisés. Philippians. Baker Exegetical Commentary. Grand Rapids +: Baker, 1993. Sound comments on the Greek text. [2] -Barth, Markus and Helmut Blanke. The Letter to Philemon: A New Transl +ation with Notes and Commentary. Grand Rapids: Eerdmans, 2000. With o +ver 500 pages devoted to a letter that was probably written on a sing +le sheet of papyrus, this work will be consulted by all who want the +most thorough treatment of Philemon and avoided by the rest of us. [3 +] -Bruce, F. F. The Epistles to the Colossians, to Philemon, and to the +Ephesians. NIC. Grand Rapids: Eerdmans, 1984. See comments under “Com +mentaries on Ephesians.” [2]


[23:43:10.06] P:\test>411598 Author:'Lightfoot, J. B.' Title:'St. Paul?ÇÖs Epistle to the Philippians' Thing?:'Grand Rapids' Publisher:'Zondervan' Date:'1953' Comment:'Classic commentary by one of the greatest English-speaking +NT scholars of all time. ' No:'2' Author:'Martin, Ralph P.' Title:'Philippians. Rev. ed.; NCB' Thing?:'Grand Rapids' Publisher:'Eerdmans' Date:'1980' Comment:'Clear and informed. ' No:'2' Author:'O'Brien, Peter, T.' Title:'Commentary on Philippians. NIGTC' Thing?:'Grand Rapids' Publisher:'Eerdmans' Date:'1991' Comment:'Thorough and insightful comments on the Greek text. ' No:'1' Author:'Silva, Mois??s.' Title:'Philippians. Baker Exegetical Commentary' Thing?:'Grand Rapids' Publisher:'Baker' Date:'1993' Comment:'Sound comments on the Greek text. ' No:'2' Author:'Barth, Markus and Helmut Blanke.' Title:'The Letter to Philemon: A New Translation with Notes and Co +mmentary' Thing?:'Grand Rapids' Publisher:'Eerdmans' Date:'2000' Comment:'With over 500 pages devoted to a letter that was probably w +ritten on a single sheet of papyrus, this work will be consulted by a +ll who want the most thorough treatment of Philemon and avoided by th +e rest of us. ' No:'3' Author:'Bruce, F. F.' Title:'The Epistles to the Colossians, to Philemon, and to the Eph +esians. NIC' Thing?:'Grand Rapids' Publisher:'Eerdmans' Date:'1984' Comment:'See comments under ?Ç£Commentaries on Ephesians.?Ç¥ ' No:'2'

Examine what is said, not who speaks.
"But you should never overestimate the ingenuity of the sceptics to come up with a counter-argument." -Myles Allen
"Think for yourself!" - Abigail        "Time is a poor substitute for thought"--theorbtwo         "Efficiency is intelligent laziness." -David Dunham
"Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon

In reply to Re: parsing a bibliography by BrowserUk
in thread parsing a bibliography by patrickrock

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others wandering the Monastery: (6)
    As of 2020-08-05 22:13 GMT
    Find Nodes?
      Voting Booth?
      Which rocket would you take to Mars?

      Results (37 votes). Check out past polls.