Add CVS revision line

[openldap] / doc / man / man3 / ldap_get_dn.3

diff --git a/doc/man/man3/ldap_get_dn.3 b/doc/man/man3/ldap_get_dn.3
index 4471612259399f20d4be9d068ad6ffcd695f4fa7..cecf5d5652d7701206fe797d7f404fac90bdafe2 100644 (file)
--- a/doc/man/man3/ldap_get_dn.3
+++ b/doc/man/man3/ldap_get_dn.3
@@ -1,11 +1,11 @@
 .TH LDAP_GET_DN 3 "RELEASEDATE" "OpenLDAP LDVERSION"
 .\" $OpenLDAP$
-.\" Copyright 1998-2002 The OpenLDAP Foundation All Rights Reserved.
+.\" Copyright 1998-2008 The OpenLDAP Foundation All Rights Reserved.
 .\" Copying restrictions apply.  See COPYRIGHT/LICENSE.
 .SH NAME
 ldap_get_dn, ldap_explode_dn, ldap_explode_rdn, ldap_dn2ufn \- LDAP DN handling routines
 .SH LIBRARY
-OpenlDAP LDAP (libldap, -lldap)
+OpenLDAP LDAP (libldap, -lldap)
 .SH SYNOPSIS
 .nf
 .ft B
@@ -41,8 +41,8 @@ char *ldap_dn2ad_canonical( const char * dn )
 These routines allow LDAP entry names (Distinguished Names, or DNs)
 to be obtained, parsed, converted to a user-friendly form, and tested.
 A DN has the form described in
-RFC 2253 "Lightweight Directory Access Protocol (v3):
-UTF-8 String Representation of Distinguished Names".
+RFC 4414 "Lightweight Directory Access Protocol (LDAP):
+String Representation of Distinguished Names".
 .LP
 The
 .B ldap_get_dn()
@@ -91,7 +91,7 @@ can be either
 or
 .B LDAP_AVA_BINARY,
 the latter meaning that the value is BER/DER encoded and thus must
-be represented as, quoting from RFC 2253, " ... an
+be represented as, quoting from RFC 4514, " ... an
 octothorpe character ('#' ASCII 35) followed by the hexadecimal
 representation of each of the bytes of the BER encoding of the X.500
 AttributeValue."
@@ -107,7 +107,7 @@ can be
        LDAP_DN_FORMAT_DCE
 
 .fi
-which defines what DN syntax is expected (according to RFC 2253, 
+which defines what DN syntax is expected (according to RFC 4514, 
 RFC 1779 and DCE, respectively).
 The format can be \fIOR\fPed to the flags
 .LP
@@ -184,7 +184,7 @@ is used to turn a DN as returned by
 .BR ldap_get_dn (3)
 into a more user-friendly form, stripping off all type names.  See
 "Using the Directory to Achieve User Friendly Naming" (RFC 1781)
-for more details on the UFN format.  Due to the ambigious nature
+for more details on the UFN format.  Due to the ambiguous nature
 of the format, it is generally only used for display purposes.
 The space for the UFN returned is obtained dynamically and the user
 is responsible for freeing it via a call to
@@ -234,7 +234,4 @@ These routines dynamically allocate memory that the caller must free.
 .BR ldap_memfree (3),
 .BR ldap_value_free (3)
 .SH ACKNOWLEDGEMENTS
-.B     OpenLDAP
-is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).
-.B     OpenLDAP
-is derived from University of Michigan LDAP 3.3 Release.  
+.so ../Project