aboutsummaryrefslogtreecommitdiffstats
path: root/gcc-4.8/libjava/classpath/doc
diff options
context:
space:
mode:
Diffstat (limited to 'gcc-4.8/libjava/classpath/doc')
-rw-r--r--gcc-4.8/libjava/classpath/doc/cp-tools.info288
-rw-r--r--gcc-4.8/libjava/classpath/doc/gappletviewer.120
-rw-r--r--gcc-4.8/libjava/classpath/doc/gjar.120
-rw-r--r--gcc-4.8/libjava/classpath/doc/gjarsigner.120
-rw-r--r--gcc-4.8/libjava/classpath/doc/gjavah.120
-rw-r--r--gcc-4.8/libjava/classpath/doc/gjdoc.142
-rw-r--r--gcc-4.8/libjava/classpath/doc/gkeytool.120
-rw-r--r--gcc-4.8/libjava/classpath/doc/gnative2ascii.120
-rw-r--r--gcc-4.8/libjava/classpath/doc/gorbd.120
-rw-r--r--gcc-4.8/libjava/classpath/doc/grmid.120
-rw-r--r--gcc-4.8/libjava/classpath/doc/grmiregistry.120
-rw-r--r--gcc-4.8/libjava/classpath/doc/gserialver.120
-rw-r--r--gcc-4.8/libjava/classpath/doc/gtnameserv.120
13 files changed, 323 insertions, 227 deletions
diff --git a/gcc-4.8/libjava/classpath/doc/cp-tools.info b/gcc-4.8/libjava/classpath/doc/cp-tools.info
index 66606220d..7b9ebafa6 100644
--- a/gcc-4.8/libjava/classpath/doc/cp-tools.info
+++ b/gcc-4.8/libjava/classpath/doc/cp-tools.info
@@ -1,5 +1,5 @@
-This is cp-tools.info, produced by makeinfo version 4.13 from
-/d/gcc-4.8.1/gcc-4.8.1/libjava/classpath/doc/cp-tools.texinfo.
+This is cp-tools.info, produced by makeinfo version 4.12 from
+/space/rguenther/gcc-4.8.3/gcc-4.8.3/libjava/classpath/doc/cp-tools.texinfo.
This file documents the Tools included in a standard distribution of
the GNU Classpath project deliverables.
@@ -343,7 +343,7 @@ signed JAR file.
form is used, or to verify if the second syntax form is used instead.
ALIAS must be a known Alias of a Key Entry in the designated Key
-Store. The private key material associated with this Alias is then used
+Store. The private key material associated with this Alias is then used
for signing the designated .JAR file.
* Menu:
@@ -379,7 +379,7 @@ signing, or verifying, a .JAR file.
`-provider PROVIDER_CLASS_NAME'
A fully qualified class name of a Security Provider to add to the
current list of Security Providers already installed in the JVM
- in-use. If a provider class is specified with this option, and was
+ in-use. If a provider class is specified with this option, and was
successfully added to the runtime -i.e. it was not already
installed- then the tool will attempt to remove this Security
Provider before exiting.
@@ -410,7 +410,7 @@ purposes.
key store -as if the protocol was `file:'.
`-storetype STORE_TYPE'
- Use this option to specify the type of the key store to use. The
+ Use this option to specify the type of the key store to use. The
default value, if this option is omitted, is that of the property
`keystore.type' in the security properties file, which is obtained
by invoking the static method call `getDefaultType()' in
@@ -418,7 +418,7 @@ purposes.
`-storepass PASSWORD'
Use this option to specify the password which will be used to
- unlock the key store. If this option is missing, the User will be
+ unlock the key store. If this option is missing, the User will be
prompted to provide a password.
`-keypass PASSWORD'
@@ -426,7 +426,7 @@ purposes.
unlock the Key Entry associated with the designated Alias.
If this option is omitted, the tool will first attempt to unlock
- the Key Entry using the same password protecting the key store. If
+ the Key Entry using the same password protecting the key store. If
this fails, you will then be prompted to provide a password.
`-sigfile NAME'
@@ -438,12 +438,12 @@ purposes.
characters will be converted to upper-case ones.
If this option is missing, the first eight characters of the ALIAS
- argument will be used. When this is the case, any character in
+ argument will be used. When this is the case, any character in
ALIAS that is outside the permissible range of characters will be
replaced by an underscore.
`-signedjar FILE'
- Use this option to specify the file name of the signed JAR. If
+ Use this option to specify the file name of the signed JAR. If
this option is omitted, then the signed JAR will be named the same
as FILE; i.e., the input JAR file will be replaced with the signed
copy.
@@ -476,7 +476,7 @@ File: cp-tools.info, Node: keytool Tool, Prev: jarsigner Tool, Up: Security T
======================
Cryptographic credentials, in a Java environment, are usually stored in
-a Key Store. The Java SDK specifies a Key Store as a persistent
+a Key Store. The Java SDK specifies a Key Store as a persistent
container of two types of objects: Key Entries and Trusted
Certificates. The security tool `keytool' is a Java-based application
for managing those types of objects.
@@ -484,11 +484,11 @@ for managing those types of objects.
A Key Entry represents the private key part of a key-pair used in
Public-Key Cryptography, and a signed X.509 certificate which
authenticates the public key part for a known entity; i.e. the owner of
-the key-pair. The X.509 certificate itself contains the public key part
+the key-pair. The X.509 certificate itself contains the public key part
of the key-pair.
A Trusted Certificate is a signed X.509 certificate issued by a
-trusted entity. The Trust in this context is relative to the User of
+trusted entity. The Trust in this context is relative to the User of
the `keytool'. In other words, the existence of a Trusted Certificate
in the Key Store processed by a `keytool' command implies that the User
trusts the Issuer of that Trusted Certificate to also sign, and hence
@@ -497,7 +497,7 @@ authenticates, other Subjects the tool may process.
Trusted Certificates are important because they allow the tool to
mechanically construct Chains of Trust starting from one of the Trusted
Certificates in a Key Store and ending with a certificate whose Issuer
-is potentially unknown. A valid chain is an ordered list, starting with
+is potentially unknown. A valid chain is an ordered list, starting with
a Trusted Certificate (also called the anchor), ending with the target
certificate, and satisfying the condition that the Subject of
certificate `#i' is the Issuer of certificate `#i + 1'.
@@ -598,7 +598,7 @@ the `-help' option for that command; e.g.
exit the running JVM.
It is worth noting here that the help messages printed by the tool
-are I18N-ready. This means that if/when the contents of the tool's
+are I18N-ready. This means that if/when the contents of the tool's
Message Bundle properties file are available in languages other than
English, you may see those messages in that language.
@@ -613,9 +613,9 @@ described here to reduce redundancy.
`-alias ALIAS'
Every entry, be it a Key Entry or a Trusted Certificate, in a key
- store is uniquely identified by a user-defined ALIAS string. Use
+ store is uniquely identified by a user-defined ALIAS string. Use
this option to specify the ALIAS to use when referring to an entry
- in the key store. Unless specified otherwise, a default value of
+ in the key store. Unless specified otherwise, a default value of
`mykey' shall be used when this option is omitted from the command
line.
@@ -636,7 +636,7 @@ described here to reduce redundancy.
this option is omitted from the command line.
`-storetype STORE_TYPE'
- Use this option to specify the type of the key store to use. The
+ Use this option to specify the type of the key store to use. The
default value, if this option is omitted, is that of the property
`keystore.type' in the security properties file, which is obtained
by invoking the static method call `getDefaultType()' in
@@ -662,16 +662,16 @@ described here to reduce redundancy.
`-provider PROVIDER_CLASS_NAME'
A fully qualified class name of a Security Provider to add to the
current list of Security Providers already installed in the JVM
- in-use. If a provider class is specified with this option, and was
+ in-use. If a provider class is specified with this option, and was
successfully added to the runtime -i.e. it was not already
installed- then the tool will attempt to removed this Security
Provider before exiting.
`-file FILE'
- Use this option to designate a file to use with a command. When
+ Use this option to designate a file to use with a command. When
specified with this option, the value is expected to be the fully
- qualified path of a file accessible by the File System. Depending
- on the command, the file may be used as input or as output. When
+ qualified path of a file accessible by the File System. Depending
+ on the command, the file may be used as input or as output. When
this option is omitted from the command line, `STDIN' will be used
instead, as the source of input, and `STDOUT' will be used instead
as the output destination.
@@ -689,8 +689,8 @@ File: cp-tools.info, Node: Distinguished Names, Next: Add/Update Commands, Pr
A Distinguished Name (or DN) MUST be supplied with some of the
`COMMAND's using a `-dname' option. The syntax of a valid value for
-this option MUST follow RFC-2253 specifications. Namely the following
-components (with their accepted meaning) will be recognized. Note that
+this option MUST follow RFC-2253 specifications. Namely the following
+components (with their accepted meaning) will be recognized. Note that
the component name is case-insensitive:
CN
@@ -712,8 +712,8 @@ C
The 2-letter Country identifier; e.g. `AU'
When specified with a `-dname' option, each pair of component/value
-will be separated from the other with a comma. Each component and value
-pair MUST be separated by an equal sign. For example, the following is
+will be separated from the other with a comma. Each component and value
+pair MUST be separated by an equal sign. For example, the following is
a valid DN value:
CN=host.domain.com, O=The Sample Company, L=Sydney, ST=NSW, C=AU
@@ -762,16 +762,16 @@ chain and will be saved in the key store.
`-sigalg ALGORITHM'
The canonical name of the digital signature algorithm to use for
- signing certificates. If this option is omitted, a default value
+ signing certificates. If this option is omitted, a default value
will be chosen based on the type of the key-pair; i.e., the
- algorithm that ends up being used by the -keyalg option. If the
+ algorithm that ends up being used by the -keyalg option. If the
key-pair generation algorithm is `DSA', the value for the
signature algorithm will be `SHA1withDSA'. If on the other hand
the key-pair generation algorithm is `RSA', then the tool will use
`MD5withRSA' as the signature algorithm.
`-dname NAME'
- This a mandatory value for the command. If no value is specified
+ This a mandatory value for the command. If no value is specified
-i.e. the `-dname' option is omitted- the tool will prompt you to
enter a Distinguished Name to use as both the Owner and Issuer of
the generated self-signed certificate.
@@ -830,7 +830,7 @@ confirmation.
If Alias exists in the key store, the tool will treat the
certificate(s) read from the input source as a Certificate Reply, which
can be a chain of certificates, that eventually would replace the chain
-of certificates associated with the Key Entry of that Alias. The
+of certificates associated with the Key Entry of that Alias. The
substitution of the certificates only occurs if a chain-of-trust can be
established between the bottom certificate of the chain read from the
input file and the Trusted Certificates already present in the key
@@ -899,9 +899,9 @@ option was omitted).
`-sigalg ALGORITHM'
The canonical name of the digital signature algorithm to use for
- signing the certificate. If this option is omitted, a default
+ signing the certificate. If this option is omitted, a default
value will be chosen based on the type of the private key
- associated with the designated Alias. If the private key is a
+ associated with the designated Alias. If the private key is a
`DSA' one, the value for the signature algorithm will be
`SHA1withDSA'. If on the other hand the private key is an `RSA'
one, then the tool will use `MD5withRSA' as the signature
@@ -909,7 +909,7 @@ option was omitted).
`-dname NAME'
Use this option to specify the Distinguished Name of the newly
- generated self-signed certificate. If this option is omitted, the
+ generated self-signed certificate. If this option is omitted, the
existing Distinguished Name of the base certificate in the chain
associated with the designated Alias will be used instead.
@@ -923,7 +923,7 @@ option was omitted).
unlock the Key Entry associated with the designated Alias.
If this option is omitted, the tool will first attempt to unlock
- the Key Entry using the same password protecting the key store. If
+ the Key Entry using the same password protecting the key store. If
this fails, you will then be prompted to provide a password.
`-storetype STORE_TYPE'
@@ -1036,7 +1036,7 @@ the destination should look something like the following:
IMPORTANT: Some documentation (e.g. RSA examples) claims that the
`Attributes' field, in the CSR is `OPTIONAL' while RFC-2986 implies the
-opposite. This implementation considers this field, by default, as
+opposite. This implementation considers this field, by default, as
`OPTIONAL', unless the option `-attributes' is specified on the command
line.
@@ -1045,9 +1045,9 @@ line.
`-sigalg ALGORITHM'
The canonical name of the digital signature algorithm to use for
- signing the certificate. If this option is omitted, a default
+ signing the certificate. If this option is omitted, a default
value will be chosen based on the type of the private key
- associated with the designated Alias. If the private key is a
+ associated with the designated Alias. If the private key is a
`DSA' one, the value for the signature algorithm will be
`SHA1withDSA'. If on the other hand the private key is an `RSA'
one, then the tool will use `MD5withRSA' as the signature
@@ -1061,7 +1061,7 @@ line.
unlock the Key Entry associated with the designated Alias.
If this option is omitted, the tool will first attempt to unlock
- the Key Entry using the same password protecting the key store. If
+ the Key Entry using the same password protecting the key store. If
this fails, you will then be prompted to provide a password.
`-storetype STORE_TYPE'
@@ -1117,9 +1117,9 @@ option is specified instead).
Use RFC-1421 specifications when encoding the output.
`-v'
- Output the certificate in binary DER encoding. This is the default
+ Output the certificate in binary DER encoding. This is the default
output format of the command if neither `-rfc' nor `-v' options
- were detected on the command line. If both this option and the
+ were detected on the command line. If both this option and the
`-rfc' option are detected on the command line, the tool will opt
for the RFC-1421 style encoding.
@@ -1167,7 +1167,7 @@ certificate, unless either the `-rfc' or the `-v' option is specified.
Use RFC-1421 specifications when encoding the output.
`-v'
- Output the certificate in human-readable format. If both this
+ Output the certificate in human-readable format. If both this
option and the `-rfc' option are detected on the command line, the
tool will opt for the human-readable form and will not abort the
command.
@@ -1224,7 +1224,7 @@ possibly a new password.
unlock the Key Entry associated with the designated Alias.
If this option is omitted, the tool will first attempt to unlock
- the Key Entry using the same password protecting the key store. If
+ the Key Entry using the same password protecting the key store. If
this fails, you will then be prompted to provide a password.
`-new PASSWORD'
@@ -1291,7 +1291,7 @@ material of a designated Key Entry.
unlock the Key Entry associated with the designated Alias.
If this option is omitted, the tool will first attempt to unlock
- the Key Entry using the same password protecting the key store. If
+ the Key Entry using the same password protecting the key store. If
this fails, you will then be prompted to provide a password.
`-new PASSWORD'
@@ -1745,7 +1745,7 @@ File: cp-tools.info, Node: gjdoc Tool, Prev: tnameserv Tool, Up: Other Tools
*******************************
Gjdoc can be used in two ways: as a stand-alone documentation tool, or
-as a driver for a user-specified Doclet. *Note Other Doclets::.
+as a driver for a user-specified Doclet. *Note Other Doclets::.
In the default mode, Gjdoc will use the Standard Doclet `HtmlDoclet'
to generate a set of HTML pages. The canonical usage is:
@@ -1966,7 +1966,7 @@ File: cp-tools.info, Node: Source Format Options, Next: Interlinking Options,
This option should be specified when applying `gjdoc' to source
code commented in a non-latin language for which the default first
- sentence detector does not work. For all other cases, the default
+ sentence detector does not work. For all other cases, the default
(do not use BreakIterator) produces better results at the time of
this writing.
@@ -1983,7 +1983,7 @@ File: cp-tools.info, Node: Interlinking Options, Next: Output Control Options,
source set. Use this option to additionally create hyperlinks to
classes covered by the specified documentation set.
- URL should be the root URL of the other documentation set. For
+ URL should be the root URL of the other documentation set. For
example, to add hyperlinks to GNU Classpath, specify the following:
-link http://developer.classpath.org/doc/
@@ -2141,7 +2141,7 @@ File: cp-tools.info, Node: Generation Options, Next: Decoration Options, Prev
of a class documentation page.
`-use'
- Generate a page with cross-reference information. By default, this
+ Generate a page with cross-reference information. By default, this
page is not generated.
The cross-reference information can be accessed by clicking on the
@@ -2468,7 +2468,7 @@ File: cp-tools.info, Node: Output Control Options, Next: Generation Options,
identifiers.
`-charset CHARSET'
- _Deprecated._ Override the specified encoding in output XHTML
+ _Deprecated._ Override the specified encoding in output XHTML
files with the one given by `charset'.
If this option is not given, the encoding specification in output
@@ -2805,7 +2805,7 @@ following benefits:
If you derive from `AbstractDoclet', there are a number of things
you need to take care of:
- *
+ *
you should not implement the `start(RootDoc)' method as it is
already defined by `AbstractDoclet' so that it can care about parsing
the options.
@@ -2999,16 +2999,16 @@ templates they use at runtime to generate the message text itself,
depending on the locale in use at the time.
The Resource Bundles these tools use are essentially Java Properties
-files consisting of a set of Name/Value pairs. The Name is the Property
+files consisting of a set of Name/Value pairs. The Name is the Property
Name and the Value is a substitution string that is used when the code
-references the associated Name. For example the following is a line in
+references the associated Name. For example the following is a line in
a Resource Bundle used by the `keytool' Tool:
Command.23=A correct key password MUST be provided
When the tool needs to signal a mandatory but missing key password,
it would reference the property named `Command.23' and the message "`A
-correct key password MUST be provided'" will be used instead. This
+correct key password MUST be provided'" will be used instead. This
indirect referencing of "resources" permits replacing, as late as
possible, the English strings with strings in other languages, provided
of course Resource Bundles in those languages are provided.
@@ -3027,12 +3027,12 @@ VV
The complete list of language codes can be found at Code for the
representation of names of languages
-(http://ftp.ics.uci.edu/pub/ietf/http/related/iso639.txt). A similar
+(http://ftp.ics.uci.edu/pub/ietf/http/related/iso639.txt). A similar
list for the region codes can be found at ISO 3166 Codes (Countries)
(http://userpage.chemie.fu-berlin.de/diverse/doc/ISO_3166.html).
The location of the Resource Bundles for the GNU Classpath Tools is
-specific to each tool. The next table shows where these files are found
+specific to each tool. The next table shows where these files are found
in a standard GNU Classpath distribution:
`jarsigner'
@@ -3042,7 +3042,7 @@ in a standard GNU Classpath distribution:
`gnu/classpath/tools/keytool'
The collection of Resource Bundles in a location act as an inverted
-tree with a parent-child relationship. For example suppose in the
+tree with a parent-child relationship. For example suppose in the
`gnu/classpath/tools/keytool' there are 3 message bundles named:
1. `messages.properties'
@@ -3052,7 +3052,7 @@ tree with a parent-child relationship. For example suppose in the
3. `messages_fr_FR.properties'
In the above example, bundle #1 will act as the parent of bundle #2,
-which in turn will act as the parent for bundle #3. This ordering is
+which in turn will act as the parent for bundle #3. This ordering is
used by the Java runtime to choose which file to load based on the set
Locale. For example if the Locale is `fr_CH', `messages_fr.properties'
will be used because (a) `messages_fr_CH.properties' does not exist,
@@ -3067,7 +3067,7 @@ the hierarchy.
You can see from the examples above that `messages.properties' is
the safety net that the Java runtime falls back to when failing to find
a specific bundle and its parent(s). This file is always provided with
-the Tool. In time, more localized versions will be included to cater
+the Tool. In time, more localized versions will be included to cater
for other languages.
In the meantime, if you are willing to contribute localized versions
@@ -3099,93 +3099,93 @@ alter text between curly braces.

Tag Table:
-Node: Top1150
-Node: Applet Tools6870
-Node: appletviewer Tool7443
-Node: gcjwebplugin10558
-Node: Security Tools10870
-Node: jarsigner Tool11523
-Node: Common jarsigner Options12571
-Node: Signing Options13886
-Node: Verification Options16469
-Node: keytool Tool17057
-Node: Getting Help21485
-Node: Common keytool Options22229
-Ref: alias22502
-Ref: keyalg22884
-Ref: keysize23114
-Ref: validity23379
-Ref: storetype23594
-Ref: storepass23925
-Ref: keystore24122
-Ref: provider24665
-Ref: file25072
-Ref: verbose25543
-Node: Distinguished Names25635
-Ref: dn25829
-Node: Add/Update Commands26892
-Node: Command -genkey27420
-Node: Command -import29829
-Node: Command -selfcert32973
-Node: Command -cacert35152
-Node: Command -identitydb36205
-Node: Export Commands36863
-Node: Command -certreq37179
-Node: Command -export39585
-Node: Display Commands40782
-Node: Command -list41114
-Node: Command -printcert42247
-Node: Management Commands42631
-Node: Command -keyclone43063
-Node: Command -storepasswd44466
-Node: Command -keypasswd45195
-Node: Command -delete46389
-Node: Other Tools47012
-Node: jar Tool47854
-Node: javah Tool49246
-Node: gcjh Tool50465
-Node: native2ascii Tool51578
-Node: orbd Tool52039
-Node: serialver Tool52769
-Node: rmid Tool53238
-Node: rmiregistry Tool54179
-Node: tnameserv Tool55019
-Node: gjdoc Tool55643
-Node: Invoking the Standard Doclet57631
-Node: Option Summary by Type58786
-Node: Source Set Options61216
-Node: Source Format Options63080
-Node: Interlinking Options64594
-Node: Generation Options67371
-Node: Taglet Options73468
-Node: Doclet Options75695
-Node: Decoration Options77271
-Node: Output Control Options81362
-Node: Verbosity Options84894
-Node: Virtual Machine Options85240
-Node: Invoking a Custom Doclet86636
-Node: Gjdoc Option Summary87311
-Node: Other Doclets87491
-Node: Built-in Doclets87719
-Node: Using TexiDoclet87974
-Node: Using XmlDoclet88196
-Node: Using IspellDoclet88421
-Node: Using DebugDoclet88649
-Node: Third-party Doclets88849
-Node: DocBook Doclet89065
-Node: PDFDoclet89208
-Node: JUnitDoclet89361
-Node: Gjdoc Concepts89495
-Node: Taglets89739
-Node: Writing Doclets89922
-Node: Doclet Invocation Interface90262
-Node: Using AbstractDoclet91054
-Node: GNU Doclet SPI94048
-Node: XHTML Fragments95520
-Node: First Sentence Detector96953
-Node: Adding Custom Resources98715
-Node: I18N Issues100411
-Node: Language Resources100913
-Node: Message Formats104577
+Node: Top1164
+Node: Applet Tools6884
+Node: appletviewer Tool7457
+Node: gcjwebplugin10572
+Node: Security Tools10884
+Node: jarsigner Tool11537
+Node: Common jarsigner Options12585
+Node: Signing Options13900
+Node: Verification Options16483
+Node: keytool Tool17071
+Node: Getting Help21499
+Node: Common keytool Options22243
+Ref: alias22516
+Ref: keyalg22898
+Ref: keysize23128
+Ref: validity23393
+Ref: storetype23608
+Ref: storepass23939
+Ref: keystore24136
+Ref: provider24679
+Ref: file25086
+Ref: verbose25557
+Node: Distinguished Names25649
+Ref: dn25843
+Node: Add/Update Commands26906
+Node: Command -genkey27434
+Node: Command -import29843
+Node: Command -selfcert32987
+Node: Command -cacert35166
+Node: Command -identitydb36219
+Node: Export Commands36877
+Node: Command -certreq37193
+Node: Command -export39599
+Node: Display Commands40796
+Node: Command -list41128
+Node: Command -printcert42261
+Node: Management Commands42645
+Node: Command -keyclone43077
+Node: Command -storepasswd44480
+Node: Command -keypasswd45209
+Node: Command -delete46403
+Node: Other Tools47026
+Node: jar Tool47868
+Node: javah Tool49260
+Node: gcjh Tool50479
+Node: native2ascii Tool51592
+Node: orbd Tool52053
+Node: serialver Tool52783
+Node: rmid Tool53252
+Node: rmiregistry Tool54193
+Node: tnameserv Tool55033
+Node: gjdoc Tool55657
+Node: Invoking the Standard Doclet57645
+Node: Option Summary by Type58800
+Node: Source Set Options61230
+Node: Source Format Options63094
+Node: Interlinking Options64608
+Node: Generation Options67385
+Node: Taglet Options73482
+Node: Doclet Options75709
+Node: Decoration Options77285
+Node: Output Control Options81376
+Node: Verbosity Options84908
+Node: Virtual Machine Options85254
+Node: Invoking a Custom Doclet86650
+Node: Gjdoc Option Summary87325
+Node: Other Doclets87505
+Node: Built-in Doclets87733
+Node: Using TexiDoclet87988
+Node: Using XmlDoclet88210
+Node: Using IspellDoclet88435
+Node: Using DebugDoclet88663
+Node: Third-party Doclets88863
+Node: DocBook Doclet89079
+Node: PDFDoclet89222
+Node: JUnitDoclet89375
+Node: Gjdoc Concepts89509
+Node: Taglets89753
+Node: Writing Doclets89936
+Node: Doclet Invocation Interface90276
+Node: Using AbstractDoclet91068
+Node: GNU Doclet SPI94062
+Node: XHTML Fragments95534
+Node: First Sentence Detector96967
+Node: Adding Custom Resources98729
+Node: I18N Issues100425
+Node: Language Resources100927
+Node: Message Formats104591

End Tag Table
diff --git a/gcc-4.8/libjava/classpath/doc/gappletviewer.1 b/gcc-4.8/libjava/classpath/doc/gappletviewer.1
index 992ecaf16..7fe673835 100644
--- a/gcc-4.8/libjava/classpath/doc/gappletviewer.1
+++ b/gcc-4.8/libjava/classpath/doc/gappletviewer.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -45,14 +53,14 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.ie \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-. nr % 0
+. nr % 0
. rr F
.\}
.el \{\
@@ -124,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GAPPLETVIEWER 1"
-.TH GAPPLETVIEWER 1 "2013-05-31" "0.99.1-pre" "GNU"
+.TH GAPPLETVIEWER 1 "2014-05-22" "0.99.1-pre" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc-4.8/libjava/classpath/doc/gjar.1 b/gcc-4.8/libjava/classpath/doc/gjar.1
index 1156c1c6a..105c76f88 100644
--- a/gcc-4.8/libjava/classpath/doc/gjar.1
+++ b/gcc-4.8/libjava/classpath/doc/gjar.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -45,14 +53,14 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.ie \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-. nr % 0
+. nr % 0
. rr F
.\}
.el \{\
@@ -124,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GJAR 1"
-.TH GJAR 1 "2013-05-31" "0.99.1-pre" "GNU"
+.TH GJAR 1 "2014-05-22" "0.99.1-pre" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc-4.8/libjava/classpath/doc/gjarsigner.1 b/gcc-4.8/libjava/classpath/doc/gjarsigner.1
index 02ee77cf1..c212e7830 100644
--- a/gcc-4.8/libjava/classpath/doc/gjarsigner.1
+++ b/gcc-4.8/libjava/classpath/doc/gjarsigner.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -45,14 +53,14 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.ie \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-. nr % 0
+. nr % 0
. rr F
.\}
.el \{\
@@ -124,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GJARSIGNER 1"
-.TH GJARSIGNER 1 "2013-05-31" "0.99.1-pre" "GNU"
+.TH GJARSIGNER 1 "2014-05-22" "0.99.1-pre" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc-4.8/libjava/classpath/doc/gjavah.1 b/gcc-4.8/libjava/classpath/doc/gjavah.1
index 4fac63f69..d55f388e3 100644
--- a/gcc-4.8/libjava/classpath/doc/gjavah.1
+++ b/gcc-4.8/libjava/classpath/doc/gjavah.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -45,14 +53,14 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.ie \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-. nr % 0
+. nr % 0
. rr F
.\}
.el \{\
@@ -124,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GJAVAH 1"
-.TH GJAVAH 1 "2013-05-31" "0.99.1-pre" "GNU"
+.TH GJAVAH 1 "2014-05-22" "0.99.1-pre" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc-4.8/libjava/classpath/doc/gjdoc.1 b/gcc-4.8/libjava/classpath/doc/gjdoc.1
index 45b8a047c..8177548e2 100644
--- a/gcc-4.8/libjava/classpath/doc/gjdoc.1
+++ b/gcc-4.8/libjava/classpath/doc/gjdoc.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -45,14 +53,14 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.ie \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-. nr % 0
+. nr % 0
. rr F
.\}
.el \{\
@@ -124,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GJDOC 1"
-.TH GJDOC 1 "2013-05-31" "0.99.1-pre" "GNU"
+.TH GJDOC 1 "2014-05-22" "0.99.1-pre" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -181,7 +189,7 @@ To learn more about running Doclets other than the Standard Doclet,
refer to the manual.
.SH "OPTIONS"
.IX Header "OPTIONS"
-.SS "Option Summary by Type"
+.Sh "Option Summary by Type"
.IX Subsection "Option Summary by Type"
Here is a summary of all the options of both Gjdoc and the Standard
Doclet, grouped by type. Explanations are in the following sections.
@@ -223,7 +231,7 @@ Doclet, grouped by type. Explanations are in the following sections.
.IP "\fIVirtual Machine Options\fR" 4
.IX Item "Virtual Machine Options"
\&\fB\-classpath \-bootclasspath \-J\fR \fIvmopt\fR
-.SS "Selecting which Source Files to Process"
+.Sh "Selecting which Source Files to Process"
.IX Subsection "Selecting which Source Files to Process"
.IP "\fB\-s\fR \fIpathlist\fR" 4
.IX Item "-s pathlist"
@@ -273,7 +281,7 @@ Process all classes in the given Java packages.
.IP "\fIsourcefiles\fR\fB...\fR" 4
.IX Item "sourcefiles..."
Process the classes in the given Java source files.
-.SS "Specifying the Format of Input Files"
+.Sh "Specifying the Format of Input Files"
.IX Subsection "Specifying the Format of Input Files"
.IP "\fB\-source\fR \fIrelease\fR" 4
.IX Item "-source release"
@@ -309,7 +317,7 @@ source code commented in a non-latin language for which the default
first sentence detector does not work. For all other cases, the
default (do not use BreakIterator) produces better results at the time
of this writing.
-.SS "Interlinking with other Documentation Sets"
+.Sh "Interlinking with other Documentation Sets"
.IX Subsection "Interlinking with other Documentation Sets"
.IP "\fB\-link\fR \fIurl\fR" 4
.IX Item "-link url"
@@ -372,7 +380,7 @@ you place your mouse pointer over it in the \s-1HTML\s0 documentation.
Omit package name qualifier from all class names.
.Sp
Specify this option to omit package name qualifiers altogether,
-.SS "Selecting which Information to Generate"
+.Sh "Selecting which Information to Generate"
.IX Subsection "Selecting which Information to Generate"
.IP "\fB\-public\fR" 4
.IX Item "-public"
@@ -529,7 +537,7 @@ directory names.
This option only makes sense if \fB\-docfilessubdirs\fR is also
specified. In this case, any sub-directory located directly beneath a
\&\fIdoc-files\fR directory is omitted if listed.
-.SS "Custom Documentation Tags"
+.Sh "Custom Documentation Tags"
.IX Subsection "Custom Documentation Tags"
.IP "\fB\-tagletpath\fR \fIpathlist\fR" 4
.IX Item "-tagletpath pathlist"
@@ -618,7 +626,7 @@ Then the \s-1HTML\s0 output will contain something like
\& $Id: cp\-tools.texinfo,v 1.9 2012\-03\-07 15:27:27 gnu_andrew Exp $
.Ve
.RE
-.SS "Running Other Doclets"
+.Sh "Running Other Doclets"
.IX Subsection "Running Other Doclets"
.IP "\fB\-docletpath\fR \fIpathlist\fR" 4
.IX Item "-docletpath pathlist"
@@ -657,7 +665,7 @@ feedback when successfully running third-party applets.
This option can be specified multiple times, in which case all doclets
are executed with the same information tree exposed via the Doclet \s-1API\s0
for each Doclet run.
-.SS "Adding Information to the Output"
+.Sh "Adding Information to the Output"
.IX Subsection "Adding Information to the Output"
.IP "\fB\-windowtitle\fR \fItext\fR" 4
.IX Item "-windowtitle text"
@@ -765,7 +773,7 @@ This option is currently ignored.
.Sp
When implemented, it will use the \s-1XHTML\s0 fragment in \fIfile\fR for the
help page contents instead of the default help text.
-.SS "Controlling the Output."
+.Sh "Controlling the Output."
.IX Subsection "Controlling the Output."
.IP "\fB\-d\fR \fIdirectory\fR" 4
.IX Item "-d directory"
@@ -846,7 +854,7 @@ available at a certain \s-1URL\s0, you should use this option to specify this
.Sp
This can help avoid certain redirect attacks used by spammers, and it
can be helpful for certain web clients.
-.SS "Verbosity Options"
+.Sh "Verbosity Options"
.IX Subsection "Verbosity Options"
.IP "\fB\-quiet\fR" 4
.IX Item "-quiet"
@@ -856,7 +864,7 @@ Suppress all output except for warnings and error messages.
Be very verbose about what \fBgjdoc\fR is doing.
.Sp
This option is currently ignored.
-.SS "Virtual Machine Options"
+.Sh "Virtual Machine Options"
.IX Subsection "Virtual Machine Options"
Sun's \fBjavadoc\fR tool seems to be based on \fBjavac\fR and
as such it seems to operate on the \s-1VM\s0 level. \fBgjdoc\fR, in
diff --git a/gcc-4.8/libjava/classpath/doc/gkeytool.1 b/gcc-4.8/libjava/classpath/doc/gkeytool.1
index ae582c471..88e97f663 100644
--- a/gcc-4.8/libjava/classpath/doc/gkeytool.1
+++ b/gcc-4.8/libjava/classpath/doc/gkeytool.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -45,14 +53,14 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.ie \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-. nr % 0
+. nr % 0
. rr F
.\}
.el \{\
@@ -124,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GKEYTOOL 1"
-.TH GKEYTOOL 1 "2013-05-31" "0.99.1-pre" "GNU"
+.TH GKEYTOOL 1 "2014-05-22" "0.99.1-pre" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc-4.8/libjava/classpath/doc/gnative2ascii.1 b/gcc-4.8/libjava/classpath/doc/gnative2ascii.1
index 770808e9d..26633db60 100644
--- a/gcc-4.8/libjava/classpath/doc/gnative2ascii.1
+++ b/gcc-4.8/libjava/classpath/doc/gnative2ascii.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -45,14 +53,14 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.ie \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-. nr % 0
+. nr % 0
. rr F
.\}
.el \{\
@@ -124,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GNATIVE2ASCII 1"
-.TH GNATIVE2ASCII 1 "2013-05-31" "0.99.1-pre" "GNU"
+.TH GNATIVE2ASCII 1 "2014-05-22" "0.99.1-pre" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc-4.8/libjava/classpath/doc/gorbd.1 b/gcc-4.8/libjava/classpath/doc/gorbd.1
index dc3d23b23..968e4acbc 100644
--- a/gcc-4.8/libjava/classpath/doc/gorbd.1
+++ b/gcc-4.8/libjava/classpath/doc/gorbd.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -45,14 +53,14 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.ie \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-. nr % 0
+. nr % 0
. rr F
.\}
.el \{\
@@ -124,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GORBD 1"
-.TH GORBD 1 "2013-05-31" "0.99.1-pre" "GNU"
+.TH GORBD 1 "2014-05-22" "0.99.1-pre" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc-4.8/libjava/classpath/doc/grmid.1 b/gcc-4.8/libjava/classpath/doc/grmid.1
index 04aaa285f..732bd6d77 100644
--- a/gcc-4.8/libjava/classpath/doc/grmid.1
+++ b/gcc-4.8/libjava/classpath/doc/grmid.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -45,14 +53,14 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.ie \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-. nr % 0
+. nr % 0
. rr F
.\}
.el \{\
@@ -124,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GRMID 1"
-.TH GRMID 1 "2013-05-31" "0.99.1-pre" "GNU"
+.TH GRMID 1 "2014-05-22" "0.99.1-pre" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc-4.8/libjava/classpath/doc/grmiregistry.1 b/gcc-4.8/libjava/classpath/doc/grmiregistry.1
index fa84a7156..abaa502c0 100644
--- a/gcc-4.8/libjava/classpath/doc/grmiregistry.1
+++ b/gcc-4.8/libjava/classpath/doc/grmiregistry.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -45,14 +53,14 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.ie \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-. nr % 0
+. nr % 0
. rr F
.\}
.el \{\
@@ -124,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GRMIREGISTRY 1"
-.TH GRMIREGISTRY 1 "2013-05-31" "0.99.1-pre" "GNU"
+.TH GRMIREGISTRY 1 "2014-05-22" "0.99.1-pre" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc-4.8/libjava/classpath/doc/gserialver.1 b/gcc-4.8/libjava/classpath/doc/gserialver.1
index e0674b212..db04fcf72 100644
--- a/gcc-4.8/libjava/classpath/doc/gserialver.1
+++ b/gcc-4.8/libjava/classpath/doc/gserialver.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -45,14 +53,14 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.ie \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-. nr % 0
+. nr % 0
. rr F
.\}
.el \{\
@@ -124,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GSERIALVER 1"
-.TH GSERIALVER 1 "2013-05-31" "0.99.1-pre" "GNU"
+.TH GSERIALVER 1 "2014-05-22" "0.99.1-pre" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
diff --git a/gcc-4.8/libjava/classpath/doc/gtnameserv.1 b/gcc-4.8/libjava/classpath/doc/gtnameserv.1
index 389ef12ff..e1742ae83 100644
--- a/gcc-4.8/libjava/classpath/doc/gtnameserv.1
+++ b/gcc-4.8/libjava/classpath/doc/gtnameserv.1
@@ -1,7 +1,15 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
.\"
.\" Standard preamble:
.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
@@ -45,14 +53,14 @@
.el .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.ie \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
-. nr % 0
+. nr % 0
. rr F
.\}
.el \{\
@@ -124,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "GTNAMESERV 1"
-.TH GTNAMESERV 1 "2013-05-31" "0.99.1-pre" "GNU"
+.TH GTNAMESERV 1 "2014-05-22" "0.99.1-pre" "GNU"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l