I've found if you tag substitutions in string resource with xliff:g, aapt won't throw above error. First, I thought aapt automatically position substitutions using xliff:g ids, e.g.:
res/values/strings.xml: <string name="foo"><xliff:g id="bar">%d</xliff:g> <xliff:g id="baz">%d</xliff:g></string> res/values-en/strings.xml: <string name="foo"><xliff:g id="baz">%d</xliff:g> <xliff:g id="bar">%d</xliff:g></string> become: res/values/strings.xml: <string name="foo">%1$d %2$d</string> res/values-en/strings.xml: <string name="foo">%2$d %1$d</string> , but this isn't true. So why aapt ignores multiple non-positional substitutions in such case? Is it a bug? -- 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
