[turba] Turba, LDAP, "$", and mapquest

[Adam Tauno Williams]

>>It is important to note (as you basically say above) that the $ == newline
>>rule only applies to attributes with the syntax OID of
>>1.3.6.1.4.1.1466.115.121.1.41 (postalAddress, see rfc 2252 page 8).  Any
>>$ <=> newline conversion should only be done on attributes with this
>>syntax.
>>This probably requires some kind of attribute identifier in the Turba
>>config so that you can specify which attributes should get the
>>conversion.
>Right. Any patches that do this correctly will likely be applied.

What would be the "correct" way to do about this?

Add an a new attribute type, "postalmutliline" instead of just "multiline"?
Add an a new attribute to the source definition, perhaps in the "params" array,
containing a list of attribute names to translate?

I've never developed anything for horde before, although I've done lots of PHP.
 I'm not certain what information is available from within the scope of
::GetObject(...) in a source driver.  I don't see anywhere that the LDAP driver
actually does a subschema query for an objects syntax OID, and that would
probably make the driver very subject to various DSA compatibility issues.