Talk:LDAP Data Interchange Format

LDIF content v. change records

The article should discuss the two subformats providing examples of both. Kdz 00:06, 11 June 2006 (UTC)[reply]

mis-handled non-alphanumeric characters

Would someone of some authority in the LDIF standards community please provide specific instructions or a chart on how to handle non-alphanumeric characters (eg, ampersand, single quote, etc.). For example, Yahoo! still insists on encoding all ampersands as extended HTML characters (ie, "&" --> "&") which, of course, fails to decode properly when an LDIF-compliant application tries to read the file. They've been contacted several times over the years but apparently are unable to understand the technical nature of the problem. I routinely import my Yahoo! address list into Thunderbird and if we could just get this one issue defined clearly enough for them to understand and act accordingly, it would save me literally hours of editing each time. The problem has been compounded now that they have discovered Base64 encoding finally but it means I have to edit twice; once before importing and then again after importing to catch the errant translations in the data that were Base64 encoded. Thank you ever so much. JimScott (talk) 16:35, 12 June 2009 (UTC)[reply]

LDIF limitations

The listed limitations seem to be a limitations of the tools processing the LDIF file and have nothing to do with the directory itself. For example, with Apache Directory Studio, the examples work fine with an OpenLDAP directory. This should be changed. Mudi2000 (talk) 10:14, 20 May 2011 (UTC)[reply]

Agreed. I'm deleting the section. Highlandsun (talk) 21:37, 23 September 2011 (UTC)[reply]