Open GoogleCodeExporter opened 9 years ago
This wouldn't make much sense w/o translating the user's guide and Javadocs,
too.
Original comment by crazybob...@gmail.com
on 10 Mar 2007 at 5:44
I can help translating user's guide (i have already started translating this
document) and error messages into Brazilian Portuguese.
Original comment by danie...@gmail.com
on 10 Mar 2007 at 10:39
this doesn't seem like a highly attainable goal. we could put error codes on
the
error messages so that a translated user's guide would be able to explain them
in
multiple languages, but beyond that I'm not sure if it's a good idea.
Original comment by kevin...@gmail.com
on 20 Apr 2007 at 4:29
Original comment by limpbizkit
on 5 Jun 2008 at 6:18
A lot of work for very little gain. In my experience, translating error
messages
leads to more trouble than good -- if code ever wants to programatically scan an
error message and take different steps depending on exactly what happened,
localizing
the error makes this impossible. Unless there's a very specific exception
subclass
for every single kind of error, the only way to do this is through error message
inspection.
Original comment by sberlin
on 2 May 2010 at 12:51
Original issue reported on code.google.com by
crazybob...@gmail.com
on 10 Mar 2007 at 5:43