Re: automagically create browsable POD pages [pod2html]
On Apr 1, 2004, at 10:33 AM, Eric Lease Morgan wrote: Is there some sort of make command I can run that will read the PODs in my distribution, turn them into (X)HTML files, and save them in a specified local directory of my distribution's filesystem? Thank you for the prompt replies, but the suggestions are overkill. I simply want to: 1. create a doc directory 2. loop through my lib directory looking for pods 3. convert each pod to xhtml 4. save converted files to the pod directory I think I will write a local wrapper to pod2html. BTW, pod2html looks like it will already do this, but I can't figure out how to make it: 1. create a single xhtml file for each pod 2. give each file a specific name Yeah, I can't do this pod by pod, but I'm lazy. -- Eric Morgan
Re: automagically create browsable POD pages [pod2html]
On Apr 2, 2004, at 6:55 AM, Eric Lease Morgan wrote:
Thank you for the prompt replies, but the suggestions are overkill. I
simply want to:
1. create a doc directory
2. loop through my lib directory looking for pods
3. convert each pod to xhtml
4. save converted files to the pod directory
Like this, but there has got to be a better way:
#!/usr/bin/perl
use File::Basename;
use File::Find;
my $POD2HTML = 'pod2html';
my $IN = $ARGV[0];
my $OUT = $ARGV[1];
find (\process_files, $IN);
exit;
sub process_files {
# get the name of the found file
my $file = $File::Find::name;
# make it has the correct extension
next if ($file !~ m/\.pm$/);
# extract the necessary parts of the file name
(my $name, my $path, my $suffix) = File::Basename::fileparse($file,
'\..*');
my $cmd = $POD2HTML . --outfile=$OUT/$name.html --title=$name
$file;
print $cmd\n;
system $cmd;
}
--
Eric Lease Morgan
Re: automagically create browsable POD pages [pod2html]
Eric Lease Morgan wrote:
BTW, pod2html looks like it will already do this, but I can't figure
out how to make it:
1. create a single xhtml file for each pod
2. give each file a specific name
Yeah, I can't do this pod by pod, but I'm lazy.
I'm still not understanding what the problem is. Why can't you build
the docs pod-by-pod? Allow me to offer another suggestion that might be
the middle of the road your looking for. A single command line solution
based on pod2html.
Assume you start in your module build directory and that you want to
build your html docs from perl file in the lib subdirectory and put
html output in a subdirectory called ht
find lib -type f -name '*.(pm|pl)' -exec pod2html --htmldir=ht
--infile={} --outfile=ht/{}.html\;
Of course, if your using a makefile maybe you want to do some variation
of this that only build pods for specific parts that you might be
building separately. And of course you can have a separate install step
that copies the contents of the ht subdirectory to someplace you want
to install them.
--
Michael McDonnell, GCIA
Winterstorm Solutions, Inc.
[EMAIL PROTECTED]
Adding non standard MARC subfields with MARC::Record
Sirsi uses some non standard subfields to create links between records. Typically these subfields are '?' and '='. How can I add these non standard subfields to records that I am creating/editing with MARC::Record? Michael Michael L. Bowden Coordinator of Automation and Access Services Assistant Professor, Information Science Harrisburg Area Community College One HACC Drive Harrisburg, PA 17110-2999 E: [EMAIL PROTECTED] T: 717.780.1936 F: 717.780.2462
Re: Adding non standard MARC subfields with MARC::Record
On Fri, Apr 02, 2004 at 11:35:40AM -0500, Michael Bowden wrote: Sirsi uses some non standard subfields to create links between records. Typically these subfields are '?' and '='. How can I add these non standard subfields to records that I am creating/editing with MARC::Record? MARC::Record is actually quite lenient about what you can use as a subfield. $record-append_fields( MARC::Field-new( 245, 0, 0, '?' = 'foo', '=' = 'bar' ) ); Just make sure you quote '?' and '=' or else weirdness will ensue. :) //Ed
