Tuomo was half right, the files are converted to UTF-8 however the problem does not seem to be that UTF-8 is not used during installation. The problem apears to be that there is errors in the re-encoding.
1. The uri to the new encoded file is set to a variable thats never read, and therefor never added to the JAR
2. The code that sets resource files to empty (some kind of saftey feature I guess) is accutally called after the re-encoding is done, therefor even if the above code was set to the right variable it would be overwritten with the address to the blank file, hence why if you use the encoding attribute your text will be empty.
I have attaced a fix for both 5.0.0beta5 and 4.3.4RC1, sorry no GIT patch as I still can't work out how to create one with Eclipse (EGit)
Update: My mistake Tuomo was correct after all, the bug I have fixed is to do with blank text when no parse attribute is set. The two errors I described above will happen with the following entry: <res id="InfoPanel.info" src="resources/readme.txt" encoding="ISO-8859-1"/>
I will attach a new fix that also works with the parse attribute set as my first fix didn't. Whoops.
As for the acctual bug this post is about, I can't seem to repoduce the error on my machine but I would assume it would just involve using:
When calling loadInfo() in the info panel, etc for the other panels.