You can catch and format whatever exception you are concerned about. Use android.content.res.Resource.getString to format messages: http://developer.android.com/reference/android/content/res/Resources.html#getString(int, java.lang.Object...)
On Nov 12, 10:21 am, Rutton <rut...@web.de> wrote: > Thanks for your kind explanation. > The describing text is easy to realize, but what I wanted to really > know is, how to deal with (custom formatted) exception messages. So, > is it good practice to use the Exception e.getLocalizedMessage() and > use the Java-mechanism to deal with that, perhaps in conjunction with > the Android-string localization features. > > What I have is exception throwing code (that creates custom > formatted / not just text values that can be retrieved from the res/* > files). And I ask myself, what to do here the best. At somepoint an > exception *may* bubble up to a error message to the user, and how to > localize these the best way. > > Cheers, > R. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
