On Thu, May 30, 2013 at 2:30 AM, Hans de Goede <hdego...@redhat.com> wrote:
> Hi,
>
> On 05/30/2013 09:44 AM, Xiaofan Chen wrote:
> > On Tue, May 28, 2013 at 6:25 PM, Hans de Goede <hdego...@redhat.com>
> wrote:
> >> This patch adds the much requested libusb_strerror() function, taking
> into
> >> account all issues people raised wrt previous attempts.
> >>
> >> Criteria / Decisions underlying this implementation:
> >> -Must support translated messages
> >> -Must not use gettext as that does not work well in combination with
> Windows
> >> (when building with Visual C, or for Windows CE)
> >> -API compatible with FreeBSD and various patched libusb-s floating
> around
> >> -KISS:
> >> -Do not add any (other) library dependencies
> >> -Do not try to deal with message encodings (iconv), simply always
> return UTF-8
> >> making encoding the problem of the application using libusb_strerror.
> >> Apps which don't want to deal with encoding can opt-out with a
> simple:
> >> libusb_set_strerror_locale("en") call, after which the messages
> returned by
> >> libusb_strerror are guaranteed to be pure ASCII.
> >
> > I think the other way around will probably be better. By default,
> > libusb_strerror()
> > should be pure ASCII without doing any other thing. This will make it
> > compatible with the existing patched version of libusb.
>
> See my new proposal in this thread, that does exactly that.
>
> >
> > IMHO, I am not that fond of a multi-lingual version of libusb_strerror()
> > at all. A wiki page providing the translations for the English only error
> > messages will be good enough for simple library like libusb.
>
> A disagree if you've a fully translated / localized application you want
> user visible error messages to be translated too. But with my new proposal
> app authors can choose, and will get only English by default.
>
But I'd never display the raw messages to the user anyway. I'd put them
in a log file and that I want in English so that I can have a user send the
log file to me and be able to understand it.
Messages to the end user go through another level of sanitation, not to
mention that our UI designers will want to change the messages anyway.
People complain about Windows and one of the things it does at times is
present unsanitized Win32 error strings. It looks _really bad_ and means
nothing to the user.
So I'm in the English ASCII only and have done with it camp.
Orin.
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
