2009-06-09, 11:50
mfsav2 Wrote:Hehe... that's true but from this posts Aeon-specific meta-media information index (with Pictures) it appears that there are some files that Aeon requires and from here XBMC / Videos the information are quite confusing.
In one case are TBN, in the other are JPG; in one case is is movie in the other is <movie>...
That;s why I was suggesting it.
I completely understand your intentions, but I think there are just too many variations and every person would want something different anyway.
mfsav2 Wrote:Ok I will try it, I was using an ASK.
Let me know if it doesn't work properly for you. It seems to be working perfectly for me.... but so do a lot of things other people have problems with. lol
mfsav2 Wrote:This is terrible. (for me).
I manage my video library with another program and want to export just the title and the imdb link.
The specification of the NFO is taken from XBMC documentation Video nfo files containing an URL where it explains that the info already present in the NFO are not scraped and, if the url is present the other ones are taken from the ERL.
Why you consider it non conformig?
How can I make it conforming?
How can I make it
It's non-conforming because, for ease of coding and speed, I use .NET's serialize functions to load and save nfos. Instead of parsing and loading/setting each element individually, using probably 200-300+ lines of code, I can just run about 4 lines of code to save and load, but this only works if the nfo is proper xml. Since the url is just text stuck on the end and not proper xml, deserializing fails.
What other program do you use to export these nfo files? Is it possible to have the program export title and imdb id elements instead of a title element and imdb url text? If you did that, it would work just fine, title lock and all.
EDIT: Actually... When an nfo is detected as non-conforming I can have it load the nfo as text and look for a url and check the rest for nfo-type items.... if it passes, convert the url to an element, remove the url, save the resulting file, then recheck it for conformance. If you make a feature request on the google code page for this I'll work on it.