2009-08-09, 19:10
Well please calm down the situation
I think that what he tries to says if that even if you don't wan't to handle it in the software it's an official possible value for the nfo.
Since you must admit that users can possibly use other tools than ember, if the field if present in the nfo you should read it and write it back when you save the modified nfo.
At this time you just delete the information.
Obviously i'm not a fan of the way he asks but you must admit that it's not really a feature request, it's somewhat a "obligation" to keep in the nfo the values that you don't handle to don't break other tools or new features of xbmc you don't handle and so on.
My 2 cents
I think that what he tries to says if that even if you don't wan't to handle it in the software it's an official possible value for the nfo.
Since you must admit that users can possibly use other tools than ember, if the field if present in the nfo you should read it and write it back when you save the modified nfo.
At this time you just delete the information.
Obviously i'm not a fan of the way he asks but you must admit that it's not really a feature request, it's somewhat a "obligation" to keep in the nfo the values that you don't handle to don't break other tools or new features of xbmc you don't handle and so on.
My 2 cents