David Reid wrote:
If the answer to the question "does what we have now work" is "yes" then
apr-util 1.0 is good to go.
+1
The apr-iconv API is unfortunate, and the fact that it doesn't support transliteration like GNU libiconv is worse, but most uses of apr-iconv will be through the apr-util xlate wrapper, so it's not so important to clean up the API.
Also, if we're going to change the API, we might as well move base it on the iconv-2.0 version (we're currently using the 1.0 as a baseline).
-- Brane
