[p5sagit/p5-mst-13.2.git] / t / pod / headings.t

BEGIN {
   use File::Basename;
   my $THISDIR = dirname $0;
   unshift @INC, $THISDIR;
   require "testp2pt.pl";
   import TestPodIncPlainText;
}

my %options = map { $_ => 1 } @ARGV;  ## convert cmdline to options-hash
my $passed  = testpodplaintext \%options, $0;
exit( ($passed == 1) ? 0 : -1 )  unless $ENV{HARNESS_ACTIVE};


__END__


#################################################################
  use Pod::Usage;
  pod2usage( VERBOSE => 2, EXIT => 1 );

=pod

=head1 NAME

B<rdb2pg> - insert an rdb table into a PostgreSQL database

=head1 SYNOPSIS

B<rdb2pg>  [I<param>=I<value> ...]

=head1 PARAMETERS

B<rdb2pg> uses an IRAF-compatible parameter interface.  
A template parameter file is in F</proj/axaf/simul/lib/uparm/rdb2pg.par>.

=over 4

=item B<input> I<file>

The B<RDB> file to insert into the database. If the given name
is the string C<stdin>, it reads from the UNIX standard input stream.


=back

=head1 DESCRIPTION

B<rdb2pg> will enter the data from an B<RDB> database into a
PostgreSQL database table, optionally creating the database and the
table if they do not exist.  It automatically determines the
PostgreSQL data type from the column definition in the B<RDB> file,
but may be overriden via a series of definition files or directly
via one of its parameters.

The target database and table are specified by the C<db> and C<table>
parameters.  If they do not exist, and the C<createdb> parameter is
set, they will be created.  Table field definitions are determined
in the following order:

=cut

#################################################################

results in:


#################################################################

    rdb2pg - insert an rdb table into a PostgreSQL database

    rdb2pg [*param*=*value* ...]

    rdb2pg uses an IRAF-compatible parameter interface. A template
    parameter file is in /proj/axaf/simul/lib/uparm/rdb2pg.par.

    The RDB file to insert into the database. If the given name is
    the string `stdin', it reads from the UNIX standard input
    stream.

    rdb2pg will enter the data from an RDB database into a
    PostgreSQL database table, optionally creating the database and
    the table if they do not exist. It automatically determines the
    PostgreSQL data type from the column definition in the RDB file,
    but may be overriden via a series of definition files or
    directly via one of its parameters.

    The target database and table are specified by the `db' and
    `table' parameters. If they do not exist, and the `createdb'
    parameter is set, they will be created. Table field definitions
    are determined in the following order:


#################################################################

while the original version of Text (using pod2text) gives

#################################################################

NAME
    rdb2pg - insert an rdb table into a PostgreSQL database

SYNOPSIS
    rdb2pg [*param*=*value* ...]

PARAMETERS
    rdb2pg uses an IRAF-compatible parameter interface. A template
    parameter file is in /proj/axaf/simul/lib/uparm/rdb2pg.par.

    input *file*
        The RDB file to insert into the database. If the given name
        is the string `stdin', it reads from the UNIX standard input
        stream.

DESCRIPTION
    rdb2pg will enter the data from an RDB database into a
    PostgreSQL database table, optionally creating the database and
    the table if they do not exist. It automatically determines the
    PostgreSQL data type from the column definition in the RDB file,
    but may be overriden via a series of definition files or
    directly via one of its parameters.

    The target database and table are specified by the `db' and
    `table' parameters. If they do not exist, and the `createdb'
    parameter is set, they will be created. Table field definitions
    are determined in the following order:


#################################################################


Thanks for any help.  If, as your email indicates, you've not much
time to look at this, I can work around things by calling pod2text()
directly using the official Text.pm.

Diab

-------------
Diab Jerius
djerius@cfa.harvard.edu
Commit	Line	Data
360aca43	1	BEGIN {
9c6ed6d7	2	use File::Basename;
	3	my $THISDIR = dirname $0;
	4	unshift @INC, $THISDIR;
360aca43	5	require "testp2pt.pl";
	6	import TestPodIncPlainText;
	7	}
	8
	9	my %options = map { $_ => 1 } @ARGV; ## convert cmdline to options-hash
	10	my $passed = testpodplaintext \%options, $0;
	11	exit( ($passed == 1) ? 0 : -1 ) unless $ENV{HARNESS_ACTIVE};
	12
	13
	14	__END__
	15
	16
	17	#################################################################
	18	use Pod::Usage;
	19	pod2usage( VERBOSE => 2, EXIT => 1 );
	20
	21	=pod
	22
	23	=head1 NAME
	24
	25	B<rdb2pg> - insert an rdb table into a PostgreSQL database
	26
	27	=head1 SYNOPSIS
	28
	29	B<rdb2pg> [I<param>=I<value> ...]
	30
	31	=head1 PARAMETERS
	32
	33	B<rdb2pg> uses an IRAF-compatible parameter interface.
	34	A template parameter file is in F</proj/axaf/simul/lib/uparm/rdb2pg.par>.
	35
	36	=over 4
	37
	38	=item B<input> I<file>
	39
	40	The B<RDB> file to insert into the database. If the given name
	41	is the string C<stdin>, it reads from the UNIX standard input stream.
	42
	43
	44	=back
	45
	46	=head1 DESCRIPTION
	47
	48	B<rdb2pg> will enter the data from an B<RDB> database into a
	49	PostgreSQL database table, optionally creating the database and the
	50	table if they do not exist. It automatically determines the
	51	PostgreSQL data type from the column definition in the B<RDB> file,
	52	but may be overriden via a series of definition files or directly
	53	via one of its parameters.
	54
	55	The target database and table are specified by the C<db> and C<table>
	56	parameters. If they do not exist, and the C<createdb> parameter is
	57	set, they will be created. Table field definitions are determined
	58	in the following order:
	59
	60	=cut
	61
	62	#################################################################
	63
	64	results in:
	65
	66
	67	#################################################################
	68
69	rdb2pg - insert an rdb table into a PostgreSQL database
70
71	rdb2pg [param=value ...]
72
73	rdb2pg uses an IRAF-compatible parameter interface. A template
74	parameter file is in /proj/axaf/simul/lib/uparm/rdb2pg.par.
75
76	The RDB file to insert into the database. If the given name is
77	the string `stdin', it reads from the UNIX standard input
78	stream.
79
80	rdb2pg will enter the data from an RDB database into a
81	PostgreSQL database table, optionally creating the database and
82	the table if they do not exist. It automatically determines the
83	PostgreSQL data type from the column definition in the RDB file,
84	but may be overriden via a series of definition files or
85	directly via one of its parameters.
86
87	The target database and table are specified by the `db' and
88	`table' parameters. If they do not exist, and the `createdb'
89	parameter is set, they will be created. Table field definitions
90	are determined in the following order:
91
92
93	#################################################################
94
95	while the original version of Text (using pod2text) gives
96
97	#################################################################
98
99	NAME
100	rdb2pg - insert an rdb table into a PostgreSQL database
101
102	SYNOPSIS
103	rdb2pg [param=value ...]
104
105	PARAMETERS
106	rdb2pg uses an IRAF-compatible parameter interface. A template
107	parameter file is in /proj/axaf/simul/lib/uparm/rdb2pg.par.
108
109	input file
110	The RDB file to insert into the database. If the given name
111	is the string `stdin', it reads from the UNIX standard input
112	stream.
113
114	DESCRIPTION
115	rdb2pg will enter the data from an RDB database into a
116	PostgreSQL database table, optionally creating the database and
117	the table if they do not exist. It automatically determines the
118	PostgreSQL data type from the column definition in the RDB file,
119	but may be overriden via a series of definition files or
120	directly via one of its parameters.
121
122	The target database and table are specified by the `db' and
123	`table' parameters. If they do not exist, and the `createdb'
124	parameter is set, they will be created. Table field definitions
125	are determined in the following order:
126
127
128	#################################################################
129
130
131	Thanks for any help. If, as your email indicates, you've not much
132	time to look at this, I can work around things by calling pod2text()
133	directly using the official Text.pm.
134
135	Diab
136
137	-------------
138	Diab Jerius
139	djerius@cfa.harvard.edu
140