You can always use IDs to identify your keys, if you wish. Write a few small utility functions to do the conversion and the editing process to switch over will be fairly simple. (Plus you can leave frequently used items as they are.)
On Nov 28, 3:55 pm, Pent <[email protected]> wrote: > > You don't have to generate your own resource IDs. Just don't use IDs. > > > Nothing REQUIRES you to use IDs. > > No, but it's space (and access) efficient while being readable in the > source code. > > I need a key for each resource string. If the key is a (human- > meaningful) String then in a large proportion of cases the key takes > up more space than the content (think things like button labels etc). > > On the other hand, it's true, if you have 10 translations then the > size of the key quickly becomes relatively unimportant. > > Pent -- 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
