On 2013.05.30 17:24, Orin Eman wrote: > So I'm in the English ASCII only and have done with it camp.
Well, I'm firmly in the let's get done with it camp. And like Orin I'm not entirely sure about the whole point of localizing our error strings or just how much usage this localization will actually get. However, as long as we can get something simple, very low-maintenance and that passes as usable (doesn't mean it has to meet established standards), we might as well give a little extra bit of freedom/choice to our users. So, if there is an agreement that Hans' new proposal meets the conditions above (I think it does, but feel free to comment) and that, should we decide to integrate it, it will be final enough not to warrant us spending any more time on this (besides adding localized strings if our users are kind enough to provide translation -- which should also give us an idea on whether our message localization is really used) as well as not penalize developers who just want English messages, then I'd say let's go for it. Regards, /Pete ------------------------------------------------------------------------------ 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
