An interesting question. So I have had a look..I am sorry, but I don't know the internal structures from MP and why this NFO format does not work for you. This format has been developed a long time ago with some help of other users which use MP.
Is there no "official" NFO description in the MP wiki which declares what fields are supported and how they should be structured?
I am wondering because no one else have complained about that in the past years... (and the format has not been changed since then)
The Wiki for MP1 states that the details in the .nfo for genre should be as follows.
In that layout/format, both Mp1's Videos importer and the plugin Moving Pictures (what I use) imports the genre data perfectly.<genre>Animation</genre>
The issue is only there when using .nfo files generated using TMM. Where the formatting is :
Whilst experimenting with this, I believe I have found the issue. I am using the settings in TMM for use with Media Portal. These are what do not work.<genres>
If I use the settings for Kodi or XBMC/Kodi<16 then it writes the .nfo correctly. Without the <genres></genres> tags in the way. Which are confusing the scrapers.
Two other issues I have found with the formatting also are as follows.
When set to Media portal NFO format, it only generates <certification>rating</certification>
When on the Kodi option, it writes both <cetification> and <mpaa> into the nfo. Mediaportal requires the <mpaa> to scrape the certification rating.
lastly, Media portal requires the languages field to be <language></language> , Not <languages></languages> as is currently being written.
currently, all version of settings (MP, Kodi, XBMC) in TMM write that as <languages>. It needs to be <language>
Here is the link to the wiki page. 1.6.x - NFO file usergroup (movie set) additional support