RE: importing multi line fields

["Salter, Thomas A" <Thomas.Salter@unisys.com>]

And a side note: This all works nicely with T.61 strings because the ASCII $
(0x24) is not a legal T.61 character; in T.61 $ has the value 0xA4.  Thus
0x24 could be used as a separator without precluding the use of dollar signs
(0xA4) in the strings.  This 'niceness' has been lost in Ldap V3, now that
strings are all UTF8.

> -----Original Message-----
> From: Chris Ridd [mailto:C.Ridd@isode.com]
> Sent: Friday, January 08, 1999 10:52 AM
> To: Douglas E. Wegscheid
> Cc: openldap-general@OpenLDAP.org; alan_k@HK.Super.NET
> Subject: Re: importing multi line fields 
> 
> 
> On Fri, 08 Jan 1999 10:41:24 EST, "Douglas E. Wegscheid" wrote:
> > At 08:46 AM 1/8/99 +0000, Chris Ridd wrote:
> > >The $ separator used in the Postal Address LDAP string format has 
> > >nothing to do with carriage returns or line feeds. Postal 
> Address is 
> > >not a "multiline field", it is a value which contains up 
> to 6 strings, 
> > >which is an important distinction to make.
> > >
> > >If you put $ signs in a value of Directory String syntax 
> (for example) 
> > >they will remain just that, $ signs. (This is a good thing!)
> > >
> > >If you wanted a particular string component of a postal address to 
> > >contain a CRLF, you would have to encode it over the wire 
> as follows:
> > >
> > >1st line of 1st string\0d\0a2nd line of 1st string$2nd 
> string$3rd string
> > >
> > >This is described in RFC 1778 and RFC 2252, which you should read.
> > 
> > historically, $ is used as a separator in postaladdress 
> (and actually
> > stored in the directory). The clients had to know to do the 
> encoding and
> 
> The way they are stored varies between servers, of course.
> 
> > decoding. I also recall seeing some proposed schema with 
> examples that used
> > this schema, the Howes & Smith LDAP book uses it, and RFC 
> 1778 section 2.23
> > has the BNF for "Values of type PostalAddress" as:
> > 
> > <postal-address> ::= <t61string> | <t61string> '$' <postal-address>
> > 
> > Am I misinterpreting or misusing the RFC information?
> 
> I don't know how you are using it :-) but your interpretation is 
> correct: $ is a *separator* in attributes of syntax Postal 
> Address and 
> doesn't indicate any magic CR or LF...
> 
> Chris
>