While I (strongly) agree with this advice -- there is a major downside. If you copy it into your application, and the platform changes (an update, a manufacturer customization, etc.), then your application's look-and-feel (including terminology) will vary from the platform standard. And, in the case up upgrades, older apps will vary from newer ones. The result is the user experience is less cohesive.
On Jan 22, 4:18 am, Mark Murphy <[email protected]> wrote: > On Sat, Jan 22, 2011 at 2:32 AM, Brill Pappin <[email protected]> wrote: > > However there are thousands of string in different language value > > > resources... which is why I say it it would save a heck of a lot of time. > > Write yourself a script that copies the string resource element from > the platform resources into your own project's copy of the resources. > Not only will writing that script take less time than will the > testing, but you are presuming that device manufacturers don't change > the strings, and I doubt that's a safe assumption. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > _The Busy Coder's Guide to *Advanced* Android Development_ Version 1.9 > Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
