[chrissix666]

Can someone advise what these peculiarities are in the MPAA tag, and Studio tags, and there may be a way I can correct what is occurring when this is saved to the nfo.
Link to discussion or examples would be appreciated.

MC has options to remove/add some info to the MPAA tag, and at this time these are only for mpaa certificate for Movies, but could be transposed to TV series as well.
[url=javascript:void(0)][/url]

As already described in the above post I have to add one more thing in this regard:
The .nfo data for MPAA and studios work flawlessly with all skins as long as it's all about "text output".

The request or the problem of "MANswers" is more about a skin internal function, where internal scrapers get along with it better (probably coded on it) and you would have to fix .nfo data manually at LocalInformationOnly if you want that all working fine.

Specifically, it is about the representation of studios and MPAA as logos.
It simply accesses the studio and MPAA label, and the entry fits 1: 1 with a stored in the Textures.xbt logos, a logo can be displayed.

For example, I use the following MC settings for MPAA in the movies, so that the skin can handle it as well:
https://ibb.co/mHL5v9
So I get the MPAA in the format "G, PG, PG-13, R", not rated i have to rename to "NR" for my skin as example...
In the meantime, of course, I have the knowledge with which spelling the skin cope and which not ...
For example, the German ratings, the FSK, the data from the API always come with "FSK-6, FSK-12" and so on, but for my skin, I have to change it to "FSK 6, FSK 12" so that he can handle.

In summary, I have to say, this is not due to MC, or the data of the API, but clearly always how the skin is programmed.

No matter if scraper or .nfo, there can only be a logo if there is a graphic in Textures.xbt.
If you use MPAA with the scraper, you will get better results from the beginning, because the skin is tuned to it, with the .nfo's you have to adjust the MPAA correctly so that the entries fit.

What I have not found out yet is a small discrepancy in the studios.
The handling is very different when using .nfo or a scraper. I have not yet figured out if it is the skin implementation, or if there is a difference in reading the studios via Scraper or LocalInformationOnly.

In both cases, a studio logo must be displayed so that the name matches a graphic.
But with the Scrapern you can show several studios, and a graphic is displayed as soon as one of the studios matches.
With .nfo, the display of the studio works as a logo only if you only have one studio registered (and of course only if it agrees with a graphic)
Something works differently if there are several studios deposited in contrast to .nfo. I have not found out yet ...
Again, this only affects the feature studio as a logo, studios as text always works perfectly.
______

I've just become aware that in MC that handling/settings of MPAA in the movies and series is different. (For me now of course logical, since the MPAA settings are in the movie settings)
Probably I have not noticed until now, because the TV MPAA always worked smoothly in MC. When scrape was almost always without problems, the TV mpaa (US or Inernational) retrieved from the API, and even in the right spelling so that the skin can handle it.
(TV-G, TV-Y, TV-PG, TV-14, TV-MA) not rated I have to rename to "NR".

If in doubt, you can see manually on IMDB or TVDB after the TV MPAA itself, and enter it yourself, in addition have also to pay attention to whether the skin can handle the data (if want to use logo function)

On my side, TV-MPAA works perfectly.
Also with the Movie MPAA settings you can work very well.
I have to pay attention to how the skin is tuned to it, and in case of case formatting that is not accepted in the skin: bulk/batch edit the MPAA in MC in the TableView to a skin accepted spelling.

On the whole, everything works perfectly!
_____

The only idea I can think of.
A good "if then else" function for MPAA should bring with it every good skin.

What do I mean by that? This only affects studios as logos because "a" rating often has different spellings and is sometimes stored differently in the API, but it should always refer to the same graphic.
Example:
if "PG-13" and if "PG 13" and if "rated PG-13" and if "rated PG 13" and if "Parents Strongly Cautioned" then use "PG-13.png"
if "G" and if "rated G" and if "Approved" then use "G.png"
if "not rated" and if "not rated yet" and if "no rating" and if "empty" and if "this movie is not yet rated" and if "unrated" and if "UR" then "NR.png".

I've edited every single .nfo at the MPAA, primary for the purpose that my skin can handle, so reading the tags can also be done for Logo support.
The secondary positive effect was that now with Kodi or MC, when filtering or sorting for MPAA, now have no more MPAA spelling mixup, everything is consistent.

For uniformly written MPAA, some kind of adaptive "renaming" subtool would be nice
Example:
If I scrape a rated "PG-13" movie, different spellings could occur in the API:
"Rated PG-13", "Rated PG 13", "PG-13", "PG 13", "PG13", PG-13 (US) (one could thus also summarize the separate MPAA US ratings to the normal MPAA ratings .)
... then rename everything to "PG-13".

Of course, only users who want to pay attention to a uniform spelling in their database, or have to give consideration to Skin Mpaa logo support, would have had a boost.

But since a bulk editing in the TableView is not very time consuming, i would rather put such a function on the lower list.