FW: commit: ldap/libraries/libldap t61.c

["Howard Chu" <hyc@highlandsun.com>]

Perhaps this was an exercise in futility, but I've added functions to convert
between T.61 and UTF-8. Considering that the ITU-T has withdrawn the T.61 spec
it seems pointless to spend a lot of time on this, but it also seems like it is
still necessary as long as LDAPv2 interoperability is needed.

Also I can't reconcile the fact that RFC1777 only mentions the IA5 character
set, which is in fact a superset of the 7-bit T.61 space. I.e., 7-bit T.61 (as
described in RFC 1345) has no backslash, caret, backquote, left curly bracket,
right curly bracket, or tilde. Yet the LDAP RFCs are littered with backslashes
and curly brackets, regardless. It's quite ironic to read this example in RFC
1617 (page 25)
    localityName=Zuerich
    localityName=Zurich
    localityName={T.61}Z\c8urich
given that "{T.61}" is not legal in the T.61 character set...

Can anyone shed some more light on this? The discrepancy between 7-bit T.61 and
8-bit T.61 is somewhat disturbing too: 7-bit has '#' as x23, the usual value,
but 8-bit leaves that code undefined and moves '#' to xA6. Similarly they fudge
the usual '$' in x24, and locate it at xA4. Do existing LDAPv2 implementations
follow the T.61 spec exactly, or do they just use plain US-ASCII for x00-x7F?

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

-----Original Message-----
Update of /repo/OpenLDAP/pkg/ldap/libraries/libldap

Modified Files:
	t61.c  1.1 -> 1.2

Log Message:
Added conversion from UTF-8 to T.61.


CVS Web URLs:
  http://www.openldap.org/devel/cvsweb.cgi/libraries/libldap/
    http://www.openldap.org/devel/cvsweb.cgi/libraries/libldap/t61.c

Changes are generally available on cvs.openldap.org (and CVSweb)
within 30 minutes of being committed.