Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?
 
PerlMonks  

comment on

( [id://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]

Output:

[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

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others imbibing at the Monastery: (4)
As of 2024-04-19 06:21 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found