Simon Josefsson wrote on 2006-12-28:
> > iconvme::iconv_string -> str_iconv
> > iconvme::iconv_alloc -> str_cd_iconv (with reversed arguments)
>
> I looked into this now, for libidn, and it seems the move to striconv
> will add some additional dependencies: striconv depends on
> c-strcasecmp w
Bruno Haible <[EMAIL PROTECTED]> writes:
> Let us know when we can remove the iconvme module. Remember the migration
> path:
> iconvme::iconv_string -> str_iconv
> iconvme::iconv_alloc -> str_cd_iconv (with reversed arguments)
I looked into this now, for libidn, and it seems the move to stric
Simon Josefsson wrote on 2006-09-06:
> > What do you think about them?
> > Acceptable?
>
> It looks good to me.
I applied these changes.
Let us know when we can remove the iconvme module. Remember the migration
path:
iconvme::iconv_string -> str_iconv
iconvme::iconv_alloc -> str_cd_iconv (wi
Bruno Haible <[EMAIL PROTECTED]> writes:
> Hi Simon,
>
>> The interface sounds good to me, let's see the code. ;)
>
> I'm making some changes to iconvme::iconv_string on the way of the merge.
> I've put them on the 'haible-private' branch of lib/iconvme.c. All based
> on code in use in GNU gettext
Hi Simon,
> The interface sounds good to me, let's see the code. ;)
I'm making some changes to iconvme::iconv_string on the way of the merge.
I've put them on the 'haible-private' branch of lib/iconvme.c. All based
on code in use in GNU gettext for years. What do you think about them?
Acceptable?
Bruno Haible <[EMAIL PROTECTED]> writes:
> Hi Simon,
>
> I'm trying to unify your 'iconvme' module and my 'iconvstring' module (from
> GNU gettext).
...
> How does that sound? Is it acceptable?
Hi! The interface sounds good to me, let's see the code. ;)
The only concern I can think of would be
Oskar Liljeblad wrote:
> it would however be very useful if these functions would
> null-terminate the generated strings properly as well. I assume str_iconv
> and str_cd_iconv would add a single null-byte
Yes. the str_* functions expect a C string as input and produce one as
output, i.e. the from
On Monday, September 04, 2006 at 14:53, Bruno Haible wrote:
Hi Bruno
[..]
> All of these options are useful in some way or the other. Therefore I'd like
> to keep all the options, and distinguish them through a consistent
> nomenclature.
> - "str" vs. "mem",
> - infix "cd" vs. none (similar
Hi Simon,
I'm trying to unify your 'iconvme' module and my 'iconvstring' module (from
GNU gettext).
extern char *iconv_string (const char *string, const char *from_code,
const char *to_code);
extern char *iconv_alloc (iconv_t cd, const char *string);
vs.
exter
