I cannot reproduce either. Normally we force encoding to UTF8 so there shouldn't be different behaviors.
Can you check which JVM your 2 machines use? On Mon, May 5, 2014 at 4:55 PM, Seth Goldenberg <[email protected]>wrote: > Strange issue here with merging resources. I have a build machine that's > botching the encoding of some unicode characters in my XML when merging > resources. This is building just fine on my own machine. > > This line is in an exploded AAR prior to being merged: > (From > build/exploded-aar/com.facebook/facebook-android-sdk/3.5.2/res/values/values.xml) > <string name="com_facebook_placepicker_subtitle_format">%1$s • %2$,d were > here</string> > > And like this after being merged: > (From build/res/all/release/values/values.xml) > <string name="com_facebook_placepicker_subtitle_format">%1$s ¥ %2$,d were > here</string> > > aapt (version 19.0.3) chokes with this error on the line above: > error: Error parsing XML: not well-formed (invalid token) > > This error does not happen on my personal machine. Both are running Mac OS > X 10.9.2. What dependency does aapt have that the same version of it would > produce different outputs on different machines? > > Thanks, > Seth > > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. http://developer.android.com | http://tools.android.com Please do not send me questions directly. Thanks! -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
