This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: What is the intended bahaviour of recoding characters outside the target range?
- From: "Troy" <tjk at tksoft dot com>
- To: ash at contact dot bg (Alexander Shopov)
- Cc: libc-alpha at sourceware dot org
- Date: Fri, 12 May 2006 02:35:50 +0300 (EEST)
- Subject: Re: What is the intended bahaviour of recoding characters outside the target range?
- Reply-to: <tjk at tksoft dot com>
ICU also provides the options in its library functions
(UCNV_FROM_U_CALLBACK_SKIP etc. arguments to ucnv_setFromUCallBack()).
Default behavior could be what it is now. Adding a
function to set a callback would give users the ability to
specify different behavior. This shouldn't break existing
programs.
I can't comment on the amount of work this might require,
since I don't have time to work on it myself.
Cheers,
Troy
>
> > I opine that it would make sense to model the solution after
> > uconv, which is ICU project's replacement for iconv. uconv
> > allows the user to specify what to do with such data with the
> > --to-callback option. E.g. escape-xml, escape-unicode, stop, skip,
> > etc..
>
> While this is acceptable for a command line tool, I don't think it will
> be appropriate for all cases - for example when the library is used by
> programs, for then the programmer would have to think about different
> options given to functions, while the functions would be almost
> certainly fixed by existing standards.
> Things could be controlled by environment variables but this is going to
> change current behavior somewhat and increase the environment.
> Still - this will be a largish project that I am not sure I will be able
> to complete and I am yet uncertain whether it is necessary.
>
>
> Kind regards:
> al_shopov
>
>