Skip to content
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

Open
trantor opened this issue Jun 19, 2021 · 3 comments
Open

LDAP RFC-4514 representation of distinguished names #33

trantor opened this issue Jun 19, 2021 · 3 comments

Comments

@trantor
Copy link

trantor commented Jun 19, 2021

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

@rrthomas
Copy link
Owner

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.

@trantor
Copy link
Author

trantor commented Jun 26, 2021

Hello @rrthomas and thanks for the answer.
Unfortunately I am not a C developer but I might attempt to code something in the near future, so I might, circumstances allowing so, take you up on that offer.
There are also a few other encoding conversions I've tried recently which seem wrong but I have to look harder to see whether it's something wrong in the code or in my understanding/expectations.
Forgive my bluntness, but judging from the commit history it seems to me that since taking over from the original creator (that passed away in 2014) the development of the software on your side has been almost entirely on cleaning/fixing/modernizing the code base, the building process and the localizations (i.e. mostly caretaking) rather than implementing something new when it comes to new encodings and such.
May I assume that further enhancements in that area, i.e. growing/enhancing the software in its primary purpose, would need to come from interested third parties?
Have a nice day :)

@rrthomas
Copy link
Owner

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 TODO), as well as to consider whether another more modern framework might be a better place to do the work (for example, iconv).

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.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants