xiosensei 30 Posted April 4, 2019 Posted April 4, 2019 I have noticed that if I created an nfo file myself, using '&' anywhere in the nfo file makes a crash when importing the nfo. My current workaround is to use: & instead of &. However, I have noticed that converting my nfo file to html entities is not the way to go because sometimes I see the raw html in some of the interfaces. Asking for more consistency in the user interface! Also I think it is better to get rid of reading nfo files as they are htmls and read them as raw text.
Luke 42080 Posted April 4, 2019 Posted April 4, 2019 Hi, currently we expect them to be valid xml. If you plug that file into an xml validator, does it validate?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now