More than once, I’ve gotten the following weird problem when looking at an XML layout for Android in Eclipse:<\/p>\n
Failed to parse file C:\\Eclipse_workspace\\ButtonTest2\\res\\drawable\\arrow_1.xml
\nException details are logged in Window > Show View > Error Log<\/p><\/blockquote>\nThe error itself isn’t exactly informative, and certainly doesn’t make sense:<\/p>\n
org.xmlpull.v1.XmlPullParserException: PI must not start with xml (position:unknown @1:5 in java.io.InputStreamReader@1c167686)
\nat org.kxml2.io.KXmlParser.exception(Unknown Source)
\n…….<\/p><\/blockquote>\nHmm. XML files should start with an appropriate declaration line, yet this says my XML file shouldn’t have it. That’s… weird.<\/a> Normally I just remove the line til it stops complaining but as I’m playing with the second pre-release of r17 android SDK (some key components have been broken lately) and feeling bold I decided to understand this once and for all. What follows is the text of my answer on StackOverflow<\/a> earlier tonight:<\/p>\n
\nI’ve beaten my head against this wall a few times and now I have the answer (I *hate* mysterious behavior, especially when it seems to be random).<\/p>\n
I just ran a 4-way test (Unix and DOS, with and without the binary “EF BB BF” BOM header\/signature). I found that Eclipse does not put a binary BOM header into XML files it creates, period.<\/strong> If you add a file that has the `”<?xml … ?>”` declaration header, it works correctly ONLY if that binary signature is ABSENT. (Whether EOLs are Unix or DOS doesn’t matter). If you have *both* forms of header you get this problem. You can have one, the other, or neither, but never both.<\/p>\n
So, if you create a new XML file in Eclipse you can expect (in 3.6 – 3.7.1 anyway) that it has no binary BOM header and you should properly put a `”<?xml … ?>”` declaration header in there to identify it as Unicode. If you IMPORT a project that has files with binary BOM header signatures or use an external editor that likes to add them, that’s where all this fun begins.<\/p>\n
Ideally, ensure XML files with declaration don’t have binary BOM header before importing them… otherwise, remove that `”<?xml … ?>”` declaration header whenever Eclipse complains… short of removing the binary header that’s all you can readily do.<\/strong> (It’d be nice if Eclipse handled this more consistently… or at least gave you a way to identify and fix the problem readily by removing the binary BOM header…)<\/p>\n
*\u00a0If in doubt, examine the file with an external hex editor, preferably one that is NOT Unicode-aware (WinHex<\/a> worked for me, YMMV). Some text\/hex editors will auto-detect Unicode and may auto-add a header when the file didn’t really have one.<\/em><\/p>\n
\nPostscript: I use IDM’s UltraEdit \/ UltraCompare<\/a> primarily. They work great but they’re a little too<\/em> good at determining if a file is Unicode or not, to the point where these four text files ALL had the binary BOM header in hex mode!! WinHex<\/a> showed the exact situation, and indeed only two of the files actually had that header. However, I’d like my regular editor to work correctly. Time to write IDM an email…<\/p>\n\n","protected":false},"excerpt":{"rendered":"
More than once, I’ve gotten the following weird problem when looking at an XML layout for Android in Eclipse: Failed to parse file C:\\Eclipse_workspace\\ButtonTest2\\res\\drawable\\arrow_1.xml Exception details are logged in Window […]<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"Layout":"","footnotes":"","_links_to":"","_links_to_target":""},"categories":[1],"tags":[],"class_list":["entry","author-marty","post-55","post","type-post","status-publish","format-standard","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/posts\/55","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/comments?post=55"}],"version-history":[{"count":0,"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/posts\/55\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/media?parent=55"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/categories?post=55"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.falatic.com\/index.php\/wp-json\/wp\/v2\/tags?post=55"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}