2012-08-09, 22:35
I think the problem might be in the .nfo file, but it's hard to be sure.
To check weather a .nfo file is valid, I run the file through a little test that tries to see if the first 5 characters of the file are "<?xml" which would make the .nfo file a valid XML file.
However, when scanning in your .nfo file, it seems to come up with some sort of invisible character right in front of the "<?xml" bit, rendering the test invalid, and stops without reading the rest of the information.
For now I've uploaded a build that is a little more relaxed, and scans the first 10 characters for "<?xml", so it should read your .nfo files:
ViMediaManager
To check weather a .nfo file is valid, I run the file through a little test that tries to see if the first 5 characters of the file are "<?xml" which would make the .nfo file a valid XML file.
However, when scanning in your .nfo file, it seems to come up with some sort of invisible character right in front of the "<?xml" bit, rendering the test invalid, and stops without reading the rest of the information.
For now I've uploaded a build that is a little more relaxed, and scans the first 10 characters for "<?xml", so it should read your .nfo files:
ViMediaManager