Oruss7 / tinymediamanager

Automatically exported from code.google.com/p/tinymediamanager
0 stars 0 forks source link

UK Movie Certification doesnt populate NFO correctly #20

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

1. Select United Kingdom for Movie Certification
2.
3.

What is the expected output? What do you see instead?

TMM populates the NFO fields mpaa and certification with correct values (Eg. U 
/ 15 / 18) But XBMC requires a prefix for international values and wont display 
the correct rating if its not present. 

The tags should be prefix with UK: (for united kingdom, unsure if other 
prefixes are used for other countries/regions). So an example of a correct tag 
would be <mpaa>UK:18</mpaa><certification>UK:18</certification>

What version of the product are you using? On what operating system?

Windows 7 - 64bit .. Latest Java7u13

Please provide any additional information below.

Original issue reported on code.google.com by scottmpe...@gmail.com on 7 Feb 2013 at 5:52

GoogleCodeExporter commented 9 years ago
Yes, this is currently on the TODO list.

Problem hereby is, that there is no specification how XBMC handles this.
(afaik XBMC only has the 5 US rating built in)
So, all other (localized) ratings are handled by the used SKIN (!)

Was reading the source of some of them, and i found following interpretation of 
localized variants:

- 16
- FSK16
- FSK 16
- Rated 16
- Germany:16
- Germany:FSK16
- Germany:FSK 16
[...]

Every skin implemented different style, there seems not to be a common naming?! 
So basically i'm not yet sure what to write into the NFO to fit them all...
(Country 2 char  vs. Name? both? all known variants seperated by / ?)

What Skin are you using?

Original comment by myron0...@gmx.net on 7 Feb 2013 at 9:31

GoogleCodeExporter commented 9 years ago
I'm using Aeon MQ4 (MQ3 was the same) and this I know definately uses 'UK:' 
prefix for UK certifications as this is what Ember Media Manager populates the 
field with and it works correctly. I think other skins follow this convention 
to.

As to support for other countries I guess it could be problematic if each skin 
has different expectations. Maybe you go with a default prefix for each country 
but have settings to allow the user to override that ?

Original comment by scottmpe...@gmail.com on 8 Feb 2013 at 1:46

GoogleCodeExporter commented 9 years ago
I would give a +1 for writing certifications the way like EMM did:

<country code (2 chars)>:<Rating (shortcode)>

example:

US:R
UK:18
DE:FSK16

But we would need some testimonials to see if (most of) the xbmc skins read it 
the right way.

Original comment by manuel.l...@gmail.com on 9 Feb 2013 at 10:22

GoogleCodeExporter commented 9 years ago
implemented in r337
writing now all possible variants of movie certification to NFO
eg: 
"DE:FSK 16 / DE:FSK16 / DE:16 / DE:ab 16"
"US:R / US:Rated R"

Checked the implementation of about 10 different skins, and mostly all parse 
the MPAA field with some substring, so they should be happy :)
(unfortunately, not all)

Original comment by myron0...@gmx.net on 11 Mar 2013 at 10:12