The reason for the big difference is that strings in res/values are stored uncompressed in UTF16. They can then be memory mapped. (The Android dev team later said if would have been better if they went with UTF8 for size)
Perhaps you could leave one language (the most used) in res/values for safety, speed, and the generations of the IDs. And then create something that will load strings using the same IDs from xml for other languages. On Nov 28, 9:47 pm, Pent <[email protected]> wrote: > > XML files that aren't > > precompiled should compress quite efficiently. > > The difference is astonishing. Reading the XML from assets is easy. > > However, it's looking like I'll have to generate my own resource IDs > into e.g. RR.java, bit of a pain. > > Shame there's nothing built in to let you reference compressed > strings. > > 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
