Subject: LDAP Addressbook with multiple cn's

From: Steffen Kaiser <[email-masked]>
Date: Tue, 15 Oct 2002 10:50:07 +0200 (CET)

Hello,

below is a quote of the 'ldapsearch' man page of OpenLDAP v2:

       The following command:

           ldapsearch -LLL "(sn=smith)" cn sn telephoneNumber

       will perform a subtree search (using the default search base
defined in ldap.conf(5)) for entries  with  a
       surname  (sn)  of  smith.  The common name (cn), surname (sn) and
telephoneNumber values will be retrieved
       and printed to standard output.  The output might look something
like this if two entries are found:

           dn: uid=jts, dc=example, dc=com
            cn: John Smith
            cn: John T. Smith
            sn: Smith
            sn;lang-en: Smith
            sn;lang-de: Schmidt
            telephoneNumber: 1 555 123-4567

            dn: uid=sss, dc=example, dc=com
            cn: Steve Smith
            cn: Steve S. Smith
            sn: Smith
            sn;lang-en: Smith
            sn;lang-de: Schmidt
            telephoneNumber: 1 555 765-4321

So my problem with multiple cn attributes is not home grew: How can I have
pine display one specific cn, in this example it would be "Steve S.
Smith". Is there a standard/RFC somewhere specifying this particular
problem?

To tweak the order of the attributes is not the solution, because
different clients (Netscape Communicate, Mozilla) seem to display either
the first or the last (maybe even a random one).

I have, in particular, a problem with:
1) names that include non-ASCII characters, such as umlauts, accented
letters etc., &
2) persons, who marry.

Both need to have two or more cn/sn/gn attributes to allow _searching_ for
them, e.g.:

1) plain-ASCII variant and native charset ISO-5589-15, &
2) the pre- and post-wedding name.

But when two cn's are present, all the LDAP clients use another
"display name" of the entry found, though, it should be:
1) the native one, &
2) the post-wedding name.

Bye,

-- 

Steffen Kaiser

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------