-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LDAP RFC-4514 representation of distinguished names #33
Comments
Yes, I think this would be within the scope of Recode. If you would like to implement it, I would be happy to discuss the design. |
Hello @rrthomas and thanks for the answer. |
Hopefully the code to be written would be more-or-less trivial, and the conversion would be mostly data-driven. You're quite right, my involvement with recode has been purely maintenance, to clean up and release François Pinard's unreleased development work, to integrate bug fixes, and to fix portability and other problems. Anyone wanting to further develop recode would do well to read Pinard's own notes (the file Pinard himself planned to rewrite recode in Python; I would not now make that choice, but if I were planning recode's further development, I would certainly want to rewrite it in a more tractable language than C. Also, I would want to remove duplication by using iconv or other libraries for as many of the standard recodings as possible. (This would require careful auditing of the differences between recode and other systems.) |
Hello @rrthomas .
I was interested in recode support for the peculiar encoding/escaping of the RFC in question.
Would it be within the scope of the software?
Thanks a lot
The text was updated successfully, but these errors were encountered: