On 30/05/2013 10:44, "Xiaofan Chen" <xiaof...@gmail.com> 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.
I would be happy with that approach.
>
>IMHO, I am not that fond of a multi-lingual version of libusb_strerror()
>at all.
Me too.
>A wiki page providing the translations for the English only error
>messages will be good enough for simple library like libusb.
Good enough.
>
>> This patch includes a Dutch translation for the messages to show how
>>further
>> languages can be added in a simple manner.
>
>I do not quite like the idea of adding lots of translations in the source
>code. Can it be a separate file if this is really wanted by the community?
As per above I don't need or want anything but English, but if there
are other languages what's wrong with having them in the source code?
Are you suggesting that a file that is separate (at run time) from the
application code should be used so that the translations could be
changed without relinking the app or library or what you have in mind,
please clarify..
br Kusti
This e-mail may contain confidential or privileged information. If you are not
the intended recipient (or have received this e-mail in error) please notify
the sender immediately and destroy this e-mail. Any unauthorized copying,
disclosure or distribution of the material in this e-mail is strictly
forbidden. We will not be liable for direct, indirect, special or consequential
damages arising from alteration of the contents of this message by a third
party or as a result of any virus being passed on or as of transmission of this
e-mail in general.
------------------------------------------------------------------------------
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
