Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <429B5701.5010508@apache.org>
Date: Mon, 30 May 2005 20:10:09 +0200
From: Mladen Turk <mturk@apache.org>
User-Agent: Mozilla
MIME-Version: 1.0
To: Jeff Trawick <trawick@gmail.com>
CC: dev@apr.apache.org
Subject: Re: Move apr_xlate from apr-util to apr-iconv?
References: <429AE893.6040207@apache.org>
	 <cc67648e05053003595300549a@mail.gmail.com>	 <429AF750.7000806@apache.org>
 <cc67648e050530055710e51886@mail.gmail.com>
In-Reply-To: <cc67648e050530055710e51886@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jeff Trawick wrote:
>>>>Can we move the entire apr_xlate API from apr-utils to
>>>>the apr-iconv?
>>>
>>>no; apr_xlate works just fine without apr-iconv (when system provides
>>>a suitable iconv)
>>>
>>
>>It does not.
> 
> 
> you misread my statement, but that isn't really the point...  (I was
> trying to convince you that the current arrangement makes a lot of
> sense on some platforms...)
>

I just browse the source code for the httpd and in 99% there is a
single need for apr_xlate API, and that is to convert from
ISO-8859-1 to EBCDIC if someone is using IBM at the first place.

So IMHO we can write a simple converter for that, and get rid
entirely of iconv dependency from apr-util.
Someting like apr_ascii_to_ebcdic should do thought.

If someone wish to use the translation mechanism, well, the
there is apr-icov project that should in that case provide
the full apr_xlate api.
Only mod_charset_lite uses the full capability of iconv stuff,
so what's the point to link the apr-util with the
iconv/apr-iconv anyhow?


Regards,
Mladen.