Speaking of which, where is the (if there is any) roadmap document or
something similar for the next version of the API?
*--*
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major in Computer Science
| tylerromeo(a)gmail.com
On Fri, Jan 25, 2013 at 10:08 AM, Brad Jorsch <bjorsch(a)wikimedia.org> wrote:
On Fri, Jan 25, 2013 at 9:48 AM, Tyler Romeo
<tylerromeo(a)gmail.com> wrote:
* Should error messages returned by the API be translated? Or should the
translation be left to JavaScript in the client?
I think it should be left to JavaScript in the client. The API is not a
UI,
so it is not intended to function as an
internationalized interface.
However, a JavaScript script that uses the API *is* part of a UI, and
thus
has the burden of internationalizing whatever it
does. Additionally, I
don't know much about our API clients, but adding in non-ASCII characters
may or may not cause issues.
Any client that has issues with non-ASCII characters is probably
already broken, since our pages have non-ASCII all over the place and
non-ASCII can make its way into error messages by being included in
page titles and such.
As for i18n, it would be nice to support API users that don't speak
English well.
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l