Mark Banner wrote:
Can someone confirm for me that strings containing characters such as umlaut should be base-64 encoded? That is how I read RFC 2849 (http://www.ietf.org/rfc/rfc2849.txt?number=2849), just want to make sure before I mark more bugs invalid.
Yes, according to the LDIF RFC UTF-8 characters outside of ASCII are to be base64-encoded. Such files should be easily imported into any LDIF-aware program.
Note that some LDAP-based software goes beyond the RFC and provides a way to produce "minimally encoded" LDIF where such characters are not base64-encoded (e.g., the Mozilla ldapsearch tool's -e option). If you want to use a UTF-8 aware editor to view or modify an LDIF file, it is nice to have such an option. But I think that the reason the LDIF RFC specifies base64-encoding is for maximum interoperability (e.g., the ability to pass LDIF files through ASCII-only email gateways, etc.)
-- Mark Smith Pearl Crescent, LLC http://pearlcrescent.com/ LDAP Book Information http://ldapbook.com/ _______________________________________________ dev-tech-ldap mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-ldap
