Correct way of naming NFO File on Movies spltted into parts (1 Viewer)

[darkside40]

Hi there,
just a quick question what is the correct way to name the nfo file with IMDB ID or the XMBC XML in it if the movie is splitted into several Files for example Cool Movie Part 1.avi, Cool Movie Part 2.avi.

Normally i used Cool Movie Part.nfo, which works with Filminfo+ but the XBMC Local Scraper seems to have a problem with that not finding the NFO file in that case. For that Scraper i must use Cool Movie Part 1.avi which obviously only works if i have the option set on to group files in the same folder.

Because of that i would like to know what is the "official" way to name the nfo files.

 

[fforde]

The importer determines whether or not to group files together before any scraper scripts come into play. In cases where there are multiple files grouped together, the XBMC script looks for an NFO file with the same name as the first file in the grouping. So the following would be valid:

braveheart - part 1.avi
braveheart - part 2.avi
braveheart - part 1.nfo

The NFO preprocessor (which is normally run all the time, regardless of the scraper script used) is a bit more lenient, the above only applies to the XBMC importer.


I am not sure I understand your comment about the "always group files in a folder" configuration option.

 

[darkside40]

First of all thank you for the answer (althought my thanks are a little bit late).

I meant the option in the Importer settings where you can determinate that the importer groups all files in the same folder.

Another question: What is the correct encoding for a XBMC XML file? I have the problem that german umlauts wont be displayed (or it shows another special character) when i add a Movie throught the XBMC Local scraper.

 

[fforde]

Some characters are not valid in an XML file, most characters with an umlaut included. A more common example is the less than sign "<". The less than sign is part of the XML syntax so if text that were not a part of the markup included a less than sign, the document would be impossible to parse. The solution is to use "&lt;" in place of less than. Similarly the "ä" character must be replaced with "&auml;". Without quotes of course.

A full list of XML character encodings can be found on Wikipedia.

EDIT: I realize the absurdity of some of this. Please keep in mind I did not design the XBMC NFO format or the XML specification.

 

[RoChess]

You can normally also set the encoding format via first line.

For XML files this is done via: <?xml version="1.0" encoding="iso-8859-1"?>

The ISO-8859-1 is Western-Europe based and supports é, ë, and special chars such as ß as-is so that no &encode; tricks are needed. If the encoding format is ommited then UTF-8 is usually the default used which requires a special way of saving the file.

I'm just not sure if the XBMC syntax allows for setting an encoding as like shown for the XML syntax, or if Moving-Pictures has support for it.

 

[fforde]

Moving Pictures should handle any valid encoding fine.