Re: [openssl.org #333] x509.pod
Lutz Jaenicke via RT wrote: On Thu, Nov 14, 2002 at 12:25:15PM +0100, Ernst G Giessmann via RT wrote: I guess that in this case =head1 B is less opportunistic and therefore a bit better workaround saving the section name for the next generation ;-) Ok, I have finally chosen another workaround: as NAME OPTIONS are just a subset of all OPTIONS, I have adjusted the structre, such now NAME OPTIONS is only a =head2 section and does not longer create the problem. Best regards, Lutz Fine, I guess that the TEXT OPTIONS became a head2 section too, isn't it? BTW the problem in the 0.9.7 version didn't appear because the dirty section is renamed to Subject and Issuer name options ;-) Regards, Ernst __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [openssl.org #333] x509.pod
On Tue, Nov 19, 2002 at 09:18:13AM +0100, Ernst G Giessmann via RT wrote: Lutz Jaenicke via RT wrote: On Thu, Nov 14, 2002 at 12:25:15PM +0100, Ernst G Giessmann via RT wrote: I guess that in this case =head1 B is less opportunistic and therefore a bit better workaround saving the section name for the next generation ;-) Ok, I have finally chosen another workaround: as NAME OPTIONS are just a subset of all OPTIONS, I have adjusted the structre, such now NAME OPTIONS is only a =head2 section and does not longer create the problem. Best regards, Lutz Fine, I guess that the TEXT OPTIONS became a head2 section too, isn't it? Yes. I have adapted the structures accordingly, such that all BLAH OPTIONS are subsections of the OPTIONS section. BTW the problem in the 0.9.7 version didn't appear because the dirty section is renamed to Subject and Issuer name options ;-) This was the first workaround that now has been reverted. Best regards, Lutz -- Lutz Jaenicke [EMAIL PROTECTED] http://www.aet.TU-Cottbus.DE/personen/jaenicke/ BTU Cottbus, Allgemeine Elektrotechnik Universitaetsplatz 3-4, D-03044 Cottbus __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [openssl.org #333] x509.pod
On Thu, Nov 14, 2002 at 12:25:15PM +0100, Ernst G Giessmann via RT wrote: I guess that in this case =head1 BNAME OPTIONS is less opportunistic and therefore a bit better workaround saving the section name for the next generation ;-) Ok, I have finally chosen another workaround: as NAME OPTIONS are just a subset of all OPTIONS, I have adjusted the structre, such now NAME OPTIONS is only a =head2 section and does not longer create the problem. Best regards, Lutz -- Lutz Jaenicke [EMAIL PROTECTED] http://www.aet.TU-Cottbus.DE/personen/jaenicke/ BTU Cottbus, Allgemeine Elektrotechnik Universitaetsplatz 3-4, D-03044 Cottbus __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [openssl.org #333] x509.pod
Lutz Jaenicke via RT wrote: [[EMAIL PROTECTED] - Fri Nov 8 12:19:04 2002]: Dear all, I identified that the Documentation in doc/apps/x509.pod is wrong if passed through pod2latex. The line =head1 NAME OPTIONS causes a wrong representation in the tex-File (and maybe in others too) I'm not a perl guru, I fixed it by surrounding =head1 BNAME OPTIONS Hmm, I just checked with pod2latex of perl 5.6.1 and cannot find any problems in the handling of =head1 ... Best regards, Lutz Hi Lutz, the problem is in fact not in the handling of =head1 instruction. It encounters after pod2latex -full -modify -out main.tex *.pod and is in the misinterpretation of the =head1 NAME string in the modify mode. Run in your doc/apps directory fgrep =head1 NAME *.pod you'll get CA.pl.pod:=head1 NAME asn1parse.pod:=head1 NAME ...more files spkac.pod:=head1 NAME verify.pod:=head1 NAME version.pod:=head1 NAME x509.pod:=head1 NAME x509.pod:=head1 NAME OPTIONS all but the last are fine here. How one can stop the pod2latex to misunderstand the =head1 NAME OPTIONS string? Regards, Ernst -- Ernst G Giessmann (ES22a) T-Systems GmbH ITC-Security Goslarer Ufer 35, D-10589 Berlin phone:+49-30-3497-4342 mailto:ErnstG.Giessmann;t-systems.com __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [openssl.org #333] x509.pod
In message [EMAIL PROTECTED] on Thu, 14 Nov 2002 11:24:16
+0100 (MET), Ernst G Giessmann via RT [EMAIL PROTECTED] said:
rt Run in your doc/apps directory
rt
rt fgrep =head1 NAME *.pod
rt
rt you'll get
rt
rt CA.pl.pod:=head1 NAME
rt asn1parse.pod:=head1 NAME
rt ...more files
rt spkac.pod:=head1 NAME
rt verify.pod:=head1 NAME
rt version.pod:=head1 NAME
rt x509.pod:=head1 NAME
rt x509.pod:=head1 NAME OPTIONS
rt
rt all but the last are fine here. How one can stop the pod2latex to
rt misunderstand the =head1 NAME OPTIONS string?
Hmm, I can't see any way to stop pod2latex, except maybe changing the
following line in Pod::LaTeX:
if ($self-{_CURRENT_HEAD1} =~ /^NAME/i $self-ReplaceNAMEwithSection()) {
to:
if ($self-{_CURRENT_HEAD1} =~ /^NAME\s*$/i $self-ReplaceNAMEwithSection()) {
This might be a worthy bug report to the authors of the Pod system.
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
\ SWEDEN \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Unsolicited commercial email is subject to an archival fee of $400.
See http://www.stacken.kth.se/~levitte/mail/ for more info.
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
Re: [openssl.org #333] x509.pod
In message [EMAIL PROTECTED] on Thu, 14 Nov 2002 11:24:16
+0100 (MET), Ernst G Giessmann via RT [EMAIL PROTECTED] said:
rt Run in your doc/apps directory
rt
rt fgrep =head1 NAME *.pod
rt
rt you'll get
rt
rt CA.pl.pod:=head1 NAME
rt asn1parse.pod:=head1 NAME
rt ...more files
rt spkac.pod:=head1 NAME
rt verify.pod:=head1 NAME
rt version.pod:=head1 NAME
rt x509.pod:=head1 NAME
rt x509.pod:=head1 NAME OPTIONS
rt
rt all but the last are fine here. How one can stop the pod2latex to
rt misunderstand the =head1 NAME OPTIONS string?
Hmm, I can't see any way to stop pod2latex, except maybe changing the
following line in Pod::LaTeX:
if ($self-{_CURRENT_HEAD1} =~ /^NAME/i $self-ReplaceNAMEwithSection()) {
to:
if ($self-{_CURRENT_HEAD1} =~ /^NAME\s*$/i $self-ReplaceNAMEwithSection()) {
This might be a worthy bug report to the authors of the Pod system.
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
\ SWEDEN \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Unsolicited commercial email is subject to an archival fee of $400.
See http://www.stacken.kth.se/~levitte/mail/ for more info.
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
AW: [openssl.org #333] x509.pod
-Urspr üngliche Nachricht-
Von: Lutz Jaenicke via RT [SMTP:[EMAIL PROTECTED]]
Gesendet am: Donnerstag, 14. November 2002 12:15
An: Giessmann, Ernstg
Cc: [EMAIL PROTECTED]
Betreff: [openssl.org #333] x509.pod
[[EMAIL PROTECTED] - Thu Nov 14 11:47:20 2002]:
In message [EMAIL PROTECTED] on Thu, 14 Nov
2002 11:24:16 +0100 (MET), Ernst G Giessmann via RT [EMAIL PROTECTED]
said:
rt Run in your doc/apps directory
rt
rt fgrep =head1 NAME *.pod
rt
rt you'll get
rt
rt CA.pl.pod:=head1 NAME
rt asn1parse.pod:=head1 NAME
rt ...more files
rt spkac.pod:=head1 NAME
rt verify.pod:=head1 NAME
rt version.pod:=head1 NAME
rt x509.pod:=head1 NAME
rt x509.pod:=head1 NAME OPTIONS
rt
rt all but the last are fine here. How one can stop the pod2latex to
rt misunderstand the =head1 NAME OPTIONS string?
Hmm, I can't see any way to stop pod2latex, except maybe changing the
following line in Pod::LaTeX:
if ($self-{_CURRENT_HEAD1} =~ /^NAME/i $self-
ReplaceNAMEwithSection()) {
to:
if ($self-{_CURRENT_HEAD1} =~ /^NAME\s*$/i $self-
ReplaceNAMEwithSection()) {
This might be a worthy bug report to the authors of POD.
Probably this is a bug in the POD handling.
In any case I have chosen the opportunistic approach and changed the
name of the section :-)
Hi Lutz,
I guess that in this case
=head1 BNAME OPTIONS
is less opportunistic and therefore a bit better workaround saving the section
name for the next generation ;-)
Ernst
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
[openssl.org #333] x509.pod
[[EMAIL PROTECTED] - Fri Nov 8 12:19:04 2002]: Dear all, I identified that the Documentation in doc/apps/x509.pod is wrong if passed through pod2latex. The line =head1 NAME OPTIONS causes a wrong representation in the tex-File (and maybe in others too) I'm not a perl guru, I fixed it by surrounding =head1 BNAME OPTIONS Hmm, I just checked with pod2latex of perl 5.6.1 and cannot find any problems in the handling of =head1 ... Best regards, Lutz __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
[openssl.org #333] x509.pod
Dear all, I identified that the Documentation in doc/apps/x509.pod is wrong if passed through pod2latex. The line =head1 NAME OPTIONS causes a wrong representation in the tex-File (and maybe in others too) I'm not a perl guru, I fixed it by surrounding =head1 BNAME OPTIONS Happy TeXing Ernst __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
